> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/get-started/get-started-space-de/loslegen-agenturen/agentur-dashboard.md).

# Agentur-Dashboard

Erfahre, wie du das Agentur-Dashboard nutzt, um Kundenunternehmen zu verwalten, Account-Probleme zu überwachen und den Agenturzriff zu steuern.

Das **Agentur-Dashboard** ist dein zentraler Ort, Zu verwalten von Kundenunternehmen und Agenturnutzern.

Für die vollständige Übersicht zum Agency Partner Program beginne mit [Starte als Agentur](/get-started/get-started-space-de/loslegen-agenturen/als-agentur-loslegen.md).

### Vorteile des Agentur-Dashboards

* **Sieh dir alle verbundenen Unternehmen an:** Überwache die Kundenunternehmen, die deine Agentur verwaltet, alle von einer Ansicht aus.
* **Verwalte den Zugriff im gesamten Team:** Agenturnutzer erhalten automatisch Zugriff auf verbundene Unternehmen.
* **Reagiere schneller auf Probleme:** Überprüfe Account-Fehler und nimm Maßnahmen, ohne zwischen Accounts zu wechseln.
* **Trenne Unternehmen bei Bedarf:** Entferne den Zugriff sauber, wenn eine Kundenbeziehung endet.


---

# 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://helpcenter.channable.com/get-started/get-started-space-de/loslegen-agenturen/agentur-dashboard.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.