Beastro is prepopulated with permissions which may meet your organizations needs. On the Permissions page you may create, edit, and delete permissions.
Objects
Permissions are defined against various “objects” in the system. The object types are as follows:
- Pages
- Services
- Data Entities
Objects can be linked to a Module. This is done for Pages and Monetary Limits. Not every page needs to be linked to a Module.
Permissions
Permissions are the records that define the object permission assigned to Roles. Roles are assigned to users. The permission contains a collection of object permissions. A permission is named in a user friendly manner and includes a description and has additional attributes of:
- Corporate Only (Yes/No) defines that this permission is only viewable a corporate credit union for corporate credit union roles. If set to Yes, the Beastro system will not allow this permission to be assigned to a role that is For Member.
- Type defines if the permission is tied to a Corporate Service OR is a base permission. If a Permission is a corporate service type, you will assign the Service. If a permissions is a Corporate Service permission, then any "For Member" roles with this permission will only be activated for any Members that are activated on that service.
In the example above, the “View Account Transactions” permission is selected. This permission allows the user access to the Account Transaction page and the Account Transaction data entity.
Object Permissions
The last piece that ties this together is the Object Permission. With a Permission, you can add the objects and specify the object permissions.
In the example screen shot below, the Object Permission for the Account Transaction permission is the grid to the right side of the screen. The Object Permission defines the platform object and the Permission Code. Permission Codes are as follows:
- Create
- Delete
- Update
- Read
Some permissions are marked as “Corporate Only.” This means the permission can only be assigned to a role that is marked “For Corporate” and not “For Member.” Note that some roles will be both For Corporate and For Member.
If a user selects permissions and later change the role to not “For Corporate” or “For Member,” this will automatically remove any “Corporate Only” permissions upon saving changes. You cannot save the Corporate Only permissions on a role if the role has the “For Member” checked or “For Corporate” not checked.