Hello Ricardo,
Today, when you use LifeTime, for an IT user to be able to login in an environment, his default access role must be at least LIST, as the NO ACCESS will prevent the login in the environment even if later we allow access to specific applications directly or through teams.
When we do that, he can list ALL applications, even those that he does not have access to.
But even if the user can't open the application, he/she should not even be able to see them, for security reasons as well as to avoid clutter the screen list, forcing him to scroll or filter.
There is a "workaround", that is to include all the developers in all the teams, setting the access role to NO ACCESS on the teams where there are applications he shouldn't see.
The problem is that even this workaround fails on situations where the user needs to be able to reference the application, but shouldn't be allowed to deal with it in Service Studio or in LifeTime.
This new Access Role would allow to overcome the NO ACCESS shortcome that would be allow him to connect to the environment, but see only the applications he/she has access.
This is a very annoying problem in big factories or in factories where the teams change frequently (fast projects or somewhat high rotation of personal), reducing the ammount of work the team managers have to control access, etc.
Hope I was able to clarify the rationale behind the idea.