Thereforeâ„¢ Help

Note:

• Following an update, security configurations that have been carried over from a previous Thereforeâ„¢ version will continue to be fully functional in Thereforeâ„¢ 2020. Under the Role node, these security configurations that have been carried over will be displayed as a numbered role (e.g. Role 6, Role 7 etc), and they will appear as roles with either 'Allow' permissions (symbolized by a green tick ) or Deny permissions (symbolized by a red and white mark ).

•The number of roles that the system creates is designed to be at a minimum. E.g. If several users possess the same permission settings in the classic version, they will be given the same role in the new role-based model following the upgrade. However, after the upgrade to Thereforeâ„¢ 2020, the security configurations (from the older version) may display several numbered roles under the Role node, but these can be condensed into smaller numbers of roles by reviewing and replacing them with an existing defined role.

Examples:

Example of a pre-installed named role:

Example of a numbered role carried over from a previous Thereforeâ„¢ version:

Note: The post-update default setting under 'Security Mode' in the 'Advanced Settings' will be the Access Mask (Deprecated). The classic security concept will remain fully functional (as before) though a new Role node will be included under Access. The classic 'Access Mask' security mode will in reality work with the Role-Based system in the background, where the classical mode emulates the security features of previous Thereforeâ„¢ versions using the configurations in the Role-Based system. The classic 'Access Mask' security mode will in reality work with the Role-Based system in the background, where the classical mode emulates the security features of previous Thereforeâ„¢ versions using the configurations in the Role-Based system". We really have emulation of old security based on RBAC.

Note: Permission within the role can also be edited by opening the Role Definition dialog.