> 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/org-chart.md).

# Organizational chart

Learn how to display your organizational chart in your Trust center

#### Activating the 'Organizational chart' Feature in your Trust center

To activate the 'Organizational Chart' 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 'Organizational chart' will be added to your Trust center.

#### Displaying the Organizational chart and impact of organizational unit selection

Once the feature is activated, the organizational chart of the organizational unit associated with your Trust center (including this unit and all its sub-units) will be displayed on the 'Organizational hart' page of your Trust center.

Outside of activation, no additional configuration is required for the organizational chart 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/org-chart.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.