Vertical Management
Avo Assure uses Role-Based Access Control (RBAC) to make sure every user gets the right level of access when working with it. This enables Vertical Management for the administrators allowing them to choose and assign roles to the users in an instance so they only see and do what’s needed for their work.
It improves security, avoids mistakes, and makes it easier for teams to work together, even across different domains without worrying about access and visibility to each and every Avo Assure component, not specific to their role or task.
The benefits of Vertical Management in Avo Assure:
Controlled Access: Users only see and do what their role permits
Improved Security: Prevents unauthorized changes or access
Streamlined Collaboration: Roles like Tester, Reviewer, Manager, or Admin make responsibilities clear
Scalability: Easy to manage permissions as teams and projects grow
Key Entities in Avo Assure:
There are three key entities in Avo Assure:
Who login and use Avo Assure and are added in Avo Assure directly or integrate to SSO
These key entities / resources can be assigned or controlled by different vertical or users. In other words, Projects, Users and Agents / Grids in Avo Assure can be segregated at different levels in an enterprise as Account level, Vertical Level and Project level. This functionality is in addition to project level roles & responsibilities.
Following diagram depicts how Avo Assure's key entities can be segregated at different levels using vertical management.

Last updated
Was this helpful?