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

# General information

In this section, indicate key information regarding the processing activity.

[**Article 30 of the GDPR**](https://gdpr-info.eu/art-30-gdpr/) requires each controller to keep a record of the processing activities under its responsibility. This record is the first element of "accountability" used to demonstrate compliance with the GDPR. The record of processing activities lets you list your data processing and gives you an overview of what you do with personal data.

The processing activity is the "umbrella" activity that covers all the purposes pursued within the framework of the activity.

For example, the "recruitment" activity could have two distinct purposes: the analysis of applications and the management of interviews, and the creation of a CV library.

The terms "processing activity" and "processing", often used interchangeably, can be understood in a similar way.

Article 4 of the GDPR defines processing as "*any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means*".

For example, it can be a database, an Excel spreadsheet, a video surveillance installation, a payment system by bank card or biometric recognition, a smartphone application, etc.

Processing of personal data may or may not be computerized.

[Read more](https://www.cnil.fr/en/record-processing-activities)

## Fill in the General section

The **General** section is the first section of a processing activity. It identifies the processing activity that you want to record in the register.

* **Name of the processing activity** (required, up to 120 characters): the name of the activity, which usually corresponds to the activity that involves one or more processing operations, such as customer management or event management.
* **Internal reference** (optional, up to 50 characters): your own identifier for this processing activity, if you have one.
* **Organizational unit** (required): the entity or department the processing activity belongs to. The data controller, its data protection officer and its representative shown in the **Parties involved** section are inherited from the entity of this organizational unit.
* **Tags**: classify the processing activity to find and filter it. While no tag is selected, the AI assistant can suggest tags based on the name and description of the processing activity.
* **Short description of the processing activity** (optional, up to 3,000 characters): describe the processing activity. Click **Generate** under the field to let the AI assistant draft the description from the name of the processing activity, then check the result and click **Apply**. When the field already contains text, the button becomes **Continue writing content**.
* **State of the processing activity** (optional): select the current state of the processing in your organization: **To study**, **Being deployed**, **In production** or **Stopped**.
* **Deployment date** (optional): available once a state is selected.

{% hint style="info" %}
The AI buttons are only available when the AI assistant is enabled for your organization.
{% 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/activity/general.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.
