> For the complete documentation index, see [llms.txt](https://docs.bfore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bfore.ai/docs/console/account-settings/managing-users.md).

# Managing users

The **Users** page lists everyone in your company with their email, name, role, and status (**Active** or **Deactivated**). Your own row is marked "(you)".

There are two roles: **Admin** and **Read only** - see [Roles and permissions](/docs/console/introduction/roles-and-permissions.md).

## Adding a user (Admins only)

Click **Add user** and fill in first name, last name, email, and role (defaults to Read only). The new user receives access with the role you chose.

## Editing a user

* You can edit your own first and last name. Changes apply the next time you log in.
* Admins can change other users' **roles**, but not their names or emails.
* Email addresses can never be changed after creation.
* Nobody can change their own role.

## Disabling and enabling users (Admins only)

Users are never deleted - they are disabled. Click the disable icon on a user's row and confirm; their status changes to **Deactivated** and they can no longer sign in. A deactivated user can be re-enabled the same way at any time.

You cannot disable your own account.


---

# 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.bfore.ai/docs/console/account-settings/managing-users.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.