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.

The pricing page shows whether new Team Checkout is available here. New Team costs $49 monthly or $490 yearly per workspace, with 50 GB of shared retained storage. Business is available only to existing subscribers. Legacy seat pricing explains existing seat-priced contracts.

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. New Team has no builder count or seat charge. Existing seat-priced Team and Business contracts retain their seat rules. Viewers are free and unlimited.

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 → Team, 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 new Team, invitations do not consume seats or have a seat-count gate.
• On legacy Team, a builder uses a seat when they accept. Pending invitations are capped at twice the purchased seat count.
• On legacy Business, a builder invitation holds one purchased seat when sent.
• On Free and Solo, the workspace has one builder, so invite people as viewers.

Legacy seat contracts refuse an invitation that needs an unavailable seat; an owner can add a seat or invite a viewer.

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 → Team 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 new Team, removing a member does not change the subscription amount. On legacy Team, the seat is freed and the next invoice is credited. On Business, the purchased seat stays available 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.

To put one of your own artifacts on the shelf, open it, choose Add to workspace shelf… in the More actions menu, and paste the prompt at your agent. A template is the pattern an artifact is an instance of, so your agent writes the template and releases it to the shelf rather than the page being copied as it is.

Making a copy

Anyone with a Builder seat or above can choose Make a copy in the More actions menu of an artifact they can open. The copy is a new artifact in your workspace, owned by you and private, and it says where it came from. It starts from the published version only: comments, collected data, analytics and the share list stay with the original, and copying gives you no access to the original beyond what you had. A Viewer seat has no copy action. If the author turned downloads off, only people who can edit the original can copy it.

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.

• Free, Solo and new Team: retained storage has a hard cap. New writes that grow storage are refused at the cap; an owner can explicitly add 10 GB packs on a paid plan or clean up.
• Legacy Team and Business: existing contracted limits and seat rules remain in force.

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.

New Team is paid by card at $49 monthly or $490 yearly, per workspace, with no per-person charge. An owner can explicitly buy 10 GB packs for $5 monthly or $60 yearly on the same billing interval, subject to a monthly equivalent spending cap. Each additional workspace has its own Team subscription and 14-day card-backed trial. Existing seat-priced Team and Business subscriptions keep their contracted billing rules. Business on yearly billing can also be paid by invoice against a purchase order, which we set up with you.

The founding price lock applies to eligible existing seat-priced Team and Business subscriptions; see Legacy seat pricing.

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.