Authorisation and Visibility

This section explains how selected user interface elements are safeguarded against unauthorised access, i.e. what is the effect if the user has access to the user interface but not to the element.

If a user has access to a user interface but is not authorised to access a certain element of this user interface, then this element will simply be invisible / not be callable.

If the element which the user has no permissions for is to be called by the menu (which is the case for a workflow start or a report call, for example), then the respective menu item will be missing as well.

If the user has no permission to any of the menu items and sub menus of a certain (sub) menu, then that whole (sub) menu will be missing.

This way, the visibility of menus and menu items is completely controlled by the user permissions of their target widgets.

Example: Let's say, the user has the role T1_User, a T1_User container role extension for container "MyStore," and a T1_User role extension for category "Store Statistics." He enters the user interface "My Store UI" which belongs to the container "MyStore." The user interface's configuration has a menu item "Purchase Order" which is a link to a workflow start. This workflow start starts a workflow from the Action Point Template "Handle Purchase Order." This template is assigned to the category "Purchase Orders" only. Then the menu item "Purchase Order" will be missing. This is because of lack of the necessary T1_User role extension for category "Purchase Orders." If this is the only item in the configured menu "Actions," then this menu item will be missing, too.