Invites and roles
The Team plan is $40 per member a month, with $20 of AI per member a month for the first three months, pooled across everyone. Invite by email; people keep their own discussions and gain the team's.
Sharing a discussion
Share it with the team and they can read it and continue it. Teammates comment in the transcript — notes the room does not answer and never sends to a model, unless a comment @mentions a seat or @room.
Share with Team… (web ⋯ menu, the Mac's Share panel, the iPhone's discussion menu) offers three choices, saved as you pick: Only Me, Whole Team, or Choose People…, which lists the team by name to tick. Only people on your team can be chosen. Untick someone and they lose the discussion at once, including a live run they were watching; leaving the team ends it too. The author, the team's owner and admins change who is in. A discussion filed in a team project is shared by the project, so its people are not chosen one by one.
If the team's plan ends, shared discussions stay readable but go read-only for everyone but their author. The line under the transcript says so, names the owner who can renew, and shows the owner a Renew button. Reading, copying and exporting still work.
For anyone else, a share link makes a discussion readable without an account. Private until you ask for one, one link, and revoking it is permanent — the old URL stops resolving rather than being reissued.
Teammates' discussions on every app
What your teammates shared is listed apart from your own: Team on the web and the iPhone, Shared With Me in the Mac's sidebar. Open one to read it, follow a run as it happens, and write in it. Your questions appear under your name, theirs under theirs.
On the Mac they are read from the server, never copied into your own discussions; the workspace, terminal and seats stay with the owner. A message goes to the server's room on the team's credit, or to the owner's Mac when they allow it (below). If the plan has ended or the team is paused, the composer says why it cannot send.
Attach pictures or files with ＋ or by pasting; they go with the message whether the server's room or the owner's Mac answers it. /comment leaves a note instead of asking the room. Right-click → Open in Split Screen to read it beside your own.
To hide the section: Show Teammates' Shared Discussions — Mac: Settings → Appearance → Display; web: Settings → Appearance → Sidebar; iPhone: Settings → Appearance → Sidebar. On by default and the same on every app. Hiding it shares nothing less; a link or a notification still opens them.
Co-drive
A shared discussion that runs on someone's Mac can be continued by a teammate from the web, the iPhone or their own Mac, with the turn handed to that Mac. The owner's switch decides whether that is allowed; the app always says whose machine a turn is going to.
Controls the owner sets
- Tickets-only — discussions must belong to a project, so nothing lands unfiled.
- Spend by project, release or ticket — where the money actually went, not just a total.
- A ceiling per discussion — the blunt stop.
- Budget alerts — told before the month runs out, not after.
PII masking
A team setting: personal data is replaced before a prompt leaves and restored in what you read, with a line saying what was masked. Off by default.
Provisioning
SCIM 2.0 for accounts that provision from an identity provider. Members sign in with Apple, Google or Microsoft, or through the team's own company sign-in: OpenID Connect, SAML 2.0, or an LDAP server (we connect from 209.71.116.125, 2a09:8280:e618:1:0:161:5814:0). The team can require it on its verified domain; the owner keeps other ways in. An admin mints the SCIM token once.
Slack
Where the deployment is connected to Slack, mentioning the bot starts a discussion, the thread mirrors it, and approvals appear as cards you can answer without leaving Slack.