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

# Configure your Trust Center

Discover the editing page of a Trust Center, how to publish it and how to display a compliance project.

This page presents the editing page of a Trust Center, explains how to publish it and describes how a compliance project is displayed. It is intended for the people who configure the portal.

## The editing page

The editing page is made of sections that you open or close with a click. The first three are always available:

* **Configuration**: the name, organizational unit, owners, welcome message, features to display and quick links. See [Homepage and general configuration](https://doc.dastra.eu/en/features/trust-center/configuration/home.md).
* **Security**: mandatory authentication, download approval and IP address filtering. See [Security](https://doc.dastra.eu/en/features/trust-center/configuration/security.md).
* **Design**: the logo, cover image and accent color. See [Appearance and design](https://doc.dastra.eu/en/features/trust-center/configuration/design.md).

The following sections unlock when the matching feature is checked in **Configuration**:

* **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).
* **Attachments**: see [Attachments](https://doc.dastra.eu/en/features/trust-center/configuration/attachments.md).
* **Compliance**: see [Display the compliance project](#display-the-compliance-project) on this page.

The other features are turned on with a checkbox, without a dedicated section: [Record of processing activities](https://doc.dastra.eu/en/features/trust-center/configuration/ropa.md), [Organizational chart](https://doc.dastra.eu/en/features/trust-center/configuration/org-chart.md), [Contacts](https://doc.dastra.eu/en/features/trust-center/configuration/contacts.md) and [AI systems](https://doc.dastra.eu/en/features/trust-center/configuration/ai-systems.md).

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

## Publish and cancel publication

A newly created Trust Center is a draft: the indicator at the top right of the page shows **The Trust Center is in Draft mode** and the portal is not accessible online.

To publish it:

1. Click **Publish**, at the top right of the editing page. The button is disabled while a required field is empty.
2. Confirm the question "Would you like to save and publish the Trust Center?". All changes are saved.

The indicator then shows **The Trust Center has been published** and the portal becomes accessible to anyone who has the link, within the rules of the **Security** section.

To make the portal inaccessible, click **Cancel publication**. This applies immediately, without confirmation. From the list of Trust Centers, the menu of each row also offers **Enable** and **Disable**.

## Display the compliance project

This feature adds a **Compliance** tab to the portal. It presents a summary of a compliance project: for each framework of the project, the active audit with its attachments and the applied controls. It requires the [Compliance](https://doc.dastra.eu/en/features/compliance.md) feature in your subscription.

### Choose the project to display

1. In the **Configuration** section, check **Display compliance project**.
2. Open the **Compliance** section.
3. In **Select the compliance project you want to display**, choose the project. A Trust Center displays one project.
4. Save, then publish the Trust Center if it is not published yet.

The **Compliance** section is flagged as an error until a project is selected.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-779a98dc4971c3d10bac9a7dfe7506294f02c3c8%2Ftrust-center-configuration-2.png?alt=media" alt="Compliance section with the compliance project selection list"><figcaption><p>Choosing the compliance project to display</p></figcaption></figure>

### What visitors see

The **Compliance** tab of the portal shows one card per framework on the left. Only the frameworks of the project that have an [active audit](https://doc.dastra.eu/en/features/compliance/projects/audits.md) are listed. When a visitor clicks a framework, the page presents:

* **Audit details**: the type, status, name and start and end dates of the active audit, then its attachments;
* **Contrôles**: the applied controls of the framework that are active and whose tests all pass. Each control shows its reference, title, description and the references of the requirements it answers.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-9530fdc9549de5324bea82ac98f31c7c46826b2e%2Ftrust-center-configuration-3.png?alt=media" alt="Compliance tab of the public portal with the list of frameworks, the audit details and the controls"><figcaption><p>The Compliance tab of the public portal</p></figcaption></figure>

To keep the portal up to date, set the active audit of each framework in the compliance project and keep the tests of your controls current. See [Audits](https://doc.dastra.eu/en/features/compliance/projects/audits.md).


---

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