> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/docs/de/user-interface.md).

# Benutzeroberfläche

Die Benutzeroberfläche ist die visuelle und interaktive Ebene des Systems. Sie hilft Benutzern, zu navigieren, auf Funktionen zuzugreifen und Aufgaben effizient zu verwalten.

Dieser Abschnitt stellt die Kernelemente vor, die im gesamten Produkt sichtbar bleiben, um eine nahtlose Interaktion zu gewährleisten.

## Kernelemente der Benutzeroberfläche

* [Header-Leiste](/docs/de/user-interface/the-header-bar.md) – Immer oben sichtbar; schneller Zugriff auf Kanal, A/B Tests, globale Aktionen und das Benutzermenü.
* [Seitenleiste](/docs/de/user-interface/the-side-bar.md) – Primäre Navigation, organisiert nach Abschnitten und Funktionen; unterstützt benutzerdefinierte Menüs.
* [Konfigurationen bearbeiten / Transaktionen verwalten](/docs/de/user-interface/editing-configurations-managing-transactions.md) – Wie man den Bearbeitungsmodus aufruft, Einstellungen sperrt und Änderungen verwaltet.


---

# 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://docs.fact-finder.com/docs/de/user-interface.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.