> 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/project-management-in-vertical/project-mapping-in-vertical.md).
# Project mapping in vertical
Project mapping in Avo Assure is needed to associate a project with specific security groups. This ensures proper organization of test assets, user roles, and access controls within the defined structure. It helps manage collaboration, execution scope, and visibility of test cases in a structured and secure way. Without project mapping, test management across teams and domains can become unorganized and inefficient.
### Step by step process to map project with vertical:
1\. Click Project Management
2. In Project Management window, select vertical
3. Click Map more button
4. Select Project name
5. Click directory icon and select Security Group
6. Click Add button to assign Security Groups to Avo Assure Roles
7. Click Map button
### Example:
As illustrated in the screenshot above, within the Horizon vertical, the AvoManagers security group is assigned the Quality Manager role for the API Testing project. When a user from the AvoManagers security group logs into their Avo Assure account, they will have access only to the API Testing project under Group Vertical 2 as a Quality Manager. They will not be able to view any other projects.
---
# 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/project-management-in-vertical/project-mapping-in-vertical.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.