> 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/rbac-operational-workflow/vertical-admin.md).
# Vertical Admin
In Avo Assure, Vertical Admin is administrative role with delegated control within specific verticals. This role is responsible for managing users, projects, and configurations within their assigned vertical.
For mapping the verticals, refer [Vertical Mapping](/avo-assure/administration/vertical-management/rbac-operational-workflow/vertical-management/vertical-mapping.md) section from this doc
Under the RBAC (Role-Based Access Control) structure:
* Vertical Admins can access the admin section relevant to their vertical, including project management, agent configuration, and role assignment within that vertical.
* They have permission to create, edit, and delete users within their vertical and can assign roles such as Quality Engineer, Quality Lead, and Quality Manager.
{% hint style="info" %}
**Note:** Vertical admins will not have access to create verticals
{% endhint %}
### Steps to login and view assigned verticals of Vertical Admin:
1. Login with Vertical admin access, admin screen will appear
2. Expand Vertical Management section and click Vertical
3. In Verticals window, assigned vertical will be displayed where vertical admin can manage users from that vertical
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.avoautomation.com/avo-assure/administration/vertical-management/rbac-operational-workflow/vertical-admin.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.