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

# Manage users

See how to manage a user account.

In order to edit a user account:

1. Go to **Admin tools** on the left side menu.
2. Type your password to enter the administrative mode.
3. In the **Users** tab, click the **Edit** (pen icon) next to the user.
4. In the opened window, you can edit the data such as name, email, user role, status, and access scope.

To temporarily deactivate a user account, change their status from *Active* to *Deactivated*. To completely remove their account, click **Delete user**. Keep in mind that changing the role of a user can take up to an hour to take effect.

### Export user details

You can export the filtered and visible user details in the table to a CSV file. To do so, click **Export Table** located at the top-right corner of the table. *For more information, refer to the* [*Export table data*](/product/administration/repositories/export-table-data.md) *topic.*


---

# 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.debricked.com/product/administration/users/manage-users.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.