> For the complete documentation index, see [llms.txt](https://docs.testwheel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testwheel.com/modules/user-groups.md).

# User Groups

This page offers a comprehensive overview of the User Management tab, outlining the process of adding new users, assigning roles, and configuring action permissions for each user.

The **User Management** section is a central component of administrative control within the platform. It enables authorized users to efficiently manage access, define responsibilities, and maintain role-based security across the organization.<br>

**Key Functionalities Include:**

1. **Adding New Users**\
   Administrators can quickly onboard new team members by entering essential details such as name, email and role. The system supports user uploads for large-scale onboarding.<br>
2. **Role Assignment**\
   Each user can be assigned a specific role (e.g., Admin, Tester, Manager), which governs their level of access and control within the system. Roles ensure that users can only perform actions relevant to their responsibilities.<br>
3. **Managing Action Types (Permissions)**\
   Fine-grained permissions empower administrators to manage user access with precision, including the ability to activate or deactivate user accounts, as well as permanently delete users when necessary.<br>


---

# 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.testwheel.com/modules/user-groups.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.
