Teams
A workspace starts as yours alone. Inviting someone turns it into a team, and the single most important thing to know before you do is this: joining a team does not hand anyone your files.
Everything you create stays visible only to you until you explicitly share it. That is the opposite of how most tools work, and it is deliberate: a shared workspace should not mean a shared filing cabinet.
Inviting people
Go to Settings → Team.
- Select Invite member.
- Enter their email address and choose a role.
- They receive an email with a link. Nothing happens until they accept it.
The invitation expires after 48 hours. If it is about to lapse, we send one reminder; after that an admin has to send a new one.
An invitation holds a seat from the moment you send it, so ten invitations into two free seats are refused at the third rather than at the tenth acceptance. Revoking an invitation frees its seat immediately.
Roles
| Role | What they can do |
|---|---|
| Owner | Everything, including billing. Every workspace has exactly one, and it cannot be removed or demoted from this screen. |
| Admin | Everything an editor can, plus members, roles, billing and destructive actions like emptying trash. |
| Editor | Create and change anything shared with them, and use AI. |
| Viewer | Open what is shared with them. Nothing else, ever. |
A role is a ceiling, not a starting point. If a designer shares a file as "can edit" and you are a viewer, you still only see it. That is the rule that makes "viewer" mean something.
Sharing an item with the team
Right-click any work and choose Share with the team, then pick Can view or Can edit.
- Sharing a folder shares everything inside it, including items added later, and including items in folders nested inside it.
- Sharing is a permission, not a copy. The file stays yours, its media stays where it is, and stopping the share takes the access away without touching anything.
- Stopping a share is immediate, including for someone who has that file open right now.
Everything shared with the workspace appears under the Team filter in Works.
Team sharing and "Shared with me" are different things
Team is what your workspace shares internally. Shared with me is what one specific person, often from outside your workspace, granted you directly. They stay separate so "why can I see this?" always has one answer.
Seats
Your plan sets how many seats a workspace has. Seats count members plus pending invitations, and a viewer counts the same as an editor.
If a plan change puts you over the limit, nobody is removed. New invitations pause, pending ones can be revoked to free space, and everyone already in the workspace keeps working.
When someone leaves
Whether they leave or an admin removes them:
- everything they created stays theirs, in their own workspace;
- anything they had shared with the team stops being shared, and admins are told what disappeared;
- their access ends at once, including any editing session they have open.
Nothing is transferred and nothing is deleted. The workspace's owner cannot leave without transferring ownership first, because a team with a subscription and nobody able to administer it is not a state worth allowing.
Automations in a team
An automation always runs on its creator's AI key and budget, no matter who or what set it off. That is why an automation only reacts to other people's actions once its creator has shared it with the team, and why every automation card states whose budget it spends. A teammate editing a shared automation is spending someone else's money, and the product says so rather than hiding it.
Switching workspaces
Once you belong to more than one workspace, a switcher appears at the top of the sidebar. Switching reloads the page on purpose: the active workspace belongs to your session, so every open tab follows it. Working in two workspaces in two tabs at the same time is not supported.