> 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/privacy-hubs/configuration/record-of-processing-activities.md).

# Record of processing activities

#### Activating the 'Record of processing activities' Feature in Your Privacy hub

To activate the 'Record of processing activities' feature in your Privacy hub, refer to the general configuration section where you can enable or disable this option. Once activated, a new public page titled 'Record of processing activities' will be added to your Privacy hub.

***

#### Register Display and Impact of Organizational Unit Selection

Once the feature is activated, the processing activities with a **'published'** status and belonging to the same organizational unit as your Privacy hub will be publicly accessible for consultation by all visitors to your Privacy hub.

Outside of activation, the record of processing activities does not require additional configuration to be displayed in your Privacy hub.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.dastra.eu/en/features/privacy-hubs/configuration/record-of-processing-activities.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.