Once you defined the roles for your module, the OutSystems Platform provides you a set of System Actions, built-in functions, and exceptions necessary to use these roles in your logic.

Role Actions

The OutSystems Platform provides you a set of System Actions that are available in the Roles folders (on the Logic Layer of the module tree) and can be simply dropped into your action flow. The Role Actions folder is organized by role in your module.

For each role in your module, the OutSystems Platform provides the following Role actions:

This action is not available for the Anonymous and Registered roles.

This action is not available for the Anonymous and Registered roles.

Role Functions

To check end-user roles in your expressions, the OutSystems Platform provides you with a built-in function that is available in the Roles folder in the Scope Tree of the Expression Editor. To use this function in your expressions, simply drag them from the Scope Tree and drop them into the Edit area of the Expression Editor.

For more details see Role Functions.

Role Exceptions

For each role in your module, the OutSystems Platform creates an exception with the following name not<Role> raised when the user has not been granted role to access that screen.

When the end-user tries to access a screen and does not have the rights to any Role assigned to that screen, OutSystems Platform launches an exception. This exception corresponds to the first Role that fails. The order by which the roles are evaluated is the order in which the roles were created.

For example: if the end-user is not registered and is not an Administrator, and tries to access a screen that requires these roles, the exception raised is notRegistered.

See Also

Grant Role Action | Revoke Role Action | Check Role Action | Role Functions | Security Exceptions