Teams

A team is not a new thing to learn. It is a workspace, the same one your artifacts already live in, on the Team or Business plan, with more people in it. This page is about what changes when more than one person publishes to the same place.

Team and Business may not be on sale where you are reading this yet. If the pricing page shows a button to start one, you can. If it says coming soon, you cannot yet. How Team and Business pricing works has the sums.

One workspace, four roles

Everyone in a workspace has exactly one role.

• Owner. Everything an admin can, plus billing, making someone else an owner, and deleting the workspace. Cannot leave while they are the last owner.
• Admin. Invites and removes people, changes roles, sees and revokes agent keys in the workspace (except an owner's), takes a template off the shelf, and releases a template to the marketplace. On Business, also sets the workspace policies. Cannot change the plan or the card, and cannot make anyone an owner.
• Member. Connects their own agents, publishes, edits a teammate's artifact that is open to the workspace, and publishes to the team's shelf. Cannot delete or re-share a teammate's artifact, and sees nobody else's keys.
• Viewer. Opens what the workspace can see, comments, submits data, joins live rooms. Cannot connect an agent or publish.

Owners, admins and members are builders. A builder uses a seat. Viewers are free and there is no limit on how many a workspace has. See How seats are counted.

Your personal workspace stays yours. Nobody is ever invited into it, and joining a team does not move anything out of it. Being on a paid team does not change what your personal workspace can do; it stays on its own plan.

Who can open what

Every artifact has an audience, set on its Share tab:

• Private. Its author, the workspace's owners and admins, and anyone named on it. Other members and viewers cannot open it.
• Anyone at the workspace. Every member can open and edit it; every viewer can open and comment. People outside the workspace are asked to request access.
• Public. Anyone with the link.

Owners and admins can always open every artifact in the workspace. A member sees a teammate's private artifact only when the teammate names them on it or opens it to the workspace.

Inviting people

From Settings → Members, an owner or admin sends an invitation to an email address with a role. The invitation is good for seven days and goes to that address and no other.

• On Team, it uses a seat when it is accepted, never when it is sent. Pending invitations are capped at twice the seat count.
• On Business, it holds one of the seats you bought from the moment it is sent.
• On Free and Solo, the workspace has one builder, so invite people as viewers.

When every seat is in use, an invitation that needs one is refused and the page says so, with the two ways out: add a seat, or invite the person as a viewer, which needs none.

Someone who is already in another team keeps it. Workspaces are switched from the top of the sidebar.

Letting colleagues find you

A Business workspace can verify a domain, such as acme.com, so that anyone who signs in with an address on it is offered the workspace. By default they request to join and an admin approves each one. An admin can instead let them join straight away, as a viewer or a member. Consumer domains such as gmail.com cannot be verified.

Domain capture is switched on per deployment. Until it is, the Domains section on Settings → Members says so and offers no button.

Nothing of theirs moves when they join. A personal workspace is still personal.

When someone leaves

Removing a member, or a member leaving, does four things, and the dialog lists them before the button:

1. Their agent keys for this workspace stop working now. An agent mid-deploy finishes; the next call gets a 401. Keys they hold for other workspaces are untouched.
2. Their artifacts, playlists and dashboards stay here, handed to a builder you choose, so that person's agent can update them from now on.
3. Private access ends within 24 hours. Access that came from membership is a grant that lasts a day and is not renewed.
4. Named sharing (artifacts they were added to by email, one at a time) is removed too, unless you untick it.

On Team the seat is freed and the next invoice is credited for the unused part of the period. On Business the seat stays bought and is free for someone else.

Deleting a workspace

An owner deletes a workspace from Settings → Workspace, after typing its handle. In this order:

1. Billing is cancelled first, prorated. If it cannot be, nothing is deleted.
2. Everything stops serving. Its artifacts answer as though gone, and its agent keys are refused. Members keep their personal workspaces.
3. For 30 days it can be restored from the same page. Billing does not come back with it, and its artifacts can take up to a day to serve again.
4. Then it is gone: artifacts, playlists, collections and keys are deleted, and the handle is retired for good, so no one else can take it and old links never lead to a stranger's work.

A personal workspace is not deleted from here; it goes with your account.

The team shelf

On Team and Business, Templates has a shelf for the workspace. Any member can publish a template to it; every member's agent can build from it; nothing on it is visible outside the workspace or in the marketplace. An admin can take a template off the shelf, and only an admin can release one to the public marketplace. On Business, an admin can require approval before anything reaches the shelf.

Building from a shelf template works the way it does everywhere else: Copy prompt, and paste it at your agent.

Usage and limits

Limits on a team are shared by the whole workspace, not set per person. One member's agent filling the storage fills the team's storage. Settings → Billing shows the usage, with storage by member.

• Team: you are warned at 80% and owners are emailed. Past 100% there is 10% of grace, then new publishes are refused.
• Business: fair use. Nothing is refused; owners are emailed and we get in touch if it stays over.
• Free and Solo: the limit is hard.

Everything already published keeps serving at every stage. A limit stops the next deploy and nothing else. The numbers are on Plans and pricing.

Billing

The subscription belongs to the workspace, not to a person, and every member gets the plan's capabilities inside it. An owner manages the card and invoices from Settings → Billing, and sets the billing email that invoices and payment warnings go to.

Team is paid by card, monthly or yearly, and seats follow membership: accepting an invitation adds one and removing a member credits one, prorated. Business seats are bought in advance; at renewal the invoice stays at the seats you bought unless there are more builders, and the billing page previews it. Business on yearly billing can also be paid by invoice against a purchase order, which we set up with you.

The first 100 Team and 20 Business workspaces to subscribe before 31 March 2027 keep the launch price for 24 months from their first payment. After that a change applies at renewal and is never more than 25% in a year.

What is not built

• SSO and SCIM. You sign in with a password, an emailed code, or Google or GitHub, and membership is managed here. Neither SSO nor SCIM can be bought.
• An audit log on Team. The audit log (who did what, kept a year, exportable) is a Business capability. Team keeps the activity feed.
• Cross-member agent access. Your agent publishes to the workspace; it does not edit a teammate's artifact for them.