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

# Record of processing activities

Learn how to edit the record of processing.

## Introduction

The record of processing activities allows you to map your **data processing** and to have **an overview** of what you do with the personal data concerned. Keeping a complete record is a **requirement** of Article 30 of the GDPR, but beyond the legal obligation, it is above all **a tool to better understand your data** and **control the associated value chain**, from the moment the data is produced to the way it is used.

Dastra provides a record and **questionnaires** that guide you step by step as you map your processing activities.

## The Dastra record in a few words

Dastra's record of processing activities meets all regulatory requirements. Both records, the data controller record and the data processor record, rely on repositories (stakeholders, assets, datasets, data, risks and security measures) that allow you **to map your processing activities** and **save time** in your day-to-day management.

Processing activities can be copied, and processing activity templates are available in a library freely accessible to all our users. A workflow is built in, a search function is available natively, and you can export processing activities in different formats (PDF, Word, HTML, Excel, CSV, JSON, Markdown) and import them from CSV, Excel or JSON files. You can also attach documents, data breaches or risks to your processing activities.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-cc4d06a3f99bb5dc253f981cab1af77d5e3a03ed%2Fropa-readme-1.png?alt=media" alt="Record of processing activities list with its indicator tiles and toolbar"><figcaption><p>The record of processing activities: indicator tiles at the top, then the list of processing activities</p></figcaption></figure>

## "Data controller" record versus "Data processor" record

Article 30 of the GDPR sets out specific obligations for the *controller's record* and the *processor's record*. If your organization acts as both a processor and a controller, your record must therefore clearly distinguish the two categories of activities.

**In practice, in this case, the French CNIL recommends that you keep 2 records:**

1. one for the processing of personal data for which you yourself are responsible,
2. another for the processing operations that you carry out, as a processor, on behalf of your clients.

{% content-ref url="/pages/529ywLjSqAr94cjpWWxO" %}
["Data controller" record](https://doc.dastra.eu/en/features/ropa/controller.md)
{% endcontent-ref %}

{% content-ref url="/pages/6XU7MuobMDopcsdrC9wf" %}
["Data processor" record](https://doc.dastra.eu/en/features/ropa/processor.md)
{% endcontent-ref %}

## The different methodologies for setting up the record of processing activities

There are two methodologies for building the record of processing activities:

* **Top-Down design**: you start the project by drawing up the inventory of data processing activities, and then you collect the information specific to each processing activity (data, processors, etc.).
* **Bottom-Up design**: you start by making an inventory of the data (software, datasets and personal data fields) and you create the processing activities from it.

### Choosing a methodology

There is no right or wrong method: everything depends on the context of your organization, the skills of the DPO team, how accessible the people who operate the data are, etc.

Here is a table comparing the two approaches:

<table><thead><tr><th width="129">Methodology</th><th width="178">Target</th><th>Benefits</th><th>Disadvantages</th></tr></thead><tbody><tr><td><strong>Top-Down</strong></td><td>Small organizations or local authorities<br>Companies with a weak data culture<br>Legal team with little affinity for IT</td><td>Quick to set up<br>Less work<br>Matches the legal expectations of the GDPR well</td><td>May cause difficulties if the team setting up the record does not know the organization's data<br>More demanding for operational staff<br>The data inventory is much less valuable because it is modeled for legal purposes only<br>More complex to maintain over the long term</td></tr><tr><td><strong>Bottom-Up</strong></td><td>Large or medium-sized organizations<br>With a strong data culture<br>Legal team with a strong IT affinity</td><td>Taking an inventory of the data is less abstract than creating processing activities directly<br>The record reflects the reality of the organization<br>The record is easier to maintain in the long run<br>More members of the organization are involved<br>Creating processing activities is more automated</td><td>Overall more difficult and time-consuming to implement<br>The project requires good governance</td></tr></tbody></table>

Dastra supports both approaches. For a top-down approach, create processing activities [from templates](https://doc.dastra.eu/en/features/ropa/templates.md). If you prefer the bottom-up approach, you can [build your data map](https://doc.dastra.eu/en/features/mapping.md) first and then create a processing activity directly from an asset (software, database).

## Set up your record

To learn how to design and manage your record of processing activities, start here:

{% content-ref url="/pages/4TOVCUQ6y1fnuq8YaZiH" %}
[Establish your record](https://doc.dastra.eu/en/features/ropa/establish.md)
{% endcontent-ref %}

To learn how to design and manage one of your processing activities, start here:

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

To understand the sections of the questionnaire, see:

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

To learn how to share the record of processing, see:

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

## Act on several processing activities at once

In **List view**, tick the boxes on the left of the processing activities you want to work on. The **Select a batch action** button then appears above the list. Depending on your permissions and on the features enabled in your workspace, it offers the following actions:

* **Switch workflow stage**
* **Export**
* **Linking stakeholders**: add or remove stakeholders or recipients on all the selected processing activities
* **Edit fields...**: change the value of one or more fields on all the selected processing activities
* **Merge**: see [Merging elements](https://doc.dastra.eu/en/features/general/merge.md)
* **Send questionnaires**
* **Review**
* **Share**
* **Move to recycle bin**

## Follow the record with reporting

In the left-hand menu, click **ROPA**, then **Reporting** to display the statistics of your record.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-a79f17884686c9f015c7940451dd9eb2b95adc4d%2Fropa-readme-2.png?alt=media" alt="Reporting page of the record of processing activities with its indicator tiles and widgets"><figcaption><p>The Reporting page of the record</p></figcaption></figure>

The page shows:

* indicator tiles for the number of processing activities and for the **Overall progression**, **Quality** and **Sensitivity** indicators;
* the **Indicator Averages** and the **Indicator breakdown**;
* the number of processing activities per **Workflow** step, per **Legal basis**, per **Data subject** category, per processor and per organizational unit;
* the share of processing activities with data transfers, the countries concerned by the **Data transfer** widget and the **DPIA** status;
* the evolution of the number of processing activities (**Creation date**) and the **Activity logs**.

Use the organizational unit selector, the filters and the **All**, **Data controller** and **Data processor** buttons to narrow the statistics. Click **Print** to print the page.

## Impact analyses and privacy by design requests

Two more entries of the **ROPA** menu give access to the questionnaires linked to your processing activities. They are displayed when you have access to questionnaires.

* **Impact analysis** lists the [DPIA](https://doc.dastra.eu/en/features/questionnaires/types/dpia.md), [LIA](https://doc.dastra.eu/en/features/questionnaires/types/lia.md) and [TIA](https://doc.dastra.eu/en/features/questionnaires/types/tia.md) questionnaires of the workspace. Click **Plan questionnaire** to create one.
* **Privacy by design** lists the processing creation request questionnaires. They [collect processing activity projects](https://doc.dastra.eu/en/features/trust-center/creation-questionnaires.md) from a Trust Center: once a response is validated, its data can become a processing activity.

## For more information

{% content-ref url="/pages/-Lvfac70bYn9YDhTkikw" %}
[Record of processing activities (ROPA)](https://doc.dastra.eu/en/gdpr/concepts/ropa.md)
{% endcontent-ref %}

{% content-ref url="/pages/zGkLmYam7IP9xxLigjAY" %}
[Attach a risk to a processing activity](https://doc.dastra.eu/en/features/risks/attach-to-processing.md)
{% endcontent-ref %}

{% content-ref url="/pages/-Lw3hALWsjvX2sseOt14" %}
[Planning](https://doc.dastra.eu/en/features/tasks.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/features/ropa.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.
