> 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 Learn how to configure the Record of processing activities in your Trust center #### Activating the 'Record of processing activities' Feature in Your Trust center To activate the 'Record of processing activities' feature in your Trust center, 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 Trust center. *** #### 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 Trust center will be publicly accessible for consultation by all visitors to your Trust center. Outside of activation, the record of processing activities does not require additional configuration to be displayed in your Trust center. --- # 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/privacy-hubs/configuration/record-of-processing-activities.md?ask=&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.