> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/organizational-setup/user-onboarding-guide/teams/create-and-view-the-exec-team.md).
# Create and View the Exec Team
An Exec Team shows aggregated metadata from selected BI connectors to generate a unified insights dashboard. This enables comparison of licenses and user activity across BI systems.
## Create an Exec Team
Follow these steps to create a team and added users to it.
1. Go to **Settings** > **Teams.**
2. Go to the Exec Team tab.
3. Select one or many connectors. All contexts will be automatically included.
4. Select users that should have access to the team.
## View the Exec Team
The Exec Team appears in the side navigation under the name **Admin Team**. Selecting this team opens the BI 360 view of your BI tenants. From the dropdown, you can choose which information to display on the dashboard—either insights for a single BI connector or aggregated insights across multiple connectors.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.datalogz.io/guides/organizational-setup/user-onboarding-guide/teams/create-and-view-the-exec-team.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.