> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/structural-user-access/managing-organization-teams/about-teams.md).

# About teams

Every user or SSO group belongs to a team within their organization.

## What's managed in a team?

The following Structural features are managed within teams:

* **Workspaces -** All workspaces belong to a specific team, and can only be shared with team members. Workspace permission sets are also managed within the team.
* **Generator presets -** All generator presets are configured within a team. A team can only view, configure, and use their own generator presets.
* **Sensitivity rules -** All custom sensitivity rules are configured within a team. A team can only view, configure, and use their own sensitivity rules.
* **Secrets managers -** All secrets managers are configured within a team. A team can only view, configure, and use their own secrets managers.

## Default team

All organizations have a Default team. Every new organization user and SSO group is added to the Default team.

## How teams are managed

The built-in Admin and Account Admin global permission sets include the permission to assign team administrators, who are granted the Team Admin team permission set.

Within their team, a team administrator can add and remove team members and assign team permission sets.


---

# 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.tonic.ai/app/structural-user-access/managing-organization-teams/about-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.