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

# Declare a processing activity

Learn how to report a data processing activity.

## Definition of a processing activity

A processing activity is an operation or set of operations performed on personal data, such as payroll management. All processing activities taken together make up the record of processing activities.

## Create a processing activity

To create a processing activity, open the record of processing activities and click **Create data processing**. The **Processing activity creation** window offers four options:

* **AI Generated**: describe your processing activity in a few words and let our AI Assistant (Beta) generate it for you, when this feature is enabled in your workspace. The AI button next to **Create data processing** opens this option directly.
* **Built-in template**: start from one of our predefined templates (see [Use a processing activity template](https://doc.dastra.eu/en/features/ropa/templates.md)).
* **From an asset**: create a processing activity from an asset and its associated data.
* **Personalized**: create a new processing activity from scratch.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-9a980637b084cbb2f7ccf9bc729c7a0fb78c7a60%2Fropa-declare-1.png?alt=media" alt="Processing activity creation window with its four creation options"><figcaption><p>Choosing how to create the new processing activity</p></figcaption></figure>

With **Personalized**, enter the **Name of this processing activity**, select the **Organizational unit** and click **Create data processing**. You are then taken to the questionnaire, where you can add all the required information.

## Create a processing operation as a data processor

Creating a processing activity as a processor is very simple: when you create it with **Personalized** (or **AI Generated**), turn on the **This activity is carried out as a processor** switch.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-1effa7f59192910451e90eb94daaf42f7243a48e%2Fropa-declare-2.png?alt=media" alt="Switch This activity is carried out as a processor in the creation window"><figcaption><p>Creating a processing activity as a data processor</p></figcaption></figure>

You then go straight to the documentation of a processing activity as a data processor, where you can declare your data controllers (usually your clients) in the **Controllers** section.

## Modify a data processing

To modify an existing processing activity, click its row in the record, or open the menu at the end of the row and choose **Edit**:

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-8190f1917a317822d47d2f0564ebeb1bf30465b1%2Fropa-merge-1.png?alt=media" alt="Row action menu of a processing activity with the Edit entry"><figcaption><p>Opening a processing activity for editing</p></figcaption></figure>

The sections of the questionnaire are listed on the left of the screen: click a section to go straight to it, or use the **Back**, **Go to section** and **Next** buttons at the bottom of the page. Click **Save changes** to save your work.

Then follow each step of the questionnaire, starting with the next section:

{% content-ref url="/pages/-LvMDW-VMCrzSDNt2PC8" %}
[Complete a data processing activity](https://doc.dastra.eu/en/features/ropa/activity.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/declare.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.
