Team workspace
Chat, shared tasks, and presence for teams on the Team plan.
The team workspace is the Team plan's headline feature: a small realtime hub inside the editor for the people sharing an account's seats to talk, split work, and see who's online — without leaving the editor or setting up anything separate.
Who sees it
Nothing about the team workspace appears unless the signed-in account is on an active team — either the owner of a Team (or Ultra) plan, or an email an owner has invited. Everyone on a team gets full Pro access to the editor for as long as the owner's plan stays active, on top of the team workspace itself.
Opening the dock
A chip in the toolbar shows the team's current online count and a small dot when there's an unread chat message. Clicking it opens the dock — a floating panel over the canvas with three tabs.
| Tab | Contents |
|---|---|
| Chat | Realtime team messages. The team leader can mute a member's chat from the Members tab |
| Tasks | A shared task list: start a task, mark it doing, submit it for merge with a note, and see feedback. The leader can block a member's task/merge rights |
| Members | Every teammate with an online indicator (seen in the last ~70 seconds counts as online), plus the leader's moderation controls |
The dock's presence heartbeat runs for the whole time the editor is open, so teammates show as online even while you have the dock closed.
Creating a team and inviting people
The team owner creates the team (naming it) and invites up to five members by email from the dock. Each invited address gets:
- Full Pro access to the editor, for as long as the owner's Team plan is active.
- A welcome email (if the owner has invited a new address) confirming the invite and linking back into the editor.
- A seat in the team's Chat, Tasks, and Members tabs, with the same read/write access as anyone else unless the leader restricts them.
An invited email can only belong to one team at a time.
Tasks and merging work
Tasks are a lightweight way to divide up a scene without stepping on each other's edits: a member starts a task against a saved project snapshot, works on their own copy, and submits it back for merge with a short note. This keeps concurrent editing from silently overwriting someone else's changes — every merge is an explicit, reviewable step rather than a live shared document.
Leader moderation
The team owner (or an Ultra admin) can mute an individual member's chat, or block their ability to start/submit tasks, from the Members tab — without removing them from the team. Every leader action (renames, invites, removals, chat/merge restrictions) is written to the team's activity log.
See What's possible for how the team workspace fits alongside the rest of the editor, and Panels and features for every other panel.