> 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/tutorial/step-2.md).

# Step 2: Map your personal data processing and draw up a register

After [training in data processing mapping](https://www.cnil.fr/en/record-processing-activities) and interviewing the people in charge of processing, you identify your first processing activities below:

| #  | Department          | Personal data processing       | Support / application      | DPIA required? |
| -- | ------------------- | ------------------------------ | -------------------------- | -------------- |
| 1  | HR                  | Recruitment management         | Linkedin (external)        | No             |
| 2  | HR                  | Payroll management             | Payfit (external)          | No             |
| 3  | HR                  | Staff management               | Microsoft Office           | No             |
| 4  | General Secretariat | Works Council data management  | Internal application       | No             |
| 5  | Production          | Quality control                | Microsoft Office           | No             |
| 6  | Marketing & Sales   | Customer management            | Salesforce (external)      | No             |
| 7  | Marketing & Sales   | Sending promotional emails     | Mailjet (external)         | No             |
| 8  | Marketing & Sales   | Prospect profiling             | Salesforce                 | Yes            |
| 9  | Security            | Building entry/exit management | IBM                        | Yes            |
| 10 | Security            | Anteriority check              | Microsoft Office           | No             |
| 11 | IT                  | Software development           | Microsoft Azure (external) | No             |
| 12 | IT                  | Application maintenance        | CGI (external)             | No             |
| 13 | Legal               | Contract management            | Microsoft Office           | No             |
| 14 | Procurement         | Supplier management            | SAP (external)             | No             |

Then complete your record in Dastra:

{% content-ref url="/pages/-LvM7KI26TZ\_CxoNeipO" %}
[Record of processing activities](https://doc.dastra.eu/en/features/ropa.md)
{% endcontent-ref %}

{% hint style="info" %}
To start designing your record, first import your existing records in Excel format, if you have any, along with your repositories of stakeholders, applications, processors, data and retention rules. Once all the repositories are integrated, data entry is quicker.
{% endhint %}

Then fill in all the information required for a processing activity by following the steps described in the page below:

{% content-ref url="/pages/SfET9imfcYryS8JcO4LP" %}
[Declare a processing activity](https://doc.dastra.eu/en/features/ropa/declare.md)
{% endcontent-ref %}

You share the record with all the controllers and with your network of GDPR correspondents, and you ask all stakeholders for validation.

{% content-ref url="/pages/-LveMzt-dJcR4lpyhE6C" %}
[Share the record of processing](https://doc.dastra.eu/en/features/ropa/share.md)
{% endcontent-ref %}

Your record is set up and your processing activities are ready to be protected.


---

# 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/tutorial/step-2.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.
