The permissions an end-user has are defined by the roles associated with that user. To grant and revoke user permissions, use the Grant and Revoke role actions.
Permissions can be persistent across multiple sessions, or only be granted for a single session.
Persistent: The association between the end-user and the roles is stored in the database. Every time the end-user logs in the association between the end-user and the roles is established.
Simply set the Is Persistent property of the Role to Yes.
Not persistent: The role is only associated with the user for a single session, and not persistent in the database. When the end-user logs in for a second time, the role is not associated with the end-user.
Simply set the Is Persistent property of the Role to No.
Using Non-Persistent Roles
When end-user authentication and authorization is performed using an external system, non-persistent roles should be used. This makes it easier to map permissions defined in an external system such as an Active Directory, to OutSystems Platform roles.
Using non-persistent roles ensures that changes to end-user permissions made in the external system are reflected in the OutSystems Platform.
About Roles | Role Properties