TransIT AI

Team plans

A team plan lets one admin buy a pool of Transit AI seats on a single invoice, invite teammates by email, and manage everything — billing, roster, tier assignments, overage — from a dedicated admin portal at transitai.app/admin/.

This page is the overview. The step-by-step guides live under How-tos → Teams.

How team plans differ from personal plans

Personal planTeam plan
SubscriberOne personOne organization
PaymentThe user’s cardThe admin’s card (one invoice for everyone)
Seats1Any mix of Operator + Pro + Max, total ≥ 1
OnboardingSign-up formAdmin sends an invite email; member clicks the link
Tier changesThe user picks their ownThe admin assigns each member’s tier
Billing portalThe user’s account pageThe admin portal
OverageOn by default; each user can turn it offOn by default per seat; the admin can turn it off per member
BYOKIncluded free, per-userIncluded free, per-user

Tiers, prices, allowances, and BYOK behavior are otherwise identical to the personal plan. See Billing & usage for the mechanics that apply to both.

What an admin can do

  • Buy a team plan from /pricing/ → “Buy for a team” → pick how many seats of each tier the team needs.
  • Invite members by email from /admin/invites/ — pick which tier the invite consumes; the member’s email gets a link.
  • Manage members from /admin/members/ — change someone’s tier, change their role (Admin can manage; Member can’t), or remove them.
  • Adjust seats from /admin/billing/ — add or remove seats at each tier. Increases prorate immediately; decreases defer to the start of your next billing period so no one’s entitlement disappears mid-period.
  • Manage overage per member from /admin/members/ — overage is on by default for each Pro or Max member; turn it off (or back on) per member to control spending past their tier allowance, up to a per-seat cap, and see every member’s current-cycle usage in the same table before deciding. (Operator seats are capped at the tier allowance; switch a member to Pro or Max if they need more. The Billing tab shows the rolled-up overage total.)
  • Cancel the subscription anytime — effective at period end; all members keep access until then.

What a member sees

A member who accepts a team invite signs in as themselves but their subscription is managed by the team’s admin. Specifically:

  • The /account/ page shows their plan but no billing controls. The “Manage subscription” button and tier-switch dropdown are replaced with a note: “Managed by your team admin.”
  • The desktop app shows their assigned tier in the sidebar footer exactly as it does for a personal subscriber.
  • If the admin changes their tier (Operator → Pro, say), the change propagates to their running desktop app within one AI request, or within ~30 minutes if the app is idle. They don’t need to sign out and back in.
  • They keep full control of BYOK. Each member enrolls their own Anthropic or OpenAI key in the desktop app — see BYOK. The admin can’t read it.

What a member CAN’T do

  • See or pay the team’s bill
  • Add seats or invite new members
  • Change anyone’s tier — including their own
  • Cancel the subscription
  • See other members’ usage

Anything that touches the org’s Stripe customer (portal, overage toggle, checkout) returns a 403 if a member calls it. The admin portal at /admin/ returns “Not authorized” if a non-admin lands there.

Pricing

A team plan is just N personal subscriptions on one invoice — no volume discount, no minimum, no setup fee.

Operator seat — $29 / month / seat
Pro seat      — $79 / month / seat
Max seat      — $199 / month / seat

Annual billing is 12× the monthly rate — same as the personal plan. Pick whichever invoice cadence you prefer.

Common workflows

The full step-by-step guides live in How-tos. The most common ones:

Cancellation

When the admin cancels, all members keep access through the end of the current billing period. After that, the AI assistant goes quiet for every member; the SSH client itself keeps working. The admin can re-subscribe later — member roster and assigned tiers are preserved, so reactivation restores the team without re-inviting.

A member can also leave a team by asking the admin to remove them from /admin/members/. After removal they keep their personal Transit AI account, but their tier becomes none — they’ll need to subscribe personally or accept another invite.