In OutSystems, how do we restrict access to a Screen?

In OutSystems, restricting access to a screen is done through the screen properties where you can manage visibility based on user roles. By unticking the roles in the Screen Properties, you effectively limit which user roles can access that specific screen. This means that only users with the associated roles checked will be able to see and interact with the screen, providing a straightforward way to control access based on predefined user roles within your application.

The other methods for access control, while they may seem relevant, do not function in the same way. Associating the screen with roles via the Users application is not a direct method to restrict access at the screen level, but rather pertains to user management in general. The CheckRole Action can be used for dynamic role verification, but it requires additional coding to handle access logic, making it less direct than simply adjusting the properties of the screen itself. Lastly, the idea that only authenticated users can access a screen does not account for the design flexibility OutSystems provides through roles, which is fundamental in adapting user experiences.