> 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.md).

# Teams

Teams scope Control Tower to a subset of your BI estate. A team is linked to a single BI connector and covers the platform contexts you select, such as your production Power BI workspaces or a set of Tableau projects. Each team gets its own monitors, inventory, and insights; for Power BI teams, BI Similarity (preview) is also available.

Group people into teams by domain (for example Finance or Marketing), by collaboration, or by access level (for example Executives or Global Admins). Team members see and manage the content their team owns.

<figure><img src="https://1435452537-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI51V8nP3ZjMKt2bCO9HR%2Fuploads%2FBF4nBPg1cUPeIiaKlP3x%2FScreenshot%202025-12-12%20at%2022.00.12.png?alt=media&amp;token=4e098274-509e-43b3-bd78-afe2558be66f" alt=""><figcaption></figcaption></figure>

### Access Control.

Users and Groups can be added to a team so they can view and interact with that team’s monitors, alerts, and assets. Users with the **BI Viewer** and **BI Admin** roles can access all the teams as a member or admin, respectively.

<br>

<br>


---

# 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://docs.datalogz.io/guides/organizational-setup/user-onboarding-guide/teams.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.