Security
Security in Therefore™ is defined using Role-Based Access Control (RBAC).
In RBAC, permissions are set under role-based attributes. A Role can be defined as a group (set) of permissions with a given name and description (e.g. Administrator, Operator, Reader, etc) that are logically put together.
Users and Groups can then be assigned a predefined or customized role on an object. Roles are inherited unless otherwise specified. That means that if a group is given the Administrator role on the Therefore™ root object they will be administrators on every Therefore™ object unless an administrator changes the security configuration on a specific object.
Right-clicking on the Role node opens a context menu including the following options as well as the Export and Security options:
New Role
Create a new customized role.
New Deny Role
This is a legacy feature.
Right-clicking on a defined role opens a context menu containing the following options as well as the Export option:
Open Role
Open the Role Definition dialog to edit the role.
Open Role for Copy
Opens a dialog where the role name and permissions can be modified before the role is copied.
Delete Role
Delete the selected role.
Show Assigned Objects
Shows the objects the role is assigned on.
Translation
Choose another language to display the saved translation for the role.
The Role Definition dialog contains the following options:
Role Name / Description
Enter an intuitive role name and description to a custom role, or review the name and description for pre-defined roles.
Permissions
Check the permissions the role should have. The available role-based access permissions can be reviewed here: