> 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/tutorial/step-2-map-your-personal-data-processing-and-draw-up-a-register.md).

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

After training in data processing mapping and interviewing data processing managers, you will identify your first data processing operations 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  | Central secretariat | Works Council data management  | Internal application       | No             |
| 5  | Output              | Quality control                | Microsoft Office           | No             |
| 6  | Marketing & Sales   | Customers 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 | Purchases           | Suppliers management           | SAP (external)             | No             |

Then complete your record in Dastra:

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

{% hint style="info" %}
A good way to start designing your record is to first import your existing records in excel format, if available, as well as your repositories of actors, applications, subcontractors, data and retention rules. This way, once all your repositories have been integrated, you'll save time during data entry.
{% endhint %}

Then fill in all the information required for treatment by following the steps described in the link below.

{% content-ref url="/pages/SfET9imfcYryS8JcO4LP" %}
[Declare a processing activity](/en/features/editer-le-registre/declare-a-treatment.md)
{% endcontent-ref %}

You share the record with all data controllers as well as your network of GDPR correspondents and ask for validation from all stakeholders.

{% content-ref url="/pages/-LveMzt-dJcR4lpyhE6C" %}
[Share the record of processing](/en/features/editer-le-registre/partager-le-registre.md)
{% endcontent-ref %}

That's it, **your record is set up** and your treatments 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/commencer/tutorial/step-2-map-your-personal-data-processing-and-draw-up-a-register.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.