> For the complete documentation index, see [llms.txt](https://documentation.panomics.bio/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.panomics.bio/documentation/access-control/concepts/teams.md).

# Teams

Teams are ways to group user accounts into addressable entities in Panomics' access granting system. Teams enable powerful access definition strategies and workflows.

A user can belong to **any number of teams**.

## What teams enable

* Grant **Organization-level** permissions for system-wide management
* Reuse teams across Projects and Analyses for consistent access patterns
* Combine with **system teams** like **All Users** and **Guest** for internal-public and guest workflows
* Create specialized teams for different roles (e.g., Biologists, Data Managers, External Partners)

{% hint style="info" %}
Behind the scenes, even organizations are resources that parent every other resource. This enables teams with `admin` permissions on the Organization to have unrestricted access to **everything** in the organization.
{% endhint %}

## Organization-level permissions

<figure><img src="/files/uqyFPqFYIfaTuaCZ0siW" alt="Team details page showing organization-level permissions section"><figcaption><p>Organization Permissions</p></figcaption></figure>

Teams can be granted permissions that range from enabling management of various parts of the organization to enabling specific features. These permissions mirror the functionality that the previous Role system used to have in Panomics.

<details>

<summary>What organization-level permissions include</summary>

Organization-level permissions cover:

* **User management** - Adding/removing users, managing user profiles
* **Team management** - Creating and managing teams
* **Organization settings** - Configuring organization-wide settings
* **Billing and credits** - Managing billing accounts and credits
* **Collections and metadata** - Managing organization-wide collections
* **External drives** - Managing external drive connections
* **Bio-App management** - Managing organization-wide Bio-Apps

</details>

The **Inherited Permission** section allows you to grant less powerful administrator access to teams, pertaining to either only Projects (including their Analyses) or Bio-Apps.

{% hint style="info" %}
See [System Teams](/documentation/access-control/system-teams.md) for information about special teams like **All Users** and **Guest** that are automatically managed by Panomics.
{% 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 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://documentation.panomics.bio/documentation/access-control/concepts/teams.md?ask=<question>&goal=<endgoal>
```

`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.