NEW!
This feature is new in Arellia v8.1.
Basically, we now have the ability to secure sets of resources based on a user’s role membership (kind of like we did for securing items in the trees). So, in the past, we’ve had item security which limits what items you see in the trees (and tabs in consoles, etc). This new feature limits which resources certain Application Roles can see, view and manage (depending on how the security descriptor is defined).
We’ve used this concept in a use case within LSS (https://www.arellia.com/wiki/display/LSS81DOC/%5BREVIEW%5D+How+to+Limit+User+Access+to+Passwords) but there are other use cases outside of LSS where this could be put into use, so I’d like to see a general overview and more details on how it works within AMS.