> 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/account-admin-mapping.md).
# Account Admin Mapping
Account Admin Mapping in Avo Assure follows the Role-Based Access Control (RBAC) principle, where access is managed through roles rather than individual user assignments.
Account Admin Mapping is a feature within Avo Assure that allows an Account Admin to assign Active Directory (AD) security groups specifically to the Avo Assure Admin role. This is done by clicking on the directory icon next to the role in the Account Admin Mapping section. Once a security group is assigned, all users within that group are automatically granted admin-level access in Avo Assure. This eliminates the need to manually assign roles to individual users and ensures that administrative access is linked directly to directory-based group memberships.
### Roles of Account Admin
1. As account admin, user can create Verticals and map security groups to Avo roles
2. As account admin, user can create project and map it with verticals
3. As account admin, user can add/remove agents from verticals
### Steps to map AD security group:
1. Login to Avo Assure using valid credentials
2. Navigate to the Admin section on the left pane of the landing page
3. Navigate to Account Admin Mapping window in SSO Management
4. Click directory icon
5. Select Security Group from list and click Add
6. Click Save to save the mapping
### **Example:**
Consider John is user who belongs to the group **AccountAdmin** as shown in steps above, since group is now mapped as Account Admin, he will be able to
* create and map verticals
* create and map projects
* add and remove agents
---
# 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/rbac-operational-workflow/account-admin-mapping.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.
