> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/getting-started/setup/users.md).

# Invite users

Find out how the Dastra invitation system works.

## Invite a user

You can invite someone to collaborate on your workspaces by inviting them to the organization the workspace belongs to.

1. In the left menu, click **Workspace settings**, then **Users**.
2. Click **Invite user**.
3. Enter the email address of the person. If this address is not already attached to the organization, click it to continue.
4. Fill in the invitation form (see the table below), then click **Send an email invitation**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-86524949f2354cb125f63176787cb1e7d70d54aa%2Fgetting-started-users-1.png?alt=media" alt="List of the workspace users with the Invite user button"><figcaption><p>The Users page of the workspace settings</p></figcaption></figure>

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-eeb8c61f44547a0ca5be44729b3d119f641c59bf%2Fgetting-started-users-2.png?alt=media" alt="User invitation form"><figcaption><p>The invitation form</p></figcaption></figure>

| Field                             | Description                                                                                   |
| --------------------------------- | --------------------------------------------------------------------------------------------- |
| **First name(s)** and **Surname** | Identity of the invited person                                                                |
| **UI language**                   | Language in which the person sees Dastra                                                      |
| **Invite to all workspaces**      | Switch: without it, you choose the workspace concerned                                        |
| **Select user's roles**           | See [Managing roles and permissions](https://doc.dastra.eu/en/getting-started/setup/roles.md) |
| **Select teams**                  | See [Create and assign teams](https://doc.dastra.eu/en/getting-started/setup/teams.md)        |
| **Default login method**          | Local account (login and password) or SSO, when an SSO is configured                          |
| **Welcome message**               | Text added to the invitation email                                                            |

You can also click **Invite a member** at the bottom of the left sidebar: it opens the same form.

The invited person receives an email with a link that gives access to the workspace. You receive a notification email when they click the link. The invitation link expires after 10 days.

Instead of sending the email, you can click **Generate a link**: Dastra displays a link that you pass on to the person yourself.

### Find the pending invitations

You manage pending invitations in the **Invitations** tab of the **Users** page.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-7841abc323a8b93bac3ed1e804044ce08957a96a%2Fgetting-started-users-3.png?alt=media" alt="Invitations tab with a pending invitation"><figcaption><p>The Invitations tab</p></figcaption></figure>

{% hint style="info" %}
Your subscription limits the number of users. The quota counts the active users and the users linked to a pending or expired invitation: remove the user of an invitation you no longer need to free a seat. When the limit is reached, Dastra shows **You have reached the users limit** and you can contact the Dastra team to increase it.
{% endhint %}

### Resend an invitation link

If the invited person has not clicked the link and it has expired, click **Resend** next to the invitation, then confirm.

### Create and assign teams

In Dastra, users are grouped into teams. Teams are then assigned to entities or departments, which lets you manage roles and responsibilities precisely. See [Create and assign teams](https://doc.dastra.eu/en/getting-started/setup/teams.md).

### Default roles

Dastra offers five base roles. Their detailed permissions are described in [Managing roles and permissions](https://doc.dastra.eu/en/getting-started/setup/roles.md).

| Role              | Identifier |
| ----------------- | ---------- |
| Administrator     | 1          |
| Contributor       | 2          |
| Reader            | 3          |
| Auditor           | 11000      |
| Compliance tester | 11500      |

{% hint style="info" %}
**Organization owner and DPO are not roles.** To give an already invited user the **owner** status of the organization, see [How to add an organization owner?](https://doc.dastra.eu/en/getting-started/setup/faq.md#how-to-add-an-organization-owner). To **change the DPO**, see [How to change the DPO?](https://doc.dastra.eu/en/getting-started/setup/faq.md#how-to-change-the-dpo).
{% endhint %}

## Import a large list of users

To import a large list of users (50 or more), you go through the Dastra team. You can request the import of a list of up to 200 users, within the limit of the available users.

**Steps to follow:**

1. Open <https://app.dastra.eu/general-settings/users>, click the arrow to the right of the **Invite a user** button, then **Import**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-dfb2959bb42ca8e685871e0a612a74a4c2235d39%2Fgetting-started-users-4.png?alt=media" alt="Menu of the Invite a user button with the Export and Import entries"><figcaption><p>The import menu in the organization settings</p></figcaption></figure>

2. Create one file per workspace, in CSV format, with the following columns separated by commas.

Required:

* `Email`: the email address of the user;
* `GivenName`: their first name;
* `FamilyName`: their last name;
* `Roles`: the identifiers of the roles in Dastra, separated by `|`;
* `Teams`: the identifiers of the teams in Dastra, separated by `|`.

Optional:

* `SSOConfigurationId`: the identifier of the SSO login, if applicable.

Here is a sample file to download and fill in:

{% file src="/files/Q9iXSnN6DSXKZEdgXItR" %}
Import file template
{% endfile %}

**Role identifiers**

The base roles have the identifiers of the table above. For the custom roles you created, the identifier is visible in your browser's developer console, in the Network tab. Roles must be created before the import.

{% hint style="info" %}
To open the console in Chrome: Cmd + Option + C (Mac) or Ctrl + Shift + J (Windows).

To open the console in Firefox: Cmd + Option + K (Mac) or Ctrl + Shift + J (Windows).

To open the console in Microsoft Edge: Ctrl + Shift + I.
{% endhint %}

**Team identifiers**

Teams are identified by their identifier number. To find it, open the team in Dastra with the **Edit** button: the number is in the title of the window.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-aae07e7610180beb601d0f89943b3c3399aae170%2Fgetting-started-teams-2.png?alt=media" alt="Team edit window whose title shows the identifier"><figcaption><p>In this example, the identifier of the Test team is 8019</p></figcaption></figure>

Teams are not mandatory in Dastra. The teams you use in the file must be created beforehand in the workspace.

**SSO configuration identifier**

The `SSOConfigurationId` column is **optional**: fill it in only if you want the imported users to be attached to an SSO login already configured in your organization. Leave it empty for a standard email and password login.

As for custom roles, this identifier is retrieved from your browser's **developer console**, in the **Network** tab:

1. Open [the SSO logins configuration page](https://app.dastra.eu/general-settings/sso) (you must be the owner of the organization).
2. Open the developer console (see the keyboard shortcuts above) and go to the **Network** tab.
3. Click the pencil icon of the relevant SSO login to open the **Edit SSO login** window. This is a modal window: the page URL stays `https://app.dastra.eu/general-settings/sso`.
4. In the **Network** tab, open the request triggered when the window opens and note the value of the `scheme` field (it is also the end of the request URL, after `ssoConfiguration/`): this is the value to enter in the `SSOConfigurationId` column.

{% hint style="info" %}
The SSO login must be configured beforehand. See [Single Sign On (SSO)](https://doc.dastra.eu/en/features/settings/sso.md).
{% endhint %}

3. Save your file in CSV UTF-8 format. In Excel, choose the file type **CSV UTF-8 (Comma delimited)**.
4. Tell us in which workspace you want to import the users and drop the file in the upload interface.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-03b5eb60b76c3135b5c5bc6b8bf87209c5798fc3%2Fgetting-started-users-6.png?alt=media" alt="Upload interface for the user import file"><figcaption><p>The file upload interface</p></figcaption></figure>

The Dastra team receives your request and gets back to you.


---

# 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://doc.dastra.eu/en/getting-started/setup/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.
