+1. I agree. I'm facing the same problem.
This happens in the service studio, on the list of roles of a web screen.
If we click "registered", service studio will check all the roles.
Later on, if we need to uncheck them we have to uncheck them one by one.
This feature would help a lot to improve application security
Avoid setting Registered Roles to access ScreensScreens should use custom Roles instead of using System Roles (Registered)
Impact: OutSystems provides you with a default set of System Roles. However, you should define your own custom Roles, specific to your app. Any Screen with a Registered Role can be accessed by any user with a valid OutSystems session, that is, any user that has logged into an app running in the same Platform Server.
How to fix:
Disable the Registered Role access on all Screens and explicitly grant access to custom Roles that are specific to your app.