> 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/agent-management-in-vertical.md).

# Agent Management in Vertical

Agent Management in Avo Assure is the process of configuring, registering, and monitoring test execution agents. Agents are environments where test cases are run. It helps ensure that tests execute in the correct platform. 

Agent Management enables users to activate or deactivate agents, track their online/offline status, and assign them efficiently. It is essential for distributing workloads, enabling parallel execution, and improving test scalability. This ensures faster, reliable, and well-coordinated automation execution across multiple systems. 

### This document includes: 

[Add Agent](/avo-assure/administration/vertical-management/rbac-operational-workflow/agent-management-in-vertical/add-agent.md)

[Manage Agent](/avo-assure/administration/agent-management/manage-agent.md)


---

# 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/agent-management-in-vertical.md?ask=<question>&goal=<endgoal>
```

`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.