> 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

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