> 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/getting-started-agencies/agency-dashboard.md).

# Agency Dashboard

Learn how to use the Agency Dashboard to manage client companies, monitor account issues, and control agency access.

The **Agency Dashboard** is your central place to manage client companies and agency users.

For the full Agency Partner Program overview, start with [Get started as an agency](/get-started/getting-started-agencies/get-started-as-an-agency.md).

### Agency Dashboard benefits

* **See all connected companies:** Monitor the client companies your agency manages, all from one view.
* **Manage access across your team:** Agency users automatically get access to connected companies.
* **Respond faster to issues:** Review account errors and take action without switching between accounts.
* **Disconnect companies when needed:** Remove access cleanly when a client relationship ends.


---

# 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/getting-started-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.
