> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/organizations/teams.md).

# Teams

A team groups people. While a team is enabled, every member holds the team's roles and permissions on top of their own, and work can be assigned to the team, for example a change approval or a remediation task, so any member can pick it up. Use this tab to create teams and manage their members, roles and permissions.

Open it from **Administration** → **Organizations** → **Teams** in the sidebar.

<figure><img src="https://content.gitbook.com/content/9vAxMuDrkUkB4OXlH9CL/blobs/kNSBLoBrzrIbIGMNtzRP/.gitbook%2Fassets%2Fv2-org-teams.png" alt="Teams tab with the list of teams, their members, roles, permissions, open work and status"><figcaption><p>Teams</p></figcaption></figure>

{% hint style="warning" %}
You need a role that can view roles to see Teams, and one that can create roles to create a team. Adding or removing members and roles needs a role that can assign roles; adding permissions needs one that can assign permissions.
{% endhint %}

## All Teams

Filter with **Status** (**All**, **Enabled** or **Disabled**) and **Search teams by name**. **Saved filters** and **Save filters** keep a filter combination; **Refresh**, **Columns** and **Export** work as on other lists.

| Column                 | Description                                                                                                                                             |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Team**               | The team name and when it was last updated. Click the name to open the team.                                                                            |
| **Members**            | How many people are in the team.                                                                                                                        |
| **Roles**              | How many roles every member holds through the team.                                                                                                     |
| **Permissions**        | How many permission grants every member holds through the team.                                                                                         |
| **Open work assigned** | How much open work is assigned to the team: change approvals, maintenance or review items, upgrade items, release sign-off steps and remediation tasks. |
| **Status**             | **Enabled** or **Disabled**.                                                                                                                            |
| **Actions**            | **Edit team** (or **View team**) opens the team; **Disable team** or **Enable team**.                                                                   |

{% hint style="info" %}
Teams are disabled, not deleted, so the history and evidence that name them stay intact.
{% endhint %}

## Create a Team

1. Click **Create team**.
2. Enter the **Team name**, for example "Platform operations". Use a name people recognise when work is assigned to it.
3. Click **Next: members** and tick the people to add. Only enabled people are listed; your ticks are kept across pages and searches.
4. Click **Next: roles** and tick the roles every member should hold.
5. Click **Next: permissions** and choose permissions, and where they apply, that every member should hold.
6. Click **Create team**.

Members, roles and permissions are optional; you can add them later from the team's page. A team can have up to 500 members. The steps you cannot use without the right permission are left out, and the form says so. If the team is created but something could not be added, a message says what to add from the team's tabs.

## Manage a Team

Open a team to manage it on its own page. **Teams** in the breadcrumb returns to the list.

| Tile                   | Description                                        |
| ---------------------- | -------------------------------------------------- |
| **Members**            | People in the team.                                |
| **Roles**              | Roles held by every member.                        |
| **Permission grants**  | Permissions held by every member, in their scopes. |
| **Open work assigned** | The open work assigned to the team, by kind.       |

The tabs list the team's contents:

| Tab                           | Description                                                                                                                                                                                                  |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Members (*****N*****)**     | Each member with **Email**, **Account**, **Sign-in method** and **Last sign-in**. Filter by **Account** and **Sign-in method**. **Remove from team** removes a member; their own roles and permissions stay. |
| **Roles (*****N*****)**       | The roles every member holds through the team, with **Type** and **Role status**. A disabled role gives nothing. **Remove from team** removes a role; anyone who holds it directly keeps it.                 |
| **Permissions (*****N*****)** | The permissions every member holds through the team, with their **Module** and where they apply (**Across the tenant**, an organization or an environment). **Remove from team** removes a grant.            |

**Rename team** changes the name. **Record identity** shows the team's identifier.

Changes take effect from each member's next request. To see everything a person holds through their teams, open the person in [Users](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/organizations/users.md) and go to **Through teams**.

## Disable or Enable a Team

1. Click **Disable team** (or **Enable team**) on the row or on the team's page.
2. Review what changes, including the open work assigned to the team.
3. Confirm with **Disable team** (or **Enable team**).

{% hint style="danger" %}
While a team is disabled, its members stop holding its roles and permissions (unless they hold them another way), nobody can work what is assigned to it, and it cannot be given new work. Members, roles and permissions are kept, so enabling the team restores them. Reassign urgent work in **Assigned work** first.
{% endhint %}

## Next Steps

* [Roles](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/organizations/roles.md): create the roles a team gives its members.
* [Users](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/organizations/users.md): see what a person holds through their teams.
* [Organizations](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/organizations.md): the other tabs.


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/organizations/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.
