> 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-view-or-delete-a-team.md).

# Create, View or Delete a Team

This page covers creating, viewing, and deleting teams. Each team is linked to a single BI connector and has its own monitors, inventory, and insights.

{% hint style="info" %}
When onboarding is complete, Datalogz automatically creates a default team with the highest level of privileges for your organization. This team ensures that administrators have immediate access to manage users, teams, and permissions.
{% endhint %}

### Users and actions they can do

* **Root Users** can create and split teams. They can also invite members.
* **Admins** can create new teams and invite members.
* **All users** can belong to one or more teams.

## Create a Team

Follow these steps to create a team and add users to it.

1. Go to **Settings** > **Teams.**
2. Click **New Team**. 
3. Give the team a name.
4. Select a connector. You can assign only one connector to one team at a time. 
5. Select the **Platform Context**. These are specific to the selected BI connector, for example Power BI workspaces or Tableau projects. Use one of the following ways to find what you are looking for:
   1. Scroll through the list to find the platform context you want to add to your team.
   2. Select **Always use all \[platform contexts]** to automatically include all workspaces, projects, streams or library folders (depending on the selected BI tool).
   3. Use the search bar to find platform contexts using an expression like `[name] contains ""`. ![](https://1435452537-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI51V8nP3ZjMKt2bCO9HR%2Fuploads%2F9XgSggtcm5vYSP7Zx28a%2FScreenshot%202025-10-21%20at%2020.30.05.png?alt=media\&token=6f7e7535-8e17-4bd0-b78d-e2dfc9ccd379)
6. Select users that should have access to the team.
7. Click **Create Team**.

## View Teams and Team Activity

All teams you have access to appear in a dropdown menu in the side navigation, and team updates are also displayed on your home page. Teams are only visible if you have access to them. If you are an admin, you can also track the Teams activity on the home page.

![](https://1435452537-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI51V8nP3ZjMKt2bCO9HR%2Fuploads%2FeJgtfYa78JBFquziiOAs%2FScreenshot%202025-09-08%20at%2017.41.34.png?alt=media\&token=b5ef0dc6-49ff-4bc2-9bd6-3cbe924842af)

## Delete a Team

Follow these steps to permanently delete a team from your Datalogz Control Tower.

* Go to **Settings** > **Teams.**
* Click the team you want to delete. 
* Click **Delete**.

{% hint style="warning" %}
Deleting a team does not remove its users. However, it will permanently delete all connectors and platform contexts associated with the team. This action cannot be undone, and the data cannot be recovered.
{% endhint %}


---

# 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/create-view-or-delete-a-team.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.