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

# FAQ

Frequently asked questions about the record of processing activities.

## How to display the history of modifications on a processing activity?

For all processing activities, you can display the history of modifications as well as the details of the changes.

Click the clock icon (**Activity history**) at the top of the processing activity page.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-afbe15798c2a1e9220373924e4ed5c2072e36d0a%2Fropa-faq-1.png?alt=media" alt="Activity history button at the top of a processing activity"><figcaption><p>History access button</p></figcaption></figure>

Click **Change details** on an entry to compare the versions. From there, a **Restore** button lets you go back to that version, if your role allows it.

Please note that changes in organizational units are not tracked.

## Is it possible to automatically add elements in the "stakeholders" field in a new processing activity?

No, stakeholders cannot be updated automatically through an automated workflow.

However, you can create a custom field at the stakeholder level, which can be modified through the automated workflow.

## How to delete a processing activity?

To delete a processing activity, you must first move it to the recycle bin with **Move to recycle bin**. Then, by displaying the recycle bin from the filters, you can delete the processing activity permanently. This is a safeguard against hasty deletions.

To move a processing activity to the recycle bin, open the menu at the end of its row and choose **Move to recycle bin**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-3f44bceec2ae984774a15743a94f0e414646a378%2Fropa-faq-2.png?alt=media" alt="Row action menu of a processing activity with the Move to recycle bin entry"><figcaption><p>Moving a processing activity to the recycle bin</p></figcaption></figure>

Then display the recycle bin: click **Filters** and tick **View recycle bin**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-432e0926ec1cb2bff7559abf9865ff21c6705ccc%2Fropa-faq-3.png?alt=media" alt="Filters panel of the record with the View recycle bin option"><figcaption><p>Displaying the recycle bin</p></figcaption></figure>

Finally, open the menu at the end of the row and choose **Delete**. You can also choose **Restore** to put the processing activity back in the 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-1a969809471b213d8c2f9c821489d60f5b1d0fd4%2Fropa-faq-4.png?alt=media" alt="Row action menu of a processing activity in the recycle bin with the Restore and Delete entries"><figcaption><p>Deleting a processing activity permanently</p></figcaption></figure>

## How can users work with datasets without being able to modify them?

Your DPO relays may need to use the datasets you provide in their processing activities without creating new ones or changing the data fields they contain, so that the links with other processing activities stay consistent.

In this case, create a custom role. Go to the roles: <https://app.dastra.eu/general-settings/roles> (see [Roles and permissions](https://doc.dastra.eu/en/features/settings/roles.md)).

Then create a custom role with the following permissions:

* **Data processing records**: Read, Write
* **Data mapping and repositories**: Read

Then assign this role to the users concerned. They will be able to use the datasets in their processing activities, but not to modify the elements of the data map.

## How to add stakeholders or recipients to several processing activities?

You can add stakeholders or recipients to several processing activities at once with batch actions.

In **List view**, select the processing activities with the checkboxes. The **Select a batch action** button appears.

Choose **Linking stakeholders**, select **Add**, choose the stakeholders, then their **Type** (for example stakeholder or recipient) and their category, and confirm. If your selection mixes data controller and processor activities, only the stakeholder type is available.

The same window, with **Delete** selected, removes stakeholders from the selected processing activities.

## How to get the list of assets per organizational unit?

You can get the list of assets per organizational unit through the links between assets and processing activities.

Use the Excel export of the processing activities: filter the record by organizational unit, select the processing activities and export them. In the export window, turn on **Export custom fields** and keep only the assets column: you get the assets of that organizational unit. You can also keep only the organizational unit and assets columns to get the assets of all organizational units at once.

The [record data map](https://doc.dastra.eu/en/features/ropa/visualization/data-map.md) also shows this information graphically.

## How to duplicate a record in another workspace?

You can duplicate a record and its processing activities in several ways:

* either by [exporting and re-importing](https://doc.dastra.eu/en/features/ropa/export-import.md) the processing activities in JSON format,
* or by going to the target workspace and creating the processing activities with **Create from library...**: in **Choose the library source**, select the workspace that holds the original record.

## How can I change my type of processing activity (from one created as a data controller to one created as a processor, and vice versa)?

Open the processing activity, click the arrow on the right of **Save changes**, then click **Switch to processor record** or **Switch to responsible of the processing**:

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-6cc1e47447eaea38257532588bc6f75ede2b7428%2Fropa-faq-7.png?alt=media" alt="Save changes menu with the Switch to processor record entry"><figcaption><p>Switching the type of a processing activity</p></figcaption></figure>

When you switch a processor activity back to a data controller activity, the clients linked to it are removed. A confirmation is requested beforehand.

## Error Message: "Label field is required."

This message typically appears when a field is left blank while answering a questionnaire.

## Error message : "Prohibited HTML content is present in a field !"

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fa05KLW1qnhhx34QfkwWl%2FCapture%20d'%C3%A9cran%202025-03-04%20165456.png?alt=media&amp;token=8206eef1-f316-4b83-8763-f758925114ff" alt="Error notification Prohibited HTML content is present in a field"><figcaption><p>Prohibited HTML content is present in a field !</p></figcaption></figure>

\
This message means that HTML code (usually enclosed in angle brackets `< >`) is present in a field where HTML is not allowed (for security reasons).<br>

\
The following message makes it easy to identify the affected field:

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2FyIr4x4ei3VdVecLPBKTr%2FCapture%20d'%C3%A9cran%202025-03-04%20165525.png?alt=media&amp;token=aad64bf1-3d89-42dc-af0a-edfda5846477" alt="Validation message pointing to the field that contains HTML"><figcaption><p>Prohibited HTML content is present in a field !</p></figcaption></figure>

## Error message: "Stakeholders provided does not exist in your current organization." when saving a data processing

The full message reads: "Stakeholders provided does not exist in your current organization. Please check the stakeholders section and remove users not related to your organization."

It means that a user who has been removed from your workspace is still set as an accountable user in the stakeholders of the data processing.

Remove the deleted user from the stakeholders of the data processing to resolve this issue.

{% hint style="info" %}
If you can't find the answer in this guide, you can [contact our support](https://doc.dastra.eu/en/getting-started/support/request.md).
{% 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/features/ropa/faq.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.
