> 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.md).

# Administration

Administration (Admin) is a role in Avo Assure that helps perform several actions like manage users, feature, and projects. It also helps work with Avo Assure Agent and Grid which are necessary to automate Test cases. Additionally, it also enables users to work with session management, locked Test cases, authentication configuration, email server configuration, as well as license details of other users.

To access Admin in Avo Assure, follow the steps below:

1. Navigate to the **Admin** section on the left pane of the landing page
2. Click the **Admin** tab to go to the admin section and find options below

### This topic covers

* [Authentication Configuration](/avo-assure/administration/authentication-configuration/authentication-configuration.md)
* [User Management](/avo-assure/administration/authentication-configuration/user-management.md)
* [Email Server Configurations](/avo-assure/administration/authentication-configuration/authentication-configuration-1/email-server-configuration.md)
* [Agents](/avo-assure/administration/authentication-configuration/agent-management.md)
* [Avo Assure Grids](/avo-assure/administration/authentication-configuration/grid-management.md)
* [Session Management](/avo-assure/administration/authentication-configuration/session-management.md)
* [Privileges](/avo-assure/administration/authentication-configuration/authentication-configuration-1/privileges.md)
* [Manage Projects](/avo-assure/administration/authentication-configuration/manage-projects.md)
* [License Details](/avo-assure/administration/authentication-configuration/license-details.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.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.
