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

# User Management

Use User Management to create, update, enable, and disable users.

## Roles

Replica uses roles to control what each user can do. Users without a role cannot use Replica or view data.

See [Roles and Permissions](/admin-guide/user-management/roles-and-permissions.md).

## Groups

Groups help organize users and control resource access.

See [Group Management](/admin-guide/user-management/group-management.md) and [Resource Visibility and Assignment](/admin-guide/user-management/resource-visibility-and-assignment.md).

## System Integrations

System Integrations are API-only identities for automation, independent of any one user's account.

See [System Integrations](/admin-guide/user-management/system-integrations.md).

## Finding Users

The Users list includes a **Search** field to quickly locate a user by name, username, or email address.

## Enabled and Disabled Users

Users must be enabled to sign in. New users are enabled by default.

Disabled users cannot sign in or use the platform. Replica keeps disabled users for history and audit purposes instead of deleting them.

To change a user's status, open the Users list and select `Disable` or `Enable` in that user's actions.

{% hint style="warning" %}
Replica does not support permanent user deletion.
{% endhint %}

## Password Resets

To reset a password, select `Reset Password` in that user's actions.

You can use the generated password or set one manually. The user must change it on the next login.


---

# 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.replicacyber.com/admin-guide/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.