All documentation

Documentation Tickets, projects and teams

Teams and sharing

Invite people, share the work, and decide what the team is allowed to spend.

Invites and roles

The Team plan is $40 per seat a month, with $20 of AI per seat 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.

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.

Co-drive

A shared discussion that runs on someone's Mac can be continued by a teammate from the web, 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, and sign-in through Google or Microsoft Entra ID. 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.

See also

Not what you were looking for? The help centre answers one question at a time, and the support page says how to reach a person.