About Permissions

Security rights in Trapeze are managed using permission keys.

Each security permission key controls a screen or function for which a user can be granted or denied access. For example, a permission key may be used to specify whether a user can edit particular field information on a specific screen.

Using permission keys, you can assign security rights directly to users. Or, you can assign security rights to user groups, and then assign users to the user groups appropriate to their roles. Users inherit permissions directly from the groups to which they belong, and indirectly as members of groups that belong to other groups.

Group memberships allow users to have more than one access level for the same permission key. For example, Grant-level access could be specified for a user for a specific permission key but the user could belong to a group with Deny-level access for the same key. When situations like this occur, the access level with the highest precedence is in effect for the user.

Deny-level access can also be applied when the permission is not currently granted. This allows users to specifically be denied a permission, instead of users not being granted access because they have None-level access.

Grant-level permissions can be applied when the a Deny-level permission has been inherited, but the permission itself will not be granted. To grant the permission, the user must be removed from the group that has the deny permission or the deny permission must be removed from the group.