Setting Permissions on Repository Objects
Most operating systems allow you to manage file and directory security settings. Similarly, becubic allows the becubic administrators to manage the permissions that are set on individual objects or on all the objects of the same type.
Permissions are granted to the roles, so that users inherit them from their associated role(s).
If permission to access a certain object is denied under one role and granted under another, any user who has the two roles will be denied access to the object. For information about permissions, see Rules for Inheriting Permissions.
Security is managed by granting or denying users these permissions:
- Type permissions, which are set on object classes. The objects in a class are of the same type. See Setting Permissions on Repository Objects.
- Object permissions, which are set on individual objects. See Setting Permissions on Repository Objects.
- Functional permissions, which are predefined. See Managing Roles.