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

# Homepage and general configuration

The **Configuration** section of a Trust Center's editing page gathers the essential options: name, organizational unit, owners, features to display, quick links and welcome message.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-d8b6e6070b2f8a329ed153f016e9bbdb408eabf0%2Ftrust-center-home-1.png?alt=media" alt="Configuration section of the editing page of a Trust Center"><figcaption><p>The Configuration section of a Trust Center</p></figcaption></figure>

## Trust Center label

The name of the Trust Center appears in the header and on every page of your portal. It is required.

## Organizational unit

Link your Trust Center to an organizational unit, in the **Entity** field. This choice determines the data that each enabled feature publishes. For the details of its effect, see the page of each feature. Questionnaire responses given from the Trust Center are also saved in this unit.

Visitors can narrow the display down to part of this scope with the **Organizational unit** selector, available on the record of processing activities and AI systems pages. It appears when the Trust Center's unit has child units. It shows the tree of published units, that is the Trust Center's unit and its child units, and offers a search by name. Once a unit is chosen, the page only lists the items of that unit and its child units, combined with the other filters.

The selector only narrows the display: the published scope remains that of the organizational unit configured here.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-c29b96e08145d5ee8d2063bdf84d78bfe3bc858c%2Ftrust-center-unit-selector.png?alt=media" alt="Organizational unit selector on the AI systems page of a Trust Center"><figcaption><p>Narrowing the Trust Center display down to an organizational unit</p></figcaption></figure>

## Owners

The **Owners** field is optional. Owners are the people responsible for the Trust Center. They receive its notifications and handle document access requests. For the rules that apply when no owner is set, see [Security](https://doc.dastra.eu/en/features/trust-center/configuration/security.md).

## Features to display

In **Choose the features to display in the Trust Center**, check the features to publish. A greyed-out box is a feature that your subscription does not include. The information icon of each box summarizes what the feature adds to the portal.

* **Homepage**: see below.
* **Questionnaires**: see [Questionnaires](https://doc.dastra.eu/en/features/trust-center/configuration/questionnaires.md).
* **Data subject requests**: see [Data subject requests](https://doc.dastra.eu/en/features/trust-center/configuration/data-subject-requests.md).
* **Record of processing activities**: see [Record of processing activities](https://doc.dastra.eu/en/features/trust-center/configuration/ropa.md).
* **AI systems**: see [AI systems](https://doc.dastra.eu/en/features/trust-center/configuration/ai-systems.md).
* **Attachments**: see [Attachments](https://doc.dastra.eu/en/features/trust-center/configuration/attachments.md).
* **Organizational chart**: see [Organizational chart](https://doc.dastra.eu/en/features/trust-center/configuration/org-chart.md).
* **Contacts**: see [Contacts](https://doc.dastra.eu/en/features/trust-center/configuration/contacts.md).
* **Display compliance project**: see [Display the compliance project](https://doc.dastra.eu/en/features/trust-center/configuration.md#display-the-compliance-project).

Features that need setup unlock a section on the editing page. For the others, the checkbox is enough.

## Homepage

The homepage is optional. When the **Homepage** box is unchecked, the **Home** tab does not appear in the portal, and the welcome message, quick links and contacts are not displayed. The **Quick links** and **Welcome message for your Trust Center** fields are then greyed out.

### Quick links

Click **Add a quick link** to create a shortcut to a resource, for example your website or your privacy policy. A Trust Center accepts up to 20 links. Each link has:

* an emoji, optional;
* a **Label**, required, up to 70 characters;
* a **Shortcut url**, required.

Links appear in a side menu of the homepage. A link to another site opens in a new window.

### Welcome message

The **Welcome message for your Trust Center** field is a rich text editor. It lets you format the text and include images or videos. The message is displayed on the homepage of the portal.


---

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