> 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/user-management.md).

# User Management

The User Management feature enables you to control user access and administration within Avo Assure. You can use this feature to create new users, generate Avo Assure Client tokens, and modify or remove existing user accounts.

{% hint style="info" %}
**Note**: To access **User Management** features, you must be assigned one of the following roles:

* Admin
* Quality Manager with Admin as a secondary role
  {% endhint %}

## This Article Covers the Following Modules

[Viewing User Details](/avo-assure/administration/authentication-configuration/user-management/viewing-user-details.md)\
Learn how to access the User Management section in Avo Assure.

[Creating New User](/avo-assure/administration/authentication-configuration/user-management/creating-new-user.md)\
Learn how to create and onboard new users on the platform.

[Updating User Details](/avo-assure/administration/authentication-configuration/user-management/updating-user-details.md)\
Easily edit and manage details of existing user accounts.

[Removing User](/avo-assure/administration/authentication-configuration/user-management/removing-user.md)\
Learn how to safely delete users from the platform.

[User Roles and Permissions](/avo-assure/administration/authentication-configuration/user-management/users-roles-and-permissions.md)\
Understand different roles and how permissions work in the tool.


---

# 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/user-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.