> 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/features/trust-center/configuration/record-of-processing-activities.md).

# Registre des traitements

Apprenez à paramétrer un registre des traitements dans votre Trust center

**Activation de la fonctionnalité 'Registre des traitements' dans votre** Trust center

Pour activer la fonctionnalité '**Registre des traitements**' dans votre Trust center, consultez la section de configuration générale qui permet d'activer ou de désactiver cette option. Une fois activée, une nouvelle page publique intitulée 'Registre des traitements' sera ajoutée à votre Trust center.

En dehors de l'activation, le registre des traitements ne nécessite pas de configuration additionnelle pour s'afficher dans votre Trust center.

#### Affichage du registre et impact du choix de l'unité organisationnelle

Dès que la fonctionnalité est activée, les traitements ayant le statut 'publié' et appartenant à la même unité organisationnelle que votre Trust center seront accessibles publiquement pour consultation par tous les visiteurs de votre 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/features/trust-center/configuration/record-of-processing-activities.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.