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

# Create and assign teams

Find out how the Dastra team system works.

In Dastra, users are grouped into teams. Teams are then assigned to legal entities or to departments, which lets you manage roles and responsibilities precisely.

## Create a team or add a user to a team

In the left menu, click **Workspace settings**, then **Teams**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-a15012648a04c1a4a4cc55b4f63f9008a7c3da37%2Fgetting-started-teams-1.png?alt=media" alt="List of teams in the workspace settings"><figcaption><p>The list of teams</p></figcaption></figure>

To create a team, click **Add a new team**, give it a **Name** and, if you want, an **Internal reference**.

To add a user to an existing team, click the three dots to the right of the team, then **Edit**, or click the team name directly. The list of users assigned to the team appears: add the users you want, or send an invitation to a new user.

To delete a team, click **Delete** in the team's menu.

## Assign a team to organizational units

A team gives access to the content of the organizational units it is assigned to. You can assign it in two ways.

* From the team: click **Edit**, then tick the units in the **Organizational units** list.
* From the organizational unit: in **Workspace settings** > **Organizational units**, click the three dots of the unit, then **Set permissions for**.

<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 with the list of organizational units"><figcaption><p>Assigning a team to organizational units</p></figcaption></figure>

{% hint style="info" %}
As soon as an organizational unit has permissions, only the listed users and teams can access it. For the inheritance rules between parent and child units, see [Restrict access to the content of an organizational unit](https://doc.dastra.eu/en/getting-started/setup/organizational-units.md#restrict-access-to-the-content-of-an-organizational-unit).
{% endhint %}


---

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