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

# Appearance and design

Learn how to configure the logo, cover image and accent color of your Trust Center.

The **Design** section of the editing page gathers the visual elements of your Trust Center: the logo, the accent color and the cover image. All three are optional.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-18d27fe94f7e5e364a71c198edd79e359da5641e%2Ftrust-center-design-1.png?alt=media" alt="Design section of a Trust Center with the logo, the accent color and the cover image"><figcaption><p>The Design section of a Trust Center</p></figcaption></figure>

## Logo

Add the logo of your choice, in square format. It appears in the header of the Trust Center, next to its name. Without a logo, only the name of the Trust Center is displayed.

## Accent color

The **Accent color** field colors the interactive elements of the public portal: links, the active tab, primary buttons and the active page of lists. Without a color, the portal uses its default color.

## Cover image

Add a cover image, in rectangular format (2:1 proportions). It appears at the top of the Trust Center header, above the logo and the name.


---

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