> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/dokumentation/settings/theme.md).

# Theme

Adapting the app's appearance to your company: primary color, favicon, app title, logos, toolbar color gradient and button colors.

**Path:** Settings → **"Theme"**

With the theme you adapt equipme to your own corporate design. The theme applies to **all users** of the company as well as to emails and documents.

| Area                  | Setting                                                                                                                               | Requirements                                                   |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
| **"Primary color"**   | Main color for the greeting, highlights and counters; also colors the toolbar and buttons as long as nothing separate is set for them | Live preview                                                   |
| **"Favicon & title"** | Icon in the browser tab                                                                                                               | **PNG** only, square, at least **512 × 512 px**                |
|                       | **"App title"**: name in the browser tab                                                                                              | Required, max. 45 characters, default "equipme App"            |
| **"Logos & Toolbar"** | **Logo for white background**, mainly for emails and documents                                                                        | jpg, png, svg or webp, at least 400 px wide, max. approx. 4 MB |
|                       | **Contrast logo**: easy to read on the primary color, for the toolbar                                                                 | as above                                                       |
|                       | **"Toolbar color gradient enabled"**: gradient with "Degree", "Start color", "Final color" and optionally "Transition color"          | "Preview"                                                      |
| **"Button colors"**   | **"Button theming active"**: custom colors for the states "Default", "Hover", "Active" and "Disabled"                                 | Preview filled/outlined                                        |

With **"Save"** you apply the theme for all users. **"Delete"** restores the default theme (for hosted customers, the provider's theme).

{% hint style="info" %}
The theme does not distinguish between light and dark mode. Check the colors in both modes if necessary.
{% endhint %}

During registration, equipme can automatically suggest a logo and colors based on the web domain. After that, you maintain the theme here.


---

# 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://hub.equipme.io/dokumentation/settings/theme.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.