Team workspaces
A team workspace is a second, separate workspace that a team plan opens for you. It is not a mode your own workspace switches into: buying the plan creates a brand-new, empty workspace and puts you in it. Your personal workspace and everything in it stay exactly as they are, and nothing moves unless you move it.
You can belong to several workspaces at once. The switcher at the top of the sidebar lists all of them, including your own, and one click moves between them.
Your workspace and a team workspace are not the same thing
| Your own workspace | A team workspace | |
|---|---|---|
| Who owns the work | You | The workspace |
| Who can see it | Only you, until you share it | Only its creator, until they share it with the team |
| Seats | None. It is yours alone | As many as the plan pays for |
| Storage | Your plan's | A pool an admin divides between members |
| AI | Your plan's | A per-seat allowance, plus anything the workspace bought |
Joining a team shares nothing on its own. Every item you make stays visible to you alone until it is explicitly shared with the team. That is deliberate: being invited to a company workspace should not publish your work to it.
Seats
A seat is taken by a member and by a pending invitation, because an invitation that has not been answered is a place being held. Revoking one frees the seat immediately.
A paused member also keeps their seat. That is on purpose: if pausing somebody freed their seat, an admin could fill it and then be unable to restore the person they paused. The seat line tells you how many are paused, so a full workspace always explains itself.
Roles
| Role | Can |
|---|---|
| Owner | Everything, including billing, the plan and handing the workspace over |
| Admin | Invite, remove, allocate storage and AI, change roles below their own |
| Editor | Create and edit work shared with them |
| Viewer | Read-only on everything shared with them |
A role is a ceiling, not a grant: sharing an item with a viewer still leaves them read-only on it.
Invitations
An invitation arrives by email, and it also appears inside the product: open Settings → Team and any invitation addressed to you is at the top, with who invited you and what role you would join as. Accept or decline there. You do not need the email.
Storage and AI inside a team
Storage is a pool the workspace bought, and an admin divides it between members. Unallocated space belongs to nobody: a member with no allocation cannot upload at all. This is a hard cap per person, so one member filling up never takes the space somebody else was given.
AI has three separate things behind it, and they behave differently:
- The seat allowance is what the plan funds for your seat each month. It is fixed - it cannot be divided, topped up or taken away - and it resets on its own. You see what percentage of it is left.
- Credit packs are bought once and drawn down until they are spent. They never reset. An admin can buy a pack for the workspace or for one specific person.
- The workspace's own API key, if an admin has added one. An admin can cap how much of it any one member may use in a month; you can see your own ceiling and what is left of it under Settings → AI Settings → My key.
Your personal API key is never capped by the workspace, because it is your account and your money. Inside a team it is off by default and only you can turn it on.
What an admin cannot do
- They cannot take your own account away from you. Your profile, security, notifications, privacy and the ability to close your account are always yours, in any workspace.
- They cannot use your personal API key without your consent. It is off by default and only you can switch it on.
- They cannot pause the owner, or themselves. Both would leave a workspace nobody can administer.
- Pausing is not removing. A paused member keeps their membership, their work, their seat and their allocation, and one click restores them.
Leaving
You can leave any team you are in from Settings → Team, whichever workspace you happen to be standing in. You keep everything you created; items you shared with the team simply stop being shared, and you would need a new invitation to come back.
An owner cannot leave their own team - it would strand a workspace with a subscription and nobody to administer it. They transfer ownership first, which makes somebody else the owner and them an admin.