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

# Contacts

Learn how to display contacts in your Trust Center.

## Enable the feature

Check **Contacts** in the **Configuration** section, as explained in [Homepage and general configuration](https://doc.dastra.eu/en/features/trust-center/configuration/home.md). A **Contacts** section is then displayed in the sidebar of your Trust Center's homepage. It therefore only appears when the homepage is enabled.

Apart from enabling it, contacts require no additional configuration.

## Contacts display and impact of the organizational unit

The contacts shown in the sidebar include the DPOs, representatives within the European Union and legal representatives entered in the organizational unit associated with your Trust Center (see [Set up organizational units](https://doc.dastra.eu/en/getting-started/setup/organizational-units.md)). If there are any, they also include those of all child units of this unit.


---

# 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/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.
