> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/setup-and-admin/business-hubs/managing-your-business-hubs/view-the-managers-of-your-business-hub.md).
# View the managers of your business hub
This article describes the information of the Managers tab for a business hub.
{% hint style="info" %}
**Who can use this feature?**
* Business hub **Owners**
* Only supported using the Cerby web app
{% endhint %}
The **Managers** tab, accessible through your business hub details page, provides a centralized view of your business hub managers.
Your business hub managers are grouped into two independent tables, **Users** and **Teams**, each with relevant details to help you manage access efficiently, as shown in **Figure 1.**
Figure 1. Managers tab in the business hub details page
The **Users** table provides information about the individual users with access to manage the business hub in the following columns:
* **Managers:** It lists the username and email of the users.
* **Role:** It lists the roles assigned to the users on the business hub integration.
* **Resource:** It indicates the method by which the users were granted access to manage the business hub integration.
* **Last used:** It is the date and time of the user's most recent activity.
* **Status:** It indicates if the manager has a seat assigned in the external app. If the manager has no status chip, they are non-seated or don't have a seat assigned in the external app.
The **Teams** table provides information about the teams with access to manage the business hub in the following columns:
* **Teams:** It lists the names of the teams.
* **Role:** It lists the roles assigned to the teams on the business hub integration.
* **Type:** It indicates the resource through which the team was granted access. For example, account or collection.
---
# 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://help.cerby.com/setup-and-admin/business-hubs/managing-your-business-hubs/view-the-managers-of-your-business-hub.md?ask=&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.
