A team space is a shared workspace with its own memory, notes, briefs, and approvals — everything a personal space has, visible to every member.
Creating a team
Settings → Teams → + Create a team (also reachable from the space switcher once you have one). You'll name the team and answer two short questions — what the space is for, and any conventions members should know — which seed the team's shared profile. The creator becomes the owner.
Team spaces are part of the Team plan; see Billing.
Inviting people
Open Members from the team dashboard (or the people icon in the nav) and invite by email. The invitee gets an email; once they sign in with that address, they're on the roster automatically. Pending invites can be revoked. On a billed team, invites are gated by seats — if the roster plus pending invites would exceed your seat count, add seats first.
Roles
| Role | Can do |
|---|---|
| Owner | Everything, including billing. One per team; fixed in v1. |
| Admin | Manage members (invite, change roles, remove). |
| Member | Full use of the space: chat, notes, runs, approvals. Can leave anytime. |
Role enforcement is server-side, not just hidden buttons — a member who calls the billing endpoint directly gets a 403. Removal or leaving takes effect immediately.
Switching spaces
Once you're in at least one team, a space switcher appears in the nav (solo users never see team chrome). It shows which space you're acting in — Personal or a team name with your role — and every screen follows it: the dashboard, vault, approvals, and agent views all show the active space. Anything you write or run while switched into a team lands in the team space, and the switcher label keeps that unambiguous.
The team dashboard — member-contributed
The team dashboard renders the team space's brief, open loops, and pending approvals, same as your personal one. One deliberate v1 design decision to know:
Team connections are the team's own — and personal ones stay personal. A team admin can connect tools directly to the team space (the shared Slack, the team calendar); those connections belong to the space and power its briefs and runs. A team-scoped run never reaches into any member's personal connectors — that would be a cross-member read of your private accounts, and that door stays closed. Members also contribute directly: switch into the team, chat there, save notes and decisions, run skills that write to the team space. Admins can restrict which connector types the team space accepts.
Billing
Team billing belongs to the owner: only they see Manage billing / Subscribe for the team, and only they can check out. Members and admins see the plan; the owner manages seats and payment. See Billing.
Leaving and deleting
Members can leave from the Members panel; owners and admins can remove members — access ends immediately, though content a member contributed remains with the team. An owner who wants to delete their account while their team still has members must first remove them (ownership transfer is manual in v1 — contact support).