> 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-nl/aan-de-slag-agencies/agency-dashboard.md).

# Agency Dashboard

Leer het gebruik van het Agency Dashboard voor het beheren van klantbedrijven, het monitoren van Problemen met je Account en het beheren van agencytoegang.

De **Agency Dashboard** is je centrale plek om klantbedrijven en agencygebruikers te beheren.

Voor het volledige Overzicht van het Agency Partner Program, begin met [Aan de slag als agency](/get-started/get-started-nl/aan-de-slag-agencies/ga-aan-de-slag-als-agency.md).

### Voordelen van het Agency Dashboard

* **Bekijk alle gekoppelde bedrijven:** Houd de klantbedrijven die je agency beheert in de gaten, allemaal vanuit één Overzicht.
* **Beheer de toegang binnen je team:** Agencygebruikers krijgen automatisch toegang tot gekoppelde bedrijven.
* **Reageer sneller op problemen:** Controleer accountfouten en neem actie zonder tussen accounts te schakelen.
* **Koppel bedrijven los wanneer dat nodig is:** Verwijder toegang netjes wanneer een klantrelatie eindigt.


---

# 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-nl/aan-de-slag-agencies/agency-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.