User rule
Rule types – Abstract
Purpose: Is considered 'passed' if the User of session is included in a whitelist that can be statically configured by multiple selection.
A User rule is considered 'passed' if the user (see Users) in the applicable login context (see User of session) is included in a positive list that can be statically configured via multiple selection.
In the following cases, the User rule is always considered as 'failed':
The multiple selection in the configuration does not contain any Users.
A guest user (see Guest users) is logged in the current session and the rule is not executed in the context of an Run as event action that assigns a 'real' user.
Configuration
The User rule refers to the User of session, which is generally defined by the session, but can be temporarily changed by the Run as event action (see also Session based).
The reference object in the execution context is irrelevant for this rule.
|
The User rule configuration provides a static multiple selection via a Multiselect combobox with search function, which offers all Users who have at least read access in the context of the configuration for selection.. ►NOTE◄ If there is no read access for a selected user account, a neutralized label will appear for it, indicating that the account is 'hidden' (hidden). As long as this entry is not specifically removed, it will remain in the list even if other entries are added or removed. 'Hidden' entries deselected by 'inversing' an existing selection do not reappear in the selection by 'inversing' again. |
|
