> 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/nl/features/trust-center/configuration/contacts.md).

# Contacten

Leer hoe u contacten weergeeft in uw Trust Center.

## De functie activeren

Vink **Contacten** aan in de sectie **Configuratie**, zoals uitgelegd in [Startpagina en algemene configuratie](https://doc.dastra.eu/nl/features/trust-center/configuration/home.md). Er wordt dan een sectie **Contacten** weergegeven in de zijbalk van de startpagina van uw Trust Center. Ze verschijnt dus alleen als de startpagina is geactiveerd.

Afgezien van de activering is er geen extra configuratie nodig om contacten weer te geven.

## Weergave van de contacten en impact van de organisatorische eenheid

De contacten in de zijbalk omvatten de functionarissen voor gegevensbescherming (FG's), vertegenwoordigers in de Europese Unie en wettelijke vertegenwoordigers die zijn opgegeven in de organisatorische eenheid die aan uw Trust Center is gekoppeld (zie [Organisatorische eenheden aanmaken en instellen](https://doc.dastra.eu/nl/getting-started/setup/organizational-units.md)), evenals, in voorkomend geval, die van alle onderliggende eenheden van deze eenheid.


---

# 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/nl/features/trust-center/configuration/contacts.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.
