> 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/commencer/get-started-in-5-minutes.md).

# Get started in 5 minutes

This guide takes you from zero to your first documented processing activity in the Dastra register. No advanced configuration — just the essentials to get going.

***

## Step 1 — Create your account (1 min)

Go to <https://app.dastra.eu/signup> and create an account.

{% hint style="info" %}
The free trial lasts 30 days, no credit card required. You have access to all features.
{% endhint %}

***

## Step 2 — Create your workspace (1 min)

A **workspace** is the environment in which you will document your processing activities. In general, one workspace corresponds to one legal entity or one compliance scope.

1. After logging in, click **"New workspace"**
2. Give it a name (e.g. *GDPR Compliance – Company X*)
3. Click **Continue**

<figure><img src="/files/wgXwYFTbg9fofB9klV81" alt="Workspace creation form in Dastra"><figcaption><p>Give your workspace a name</p></figcaption></figure>

{% content-ref url="/pages/TazJeb9S7HKVcmcswcow" %}
[Create and set up a workspace](/en/commencer/commencer/create-and-set-up-a-workspace.md)
{% endcontent-ref %}

***

## Step 3 — Add your first processing activity (2 min)

The core of Dastra is the **record of processing activities (ROPA)**. Start by documenting a simple activity — for example payroll management or email communications.

1. In the left menu, click **Record of processing activities**
2. Click **Create data processing**
3. Choose your creation mode:

<figure><img src="/files/f1YYP7F5bLYDXuQXgm0I" alt="Processing activity creation mode picker: AI Generated, Built-in template, From an asset, Personalized"><figcaption><p>Choose how to create your first processing activity</p></figcaption></figure>

| Mode                  | Description                                                                 |
| --------------------- | --------------------------------------------------------------------------- |
| **AI Generated**      | The AI Assistant generates a pre-filled record from a name or description   |
| **Built-in template** | Start from a Dastra template (payroll, recruitment, CCTV…)                  |
| **From an asset**     | Create a processing activity from an existing asset and its associated data |
| **Personalized**      | Create a blank record from scratch                                          |

To get started quickly, choose **Personalized** or **Built-in template**.

4. Fill in the two required fields:

<figure><img src="/files/sLGMfnNuWn5McQJrAjNC" alt="Processing activity creation form with name field and organizational unit"><figcaption><p>Name and organizational unit are the only required fields at creation</p></figcaption></figure>

* **Name** of the processing activity (e.g. *Payroll management*)
* **Organizational unit** — select the relevant entity

{% hint style="info" %}
The organizational unit of type **entity** automatically sets the data controller. No need to fill it in separately.
{% endhint %}

5. Click **Create data processing**

Your first processing activity is now in the register. You can enrich it progressively (purpose, legal basis, data processed, processors, security measures…).

{% content-ref url="/pages/-LvM7KI26TZ\_CxoNeipO" %}
[Record of processing activities](/en/features/editer-le-registre.md)
{% endcontent-ref %}

***

## Step 4 — Invite a colleague (1 min)

Compliance is a team effort. Invite a first colleague to start delegating.

1. Go to **Workspace Settings > Users**
2. Click **Invite a user**
3. Enter their email address and choose their role
4. Click **Send invitation**

They will receive an access link by email.

{% content-ref url="/pages/B6gsA80btIEK01IC7NBk" %}
[Invite users](/en/commencer/commencer/invite-users.md)
{% endcontent-ref %}

***

## What's next?

You've laid the foundations. To go further:

{% content-ref url="/pages/ymDPX7FFOx7WbxbnSdy5" %}
[Tutorial](/en/commencer/tutorial.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LvByP9jU6iP4h5Kv60B" %}
[Setting up](/en/commencer/commencer.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LvM7KI26TZ\_CxoNeipO" %}
[Record of processing activities](/en/features/editer-le-registre.md)
{% endcontent-ref %}

{% content-ref url="<https://github.com/Dastrateam/dastra-doc-en/tree/main/features/systemes-dia/README.md>" %}
<https://github.com/Dastrateam/dastra-doc-en/tree/main/features/systemes-dia/README.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 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://doc.dastra.eu/en/commencer/get-started-in-5-minutes.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.