# Teams

> Create a team, bring in your existing workspace, invite teammates, and manage seats, roles, ownership and session visibility.

A team gives several people one Estelle workspace. Teammates can work from shared repositories, memories and sessions, with one Team plan and one pooled usage balance. Provider keys and workspace-wide settings are shared too.

Choose a team when people need the same context and administrative controls, not merely separate accounts for the same company. Teams are part of the Team plan.

## Create your team

Buying a Team plan can create the team during checkout. If your plan is active but no team exists yet, create it from the dashboard:

### Open Team

Go to **Settings → Team** and choose **Create a team**.

### Name it

Enter a **Team name** and choose **Create team**. You become the team's owner and an admin.

### Share your existing workspace

Creating from your workspace brings your repositories, memories and sessions into the team. If you already had a team without that content, the owner can choose **Bring my workspace into the team** when that offer appears.

### Update tools that use your original key

When your workspace becomes the team's, your account's original primary API key stops working. If you have no other working key, Estelle shows a replacement once. Copy it and update your CLI, MCP clients and scripts.

**Limit:**
A replacement key is shown only once and cannot be recovered later. If you dismiss it, create another key in **Settings → API keys**. Workspace adoption retires the original key; inviting someone alone does not.

The adoption offer is available only for a team that can still accept the owner's workspace. A team with memory of its own cannot be replaced this way.

## Invite teammates

An admin can invite people from **Settings → Team**:

1. Under **Invite by email**, enter the person's address and choose **Send invite**.
2. The invitee opens the email link, signs in or creates an account with that same address, then chooses **Join**. Signing in alone does not join the team.
3. The member appears on the roster after they accept. Until then, the invitation remains under **Pending invites**.

The emailed link works once and expires after seven days. **Resend** sends a fresh link; **Revoke** withdraws an invitation that is no longer needed.

A pending invitation does not use a seat. A seat is used when the person joins. The page shows your pending-invite allowance and explains when an invite or acceptance is blocked by capacity.

## Manage seats

Only the team owner can change seats because they are billed to the owner's subscription.

1. Check **Seats** on **Settings → Team** for used, purchased and available seats.
2. Enter the new total and choose **Update seats**.
3. Review the prorated change on your next invoice.

You cannot reduce seats below the current member count. If every seat is full, the owner must add one before another invitee can join.

## Roles and what they can change

| Role | Use it for |
|---|---|
| **Member** | Everyday work: shared memory, search, agents within the applicable autonomy rules, runs and activity. |
| **Admin** | Member work plus invitations, member removal, role changes, shared provider keys, webhooks and team settings. |
| **Owner** | The billing account holder. The owner also changes seats and transfers ownership. Their role stays pinned to admin. |

Use **Make admin** or **Make member** on the roster to change a role. To remove an admin, first make them a member, then choose **Remove**. Removing a member ends their access to the shared workspace.

## Control who can see sessions

Open **Settings → Sessions & agent → Who can see sessions**. For each supported session kind, choose **Everyone**, **Admins** or **Only the owner**. Use **Per person** when one teammate needs a different rule.

These choices apply to sessions on the board and the other session views named on the page. A person can always see their own sessions. Only an admin or the owner can change visibility.

## Transfer ownership or leave

The owner can transfer the team to an existing member under **Ownership and leaving**. The new owner needs an active Team plan because billing, seats and capacity move with ownership. Shared memory stays in place.

A non-owner can choose **Leave team** and confirm. Leaving ends access to the shared workspace and frees the seat. The owner must transfer ownership before leaving.

## Related

- [Plans and credits](https://docs.fatelabs.ca/plans): How Team seats and shared usage work.
- [Keys and models](https://docs.fatelabs.ca/keys-and-models): Replace retired keys and manage shared provider keys.
- [Autonomy](https://docs.fatelabs.ca/autonomy): Choose what agents may do without a review click.