> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-core/organization/users.md).

# Users

List of all users in the system

1. Navigate to **`Organization`** -> **`Users`** 

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fl0PUaXoldtyWqmKPqFaf%2Fusers.png?alt=media&amp;token=14e366a3-94be-4c4f-b540-c38606dd2066" alt=""><figcaption></figcaption></figure>

2. Actions include -

a. **`Assign Roles`** - Configure roles to the user&#x20;

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F2o3sT848jhi9sqy4rcQQ%2Fassign-role.png?alt=media&amp;token=06b764f1-136e-478f-9656-759335f1dc81" alt=""><figcaption></figcaption></figure>

b. **`Assign Permission`** - Configure permissions to the user&#x20;

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FO3vwviWdkXPUygUvcRKf%2Fassign-permission.png?alt=media&amp;token=7d666121-cd52-4987-b543-e0ff2683af9c" alt=""><figcaption></figcaption></figure>

c. The actions menu of each user also offers, depending on your permissions:

| Action                                 | Description                                                                                                                                                      |
| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **`Manage Subscriptions`**             | Manage the user's notification subscriptions.                                                                                                                    |
| **`Set Temporary Password`**           | From 26.4.1. Set an IZ User Auth password for the user. The user must change it at their next sign-in.                                                           |
| **`Reset MFA`**                        | From 26.4.1. Remove the user's authenticator and recovery codes, for example after a lost device. The user sets up an authenticator again at their next sign-in. |
| **`Disable User`** / **`Enable User`** | Disable or re-enable the user. A disabled user cannot sign in.                                                                                                   |

**`Set Temporary Password`** and **`Reset MFA`** require the **`Generate Security Token For Another User`** permission. See [Sign-in and MFA](/product-guides/integral-zone/iz-suite/iz-core/sign-in-and-mfa.md).

{% hint style="info" %}
From 26.4.1 every tenant has an **`IZ Support User`** licence administrator. It has no password and is used only by Integral Zone support to recover access when all administrators are locked out.
{% endhint %}

### See Also

* [Organizations](/product-guides/integral-zone/iz-suite/iz-core/organization/organizations.md)
* [Invite User](/product-guides/integral-zone/iz-suite/iz-core/organization/invite-user.md)
* [Roles](/product-guides/integral-zone/iz-suite/iz-core/organization/roles.md)


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-core/organization/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.