> 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/invite-user.md).

# Invite User

Invite user to the organization:

1. Navigate to **`Organization`** -> **`Users`** and click on **`Invite User`**
2. Enter the basic details:&#x20;

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FT6g8eCq0ae3qUbgVH5TR%2Finvite-user1.png?alt=media&amp;token=645ba46c-8ab9-48fd-89d9-094e305d3b30" alt=""><figcaption></figcaption></figure>

&#x20; a. **`User Name`** - Name of the user

&#x20; b. **`User Email`** - Email of the user. User should sign-in using the account linked to same email id

3. Choose the roles to be assigned to the user&#x20;

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FXSFZ1tnbyqGjJBsTdGtU%2Finvite-user2.png?alt=media&amp;token=27b5cbe9-c2a8-4137-b8fc-5706185f1805" alt=""><figcaption></figcaption></figure>

4. Choose the organizations users should be part of&#x20;

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F9ziBH5pPHs8w0PzEUf3E%2Finvite-user3.png?alt=media&amp;token=c350b635-6432-4912-b111-4e80b4608f2b" alt=""><figcaption></figcaption></figure>

5. Click on **`Submit`** to invite the user

#### Invitation Email <a href="#invitation-email" id="invitation-email"></a>

\
From 26.4.1, when **`IZ User Auth`** is enabled and **`Email Settings`** are configured, the invited user receives an email with a **`Set your password`** link:

* The link is valid for **7 days** and can be used **once**.
* After setting a password, the user signs in with **`IZ User`** on the login page.
* If the link has expired, the user can request a new one with **`Forgot password?`** on the sign-in form, or an administrator can use **`Set Temporary Password`** under **`Users`**.

If email is not configured, the invitation is still created but no email is sent. Use **`Set Temporary Password`** to give the user a first password. See [Sign-in and MFA](/product-guides/integral-zone/iz-suite/iz-core/sign-in-and-mfa.md).

<br>

### See Also

* [Organizations](/product-guides/integral-zone/iz-suite/iz-core/organization/organizations.md)
* [Users](/product-guides/integral-zone/iz-suite/iz-core/organization/users.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/invite-user.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.
