> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/administration/vertical-management/understanding-avo-assure-roles.md).
# Understanding Avo Assure Roles
In Avo Assure, different roles have different privileges and permissions according to that QM, QL and QE perform their tasks
Go through the below screenshot to know the privileges:
### Primary Roles
**There are three primary roles defined within the system, listed here in descending order of hierarchy:**
Role
Description
Hierarchy Level (Highest to Lowest)
Quality Manager
(QM)
Holds the highest authority in the quality
domain.
1 (Highest)
Quality Lead (QL)
Mid-level role overseeing quality tasks
and team members.
2
Quality Engineer
(QE)
Entry or execution-level role responsible
for quality engineering activities.
3 (Lowest)
**Additionally, there is one Secondary Role:**
| Role | Description |
| ----- | ------------------------------------------------------------------------------------- |
| Admin |
Support role with administrative
privileges, separate from quality roles
|
### Role Precedence across Multiple Assignments
When a security group is linked to a vertical with multiple roles assigned to a single user, the role with the highest precedence will be considered effective.
**Example:** If a user is assigned both QM and QE roles within the same vertical, the system will assign the QM role privileges because QM outranks QE.
### Admin Role Combination:
The **Admin role** can be combined only with the Quality Manager (QM) role at the vertical level.
If a security group is mapped to a vertical with both QM and Admin roles, the user will have:
**Primary role:** Quality Manager Privileges Additional role: Vertical Admin privileges
### Project-Level Roles
Project-level roles mirror the same three primary roles: QM, QL, and QE.
The key difference from primary roles is that project-level roles are specific to individual projects.
A user can have a primary role (instance-level) such as QM across the organization but hold different roles (e.g., QL or QE) for specific projects.
Project-level roles define the user's privileges and responsibilities within the context of that particular project, which may differ from their primary role.
### **Summary of Role Assignment**
Role Type
Role Options
Scope
Privilege Determination
Primary Role
QM, QL, QE
User Level
Highest role takes precedence if multiple roles
assigned
Project Role
QM, QL, QE
Project-specific
Role assigned per project defines privileges for that
project
Secondary
Role
Admin
Account/Vertical
Level
Separate administrative
privileges
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.avoautomation.com/avo-assure/administration/vertical-management/understanding-avo-assure-roles.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
