> 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/authentication-configuration/grid-management.md).

# Grid Management

Grid execution in Avo Assure allows users to efficiently run a large number of test cases across multiple systems by utilizing the Avo Grid. This distributed approach helps optimize execution time by parallelizing workloads and reducing the time required for test completion. 

The Avo Grid works as a central system that smartly assigns test cases to available machines based on which agents are active and how much capacity each system has. It ensures optimal resource utilization and seamless coordination of test execution across environments.

### Prerequisites for Grid Execution

Before initiating parallel/distributed execution, ensure the following configurations are in place:

[**Agent Configuration**](/avo-assure/administration/authentication-configuration/agent-management/install-and-configure-agent.md)

{% hint style="info" %}
**Note:** At least one agent in the created Grid must be **active** for the test execution to start.
{% endhint %}

### This document includes

* [Managing Grid in Avo Assure](/avo-assure/administration/authentication-configuration/grid-management/managing-grid-in-avo-assure.md)
* [Grid Execution in Avo Assure](/avo-assure/administration/authentication-configuration/grid-management/grid-execution-in-avo-assure.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 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/authentication-configuration/grid-management.md?ask=<question>&goal=<user_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.