# Teams > Workspace roles, invitations, shared storage, billing, and legacy seat contracts. Kind: guide · ~9 min · Verified v0.66.0 · Next: [What an artifact is](https://pr-756-stg.superartifacts.app/docs/concepts/artifacts.md) 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](https://pr-756-stg.superartifacts.app/pricing.md) 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 cannot be bought; it is available only to existing subscribers, and the Business features below apply only to them. [Legacy seat contracts](https://pr-756-stg.superartifacts.app/docs/reference/plans.md#legacy-seat-contracts) explains existing seat-priced contracts. ## One workspace, three roles Everyone in a workspace has exactly one role. - **Owner.** Everything: invites and removes people, changes roles, sees and revokes agent keys in the workspace, takes a template off the shelf, releases a template to the marketplace, billing, making someone else an owner, and deleting the workspace. On legacy Business, also sets the workspace policies. Cannot leave while they are the last owner. Admin was folded into Owner; every former admin is an owner. - **Member.** Connects their own agents, publishes, and publishes to the team's shelf. Edits a teammate's artifact only when its owner has switched on builders can edit for it. 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 and members are **builders**. New Team has no builder count or seat charge. Existing seat-priced Team and Business contracts retain their [seat rules](https://pr-756-stg.superartifacts.app/docs/reference/plans.md#legacy-seat-contracts). Viewers are free and unlimited. Buying Team on your **personal workspace** makes it a team workspace in place: same id, handle and artifacts, and you can invite people. Ending Team never makes it personal again. Joining someone else's team leaves your personal workspace alone. A new team workspace is created by starting Team checkout, and stays a hidden draft until the subscription is confirmed, so on Free and Solo the personal workspace is the only one. ## Who can open what Every artifact has an audience, set on its **Share** tab: - **Restricted.** Its author, the workspace's owners, and anyone named on it. Other members and viewers cannot open it. - **Anyone at** *the workspace's name*. Needs Team. Every member and viewer can open it and comment. Members can also edit it, and see its analytics, data and files, when the owner switches on **Builders can edit**, which is off by default. People outside the workspace are asked to request access. - **Anyone with the link.** Anyone, without signing in. Owners 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 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 legacy 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 owner approves each one. An owner 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, projects 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, projects, 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 owner can take a template off the shelf, and only an owner can release one to the public marketplace. On legacy Business, an owner 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 Any builder 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 has no copy action. If the author turned downloads off, only people who can edit the original can copy it. ## Workspace keys A personal API key publishes as the person who made it: what it publishes belongs to them, and the key stops working if they leave the workspace. On Team and Business, an owner can also mint a **workspace key** from **Settings → API keys**. It publishes as the workspace instead: - What it publishes belongs to the workspace. Owners manage it like anything else in the workspace, and new artifacts follow the workspace's default audience. - It keeps working if the person who minted it leaves, or deletes their account. - It can only publish into its own workspace, and only update what workspace keys published. It cannot touch a teammate's artifacts, projects or templates, even one whose owner lets builders edit it. - Every owner sees it, with who minted it, on **Settings → API keys** and on **Agents**, and any of them can revoke it. The secret is shown once, when it is made. - If the workspace drops below Team, the key stops with a message naming the plan. Everything it published stays, and owners keep managing it. Viewers and builders cannot mint one. ## 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](https://pr-756-stg.superartifacts.app/docs/reference/plans.md). ## 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. The founding price lock applies to eligible existing seat-priced Team and Business subscriptions; see [Legacy seat contracts](https://pr-756-stg.superartifacts.app/docs/reference/plans.md#legacy-seat-contracts). ## 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) comes only with legacy Business. Team keeps the activity feed.