> For the complete documentation index, see [llms.txt](https://bluurdoc.bluur.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluurdoc.bluur.ai/en/functions/team/inviting.md).

# Inviting

To invite a new user to the organization, click the **Add user**.

<figure><img src="/files/ab5a6d3009b49081174c332e66c85ae661e03ff3" alt="Przycisk Dodaj użytkownika w widoku zarządzania zespołem."><figcaption><p>Starting the user invitation process.</p></figcaption></figure>

The system will display the invitation window. Enter the user's company email address and select the role to be assigned to their account.

{% hint style="warning" %}
**Important:** Only users using the same company domain on which the organization account was created can be invited to the organization.
{% endhint %}

## Adding multiple users

You can prepare invitations for several users in one window.

To add another person, click **Add another**, enter their email address, and choose the appropriate role. After filling in all entries, click **Send invitation**.

Each indicated person will receive a separate email with instructions on how to join the organization.

{% hint style="info" %}
The system does not set a separate limit on invitations sent from one form. The number of users in the organization is subject to the limit resulting from the active subscription.
{% endhint %}

<figure><img src="/files/254df7a44c3cb33e72dfd5f21d79a07a67c1e1e0" alt="Formularz zaproszenia użytkowników z polami adresu e-mail, wyboru roli i opcją Dodaj kolejnego." width="375"><figcaption><p>User invitation window.</p></figcaption></figure>

After the invitation is sent, the user will receive an email with an activation link. After opening the link, they will be redirected to the registration form, where they can enter their first and last name and set a password for the account.

<figure><img src="/files/f63da91a9aa66e20f409ab5fff7cad28f286b682" alt="Wiadomość e-mail z zaproszeniem do organizacji i linkiem aktywacyjnym."><figcaption><p>Message sent to the invited user.</p></figcaption></figure>

{% hint style="warning" %}
**Important:** The sent invitation is valid for 24 hours. After this time, the link will expire and become inactive. To invite the user again, delete the user and then send the invitation again.
{% endhint %}

The invitation status can be checked in the **Team**. Until the account is activated, the status visible next to the person will be **Invited**.

After registration is completed, the status will be updated, and the list will show the data provided by the user, including their first and last name. The administrator will also receive an email confirming account activation.

After creating the account, the user can change their avatar and profile details, such as first and last name. They cannot independently change the email address assigned to the account or remove themselves from the organization.

<figure><img src="/files/e7ad92deff320c8f628d361f96d883540e2c5377" alt="Użytkownik ze statusem Zaproszony widoczny na liście zespołu."><figcaption><p>The status of a user awaiting account activation.</p></figcaption></figure>


---

# 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://bluurdoc.bluur.ai/en/functions/team/inviting.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.
