# Organize people into teams

> Source: https://elaichi.ai/docs/guides/members/teams/

A **team** is a named group of members. Use it whenever you’d rather grant access once to a group than pick people one by one.

**Where to find it:** **Members & Roles → Teams**

You need the **Manage teams** permission (`team:manage`) to create, edit, delete teams, or change membership. Roles still decide what each person is allowed to *do*; teams decide who they share *with*.

## What teams are for

| Use | What you pick |
| --- | --- |
| **Connection ownership** | Own a connection at **team** scope so the group shares one authorized account. |
| **Toolbox sharing** | Share a toolbox with a team (access levels **view** / **use** / **edit**). |
| **Custom connector sharing** | Share a custom connector with a team (**view** / **edit**). |
| **Offboarding / transfer** | Move a leaving member’s personal connection to a team so shared toolboxes keep working. |

People can belong to many teams. Teams are not roles — a Viewer on the Platform team still can’t connect accounts unless their roles allow it.

## Create a team

1. Open **Members & Roles → Teams**.
2. Choose **New team** (or equivalent create action).
3. Enter a **name** and optional **description**.
4. Save.

**You'll know it worked when:** The team appears in the Teams list.

Membership is edited after create — open the team to add people.

## Add or remove members

1. Open the team from the list.
2. Under **Members**, choose someone from the organization and **Add**.
3. Remove someone with the remove control on their row.

Only existing organization members can be added. Invite people under **People** first if they aren’t in the org yet. If everyone is already on the team, the picker says so.

Team membership shows up on each person’s row under **People**.

## Use a team when connecting or sharing

### Own a connection as a team

When you [connect an account](/guides/connections/connecting-an-account), choose **team** as the owner (requires `connection:create_shared`). Everyone on that team can use the connection according to their roles and any restrictions.

You can also [transfer](/guides/connections/transferring-and-offboarding) an existing personal connection to a team later.

### Share a toolbox with a team

When sharing a toolbox, pick the team as the grantee and set the access level:

| Level | Meaning |
| --- | --- |
| **view** | See the toolbox definition. |
| **use** | Use it (including through MCP when they instantiate or are granted use). |
| **edit** | Change entries and settings. |

Sharing still requires the **Share toolboxes** permission (`toolbox:share`) plus standing on that toolbox.

## Delete a team

From the Teams list, delete a team you no longer need. Before you delete, check whether any connections are owned by that team or any shares point at it — re-home those first so nothing is left pointing at a removed group.

## Good to know

- `team:manage` is enough to edit membership; it does not grant org-wide admin powers.
- Creating **team- or org-scoped** connections also needs `connection:create_shared`.
- Roles answer “may this person invite / connect / manage SSO?” Teams answer “is this person in Platform / Support / Finance?”
- Domain join and SCIM add people to the organization; put them on teams afterward (or map groups via SCIM where you’ve set that up).

## Related

- [Invite and manage people](/guides/members/invite-and-manage-people)
- [Roles and permissions](/guides/members/roles)
- [Connect an account](/guides/connections/connecting-an-account)
- [Transfer and offboard](/guides/connections/transferring-and-offboarding)
- [Share a toolbox with your team](/guides/toolboxes/shared-toolboxes)