It represents a company enforced policy. It takes precedence over all other security policies in the system.
For example, in a company the CEO will have permissions to view anything and everything. For this a role called CEO can be created and permission be given to add/edit/view/delete everything.
Define role policies only when you can say something like A can do anything or B can never do something. i.e no matter what the situation, a particular policy applies. Otherwise, you should use object policy.
Note: Only users playing the role of administratorcan set role privileges.
From the tool bar click →
Under the general section click
Use the delegate option when you want the object security policy to be consulted.
![]() | Important |
|---|---|
If a user is playing two roles and a permission is granted for one role, but denied to the other (at the same level), then the permission is denied. |