# Teams

> Work on shadcn/ui design systems together in a DS Manager team. Create a team, invite people with links, give each person a role, move systems in, and pay per seat.

Canonical: https://www.shadcndesign.com/docs/ds-manager-teams

A team is a workspace that several people share. Its design systems and published registries belong to the team, so everyone in it works on the same systems and nobody has to pass a system around or republish it from their own account. Each person has a role that decides what they can change. Team is a paid plan: $19 per paid seat a month, or $180 per paid seat a year. See [Plans and limits](/docs/ds-manager-plans#team-plan).

![Settings, Team for Northwind Studio: the seat line with 4 paid seats at $180 a year each, the members with their roles Owner, Admin, Editor and Viewer, a pending invite with Copy link and Revoke, and Invite people](https://www.shadcndesign.com/docs/ds-manager/team-members.webp)

## What a team is

Every account has a **Personal** workspace. It holds the systems you make on your own, and it stays yours whatever teams you join. A team is a second kind of workspace, with members. Systems and registries belong to one workspace at a time.

- When you join a team, your Personal systems stay in Personal. Nothing moves unless you move it.
- When you leave a team or someone removes you, you lose access to the team's systems, and your Personal systems stay as they are.
- You can be in several teams, and you can own up to 20.

Switch between workspaces from the **Workspace** row at the top of the account menu. See [Workspaces and moving systems](#workspaces-and-moving-systems).

## Create a team

1. Open the account menu, choose **Settings…** and go to **Team**.
2. Click **Create a team**. The **New team** dialog opens.
3. Type a **Team name**, up to 80 characters. The **Address** fills in from the name, and you can change it. It takes lowercase letters, numbers and dashes, up to 40, starting and ending with a letter or number. A taken address reads "That address is taken. Pick another."
4. Click **Continue**.
5. Under **Billing**, pick **Monthly** or **Yearly**. Yearly is picked first.
6. Set **Paid seats** with the minus and plus buttons. A team needs at least one paid seat, and your own seat is one of them. The dialog shows the cost: the paid seats times the seat price, "Viewers: Free" and the total a month or a year.
7. Click **Continue to checkout**. Payment runs through Polar, and tax is added at checkout where it applies.

DS Manager creates the team before it opens the checkout. When you come back from checkout, DS Manager shows "Checking the payment for Acme Design's Team plan…" for a few seconds, then the team is ready. If you close the dialog or the checkout without paying, the team stays in **Settings** > **Team** with **Choose plan**, and nothing in it can be edited until the plan is paid.

You can also start a team from **Create team** in the Workspaces dialog or the team picker, or from **Get Team** on the **Plans** tab.

On Lifetime, your own seat is free and comes on top of the paid seats. The dialog then says "A team needs at least one paid seat. Yours is free with Lifetime."

Monthly or yearly is chosen once, at checkout. DS Manager has no switch that moves a team from one to the other.

## Roles

Each member has one of four roles. Owner, admins and editors each take a paid seat. Viewers are free.

| Role | Seat | What they can do |
|---|---|---|
| Viewer | Free | Open the team's systems, install them, get code, comment and read over MCP. |
| Editor | Paid | Everything a viewer does, plus edit tokens and components, create systems, run the design agent, import, publish, apply updates and move their own Personal systems into the team. |
| Admin | Paid | Everything an editor does, plus change Lint locks and the lint policy, turn sharing on or off, delete systems, move systems out of the team, invite and remove editors and viewers, change their roles and delete any comment thread. |
| Owner | Paid, or free with Lifetime | Everything an admin does, plus billing and seats, invite, remove and change admins, transfer ownership and delete the team. |

A team has one owner, the person who created it. The owner can't leave the team. To hand it over, use **Transfer ownership**, described in [Change roles and remove people](#change-roles-and-remove-people).

When a role doesn't allow something, the app says so at that spot. For example, a viewer sees **View only** next to the system's name, and the right rail says "You can view Acme Design's systems. Ask an admin or the owner for editor access." An editor who opens **Share** reads "Only admins and the owner change sharing in this team."

## Invite people

Owner and admins invite people from **Settings** > **Team**.

1. Click **Invite people**.
2. Type one or more addresses in **Emails**, up to 20 at once. **Add more emails** adds a field.
3. Pick a **Role**: **Viewer**, **Editor** or, for the owner, **Admin**. Viewer is picked first.
4. Click **Create invite link**, or **Create invite links** for several people.
5. Click **Copy link** next to each address and send it to that person yourself.

DS Manager doesn't send any email. Each link is tied to the address you typed, and only an account whose verified email matches that address can accept it. Each link works for 14 days. To copy it again, find it under the open invites in the members list. **Revoke** turns a link off.

When the people you invite as editors or admins need more paid seats than are free, the dialog says so, for example "All 3 paid seats are in use." The owner can click **Add seat and send**, which adds the seats and charges them at once, prorated to the renewal. An admin is told "Only Maya can add seats, since the owner handles billing." Either can click **Invite as viewer instead**.

### Viewer link

The **Invite people** dialog also has a viewer link: "Anyone with the link joins as a viewer". Click **Copy viewer link**. Anyone who has it can join the team as a viewer, with no address check. It works for 14 days, and it shows in the open invites as **Viewer link** with the days left, where you can revoke it.

### Accepting an invite

An invite link opens a page that reads, for example, "Maya invited you to Acme Design" with the role. Click **Join Acme Design**, or **Decline**. A signed-out visitor is asked to log in with the address the invite was sent to.

The page explains a link that doesn't work: "This invite has expired", "This invite was already used", "You are already in Acme Design", or "This invite is for another account" when the signed-in address doesn't match.

## Workspaces and moving systems

The **Workspace** row at the top of the account menu shows the workspace you are in and, in a team, your role. Click it to open the **Workspaces** dialog, which lists **Personal** and each of your teams with your role and how many systems it holds. Pick one to switch. The system switcher then lists that workspace's systems.

![The Workspaces dialog listing Personal with 1 system and Northwind Studio, Owner, with 3 systems, and Create team](https://www.shadcndesign.com/docs/ds-manager/team-workspaces.webp)

### New systems

The **New system** dialog has a **Where** picker with Personal and each team where you are an editor or above. Pasted CSS always becomes a system in Personal first; move it to the team once you apply its review.

### Move a system into or out of a team

**Manage systems…** in the system switcher opens the **Systems** dialog for the workspace you are in. In Personal, a system's menu has **Move to Acme Design…** for each team where you can edit. In a team, it has **Move to Personal…** for admins and the owner.

- Editors, admins and the owner can move their own Personal systems into a team. Viewers can't.
- A system with a lint policy or Lint locks can come into the team only with an admin or the owner, because in a team the policy is theirs to set.
- Only admins and the owner move a system out of the team, and it goes to their own Personal workspace.
- A team whose plan isn't paid takes no systems in and lets none out.

The move dialog asks for a confirm and says what changes: in the team, admins and editors can edit the system and viewers can open it. Back in Personal, only you can open it. Either way, its registry keeps its address, so projects that installed it keep getting updates. If the other workspace already has a system with the same slug, the moved one gets a new slug there, and the old address keeps working.

When an editor moves a system in, its share link goes off. An admin or the owner can turn sharing on again.

## What a paid seat adds

Each paid seat adds to what the whole team shares:

- **30 systems** and **10 published registries**, pooled. A team with three paid seats holds 90 systems and 30 published registries.
- **$5 of AI usage a month** to one team pool. Design agent turns on the team's systems draw from it. Monthly grants don't roll over.
- **Everything in Pro** on the team's systems, for everyone who works in the team: all Pro Blocks, custom components and custom SVG icons. Agent calls over MCP on the team's systems run on the team's plan.

A paid seat in a paid team also gives its holder Pro in their own Personal workspace. **Plans** then shows "Included with your seat in Acme Design". Viewers get none of that for themselves.

At the limit, the app says so, for example "Acme Design's plan holds 90 systems and it has 90. Each paid seat adds 30." When the team's AI pool runs out, the agent says "This team's AI usage for the month is used up. It refills with next month's grant, or the team's owner can add seats."

## Seats and billing

The seat line in **Settings** > **Team** shows the seats, how many are paid and, for the owner, the price and the renewal date, for example "3 seats · 3 paid · $57 a month · renews 16 December 2026". Only the owner changes seats and billing. An admin sees "Only Maya can add or remove seats."

### Add or remove a seat

- **Add seat** asks "Add a seat to Acme Design?" and then charges the seat at once, prorated to the renewal.
- When seats are unused, the seat line shows **Remove seat**. A removed seat stops at the next renewal, so the team keeps it until then.

A team needs as many paid seats as it has owner, admins and editors. To free a seat, make someone a viewer first.

### Cancel, resume and invoices

The **Plans** tab has a card for each team you own, such as **Acme Design · Team**, with the price, the seats and the renewal date.

- **Cancel plan** and **Resume plan** open Polar's billing portal. A cancelled plan keeps working until the end of the period you paid for, and the card shows "Ends" with the date.
- **Billing and invoices** opens the same portal for receipts and the card on file.
- **Manage seats** opens **Settings** > **Team**.

To delete a team that still has a plan, cancel the plan first. Until then, deleting is refused with "This team's Team plan still renews. Cancel the plan in Settings, Plans first, then delete the team."

### When a team's plan isn't paid

A team whose plan was never paid, failed to renew or ended is read-only for everyone in it. A banner says so, for example "Acme Design's Team plan is not paid. Editing is paused until it is renewed." The owner sees **Renew**, or **Choose plan** on a team that never paid.

- People can still open the systems, get code and comment.
- Viewers can still join.
- Every published registry keeps serving, Pro Blocks included, so installed projects keep working.
- Editing, publishing, sharing, moving systems and the design agent wait until the plan is paid.

## Change roles and remove people

The members list in **Settings** > **Team** shows each person with their role. Owner and admins change a role from the **Role** menu on that person's row. Each option says what it costs: **Seat**, **Free**, or **Adds a seat** when the paid seats are full.

- Admins change editors and viewers. Only the owner changes admins.
- Nobody changes their own role.
- **Remove from team**, in the row's menu, takes away access to the team's systems at once. The person's own systems stay theirs.
- **Leave team…** at the bottom of the tab takes you out of the team. To come back, someone in the team invites you again.

The owner hands the team over by picking **Owner**, marked **Transfer**, in another member's **Role** menu. The dialog asks "Make Jordan the owner of Acme Design?" and the billing moves with the team. You stay in the team as an admin.

The owner deletes the team with **Delete team…**. It deletes the team, its systems and their registries for everyone in it, and it can't be undone. You type the team's name to confirm.

## Agents and MCP in a team

Your coding agent signs in as you, so it acts with your role in each team. Tokens stay personal: each person connects their own agent.

- `list_systems` lists your Personal systems first, then each team's, with the workspace and your role in it.
- `create_system` takes a `workspace`, a team's id or name, to create the system in that team. You need to be an editor or above there.
- A viewer's agent reads, installs and comments. A write is refused, and the agent is told to say "You can view this team's systems but not edit them. Ask an admin for editor access."
- An editor's agent can't change Lint locks. A locked edit ends with "Ask an admin to unlock it."
- A call on a paid team's system runs on the team's plan, so a Free member spends none of their own allowance there. Calls on your Personal systems, calls that name no system, and calls on a team whose plan isn't paid run on your own plan.
- Daily usage limits stay per person: 3,000 requests and 1,000 edits a day, also in a team.

When another member's agent changes a team system, the run's banner names them, such as "Jordan's Claude Code changed 12 values".

A review from an import, a conversion or a Figma pull into a team system belongs to the team. Every member who can edit that system can see it and apply it. Each system links to one Figma kit file, shared by the team, and any editor can pull or push through their own agent's Figma connection.

**Settings** > **MCP** lists **Where your agents can work**: each workspace with your role and its number of systems, marked "read only" where your agent can only read.

See [MCP server](/docs/ds-manager-mcp).

## Comments and Lint locks in a team

Everyone in a team can comment, viewers included.

- Only the person who started a thread, and the team's editors, admins and owner, can resolve or reopen it.
- Only the team's admins and owner, and the person who started a thread or their agents, can delete a whole thread.
- A single comment can be edited or deleted only by its writer and their agents.

See [Comments](/docs/ds-manager-comments).

In a team, only admins and the owner turn Lint locks on, change them and change the lint policy. Editors see the Lint tab read-only, with "Only admins and the owner change the lint policy and Lint locks in this team." Locks still bind agents only, so anyone who can edit can still change a locked value by hand. See [Lint locks](/docs/ds-manager-lint).
