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

# Managing roles and permissions

Find out how to manage roles and permissions in Dastra.

When you invite a user, Dastra offers **five roles** by default:

* **Administrator**: administrators have contributor rights and can administer workspace settings. Administrators are the only ones who can set a processing activity to "published" status, create organizational units and invite new users to the workspace.
* **Contributor**: contributors can read and edit workspace content. They can create items and modify drafts that have not yet been published. They cannot modify workspace settings.
* **Reader**: readers can only view workspace content. They cannot edit content or modify workspace settings.
* **Auditor**: role of the compliance module. It gives read access to files and attachments, and lets you edit your own compliance audit items.
* **Compliance tester**: role of the compliance module. It gives read and write access to files and attachments, and lets you edit your own compliance operational items.

{% hint style="info" %}
Only **owners** can modify the organization account settings and create workspaces.
{% endhint %}

## Assign a role to a user

In Dastra, a user can have several roles. You can assign them from two places.

### In the current workspace

1. In the left menu, click **Workspace settings**, then **Users**.
2. Open the menu of the user's row, then click **Assign roles**. The number in brackets is the number of roles the user already has.
3. Select the role or roles to assign.

### In several workspaces at once

Only the owners of the organization can use this method.

1. Click your profile icon at the top right of the screen, then **Organisation Configuration**, then **Users**.
2. Open the menu of the user's row, then click **Workspaces**.
3. Click **Assign**, select the role, and choose the scope: **All workspaces from organization** or **Customized workspaces selection**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-fc0a9f39b8b98ecccb31b39696bc1a391813596f%2Fgetting-started-roles-1.png?alt=media" alt="Role assignment window with the role list and the choice of workspaces"><figcaption><p>Assigning a role to all workspaces or to a selection</p></figcaption></figure>

You can also create custom roles, which may fit your organization better.

## Create a custom role

To create a custom role, you must be the owner of the organization.

1. Click your profile icon at the top right of the screen, then **Organisation Configuration**.
2. In the configuration panel, click **Roles and permissions**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-448149c12450b16fb9c4151b082d883eb04ab83b%2Fgetting-started-roles-2.png?alt=media" alt="Profile menu with the Organisation Configuration entry"><figcaption><p>The profile menu</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-4c95a43a738e56ada0fd1650f5084df585e5ba64%2Fgetting-started-roles-3.png?alt=media" alt="Organization configuration panel with the Roles and permissions button"><figcaption><p>The organization configuration panel</p></figcaption></figure>

The list of roles and permissions appears.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-733d98449e081f7195265cda3d9bc8a2633e1f2c%2Fgetting-started-roles-4.png?alt=media" alt="List of base roles and custom roles"><figcaption><p>The list of roles, with examples of custom roles</p></figcaption></figure>

{% hint style="info" %}
Only the organization's owners can access the roles and permissions management screen.
{% endhint %}

3. Click **Create new role** and give it a name.
4. Tick the permissions linked to each feature (**Read**, **Write**, **Create**, **Import**, **Export**, and so on). In the modules that offer it, the **Create** permission allows the creation of new items, independently of the **Write** permission, which allows their modification (see [Roles and permissions](https://doc.dastra.eu/en/features/settings/roles.md)).
5. Click **Save changes** at the bottom of the screen.

To start from an existing role, click **Clone** next to it. **View permissions** displays the permissions of a role without changing it.

{% hint style="info" %}
To take effect, the new role must be assigned to one or more users, from the **Users** page described above.
{% endhint %}

You can now follow the tutorial or start exploring Dastra's features on your own.

{% content-ref url="/pages/ymDPX7FFOx7WbxbnSdy5" %}
[Tutorial](https://doc.dastra.eu/en/getting-started/tutorial.md)
{% endcontent-ref %}


---

# 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/roles.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.
