RBAC

Avo Assure now supports Role-Based Access Control (RBAC), a security and governance feature that allows administrators to assign specific roles and permissions to users. With RBAC, access is granted based on a user’s role within the project, ensuring that each user only has the rights needed to perform their responsibilities. This improves security, prevents unauthorized actions, and simplifies collaboration across teams. This enhancement is designed to support multi-domain operations and restrict cross-domain visibility and access. 

The key benefits of introducing RBAC to Avo Assure is to help with:

• 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

RBAC & Key Entities in Avo Assure:

There are three key entities in Avo Assure:

1. Users

Who login and use Avo Assure and are added in Avo Assure directly or integrate to SSO

2. Projects

An application under test or project that stores elements, testcases, execution profiles and reports

3. Agents/Grids

Are used for test execution in Avo Assure

In any enterprise, these key entities / resources can be assigned or controlled to different vertical or users through RBAC (Role Based Access Control) functionality. In other words, Projects, Users and Agents / Grids in Avo Assure can be isolated at different levels in an enterprise like Account level, Vertical Level and Project level. This functionality is in addition to project levels roles & responsibilities.

Following diagram depicts how Avo Assure key entities can be isolated at different level using RBAC.