TransIT AI
Sign up

How-tos

Manage overage for a team member

By default, overage is on for every Pro or Max team member: their AI requests keep working past their tier’s monthly allowance, with the additional usage billed to the team’s card at a per-seat cap (no surprise bills beyond the cap). An admin can turn overage off for a member — their requests then stop at the tier allowance instead.

Only an admin or owner can turn overage on or off, and they set it for each member individually.

This page covers what overage costs, what gets billed, and how to turn it off or back on for a member.

Quick math

When a Pro or Max member exceeds their tier allowance (overage is on by default), overage usage bills at 1.25× the AI provider’s per-token cost (provider cost + 25%), capped at:

  • $158/month per Pro seat above the tier price
  • $398/month per Max seat above the tier price

So a team with 2 Pro + 1 Max members has a maximum monthly overage exposure of (2 × $158) + (1 × $398) = $714 above the base subscription — and only if every member hits their cap. The actual bill is based on usage; if a Pro member spends $50 of overage they’re billed $50. A member you’ve turned overage off for contributes zero overage exposure no matter what they do.

Operator seats can’t use overage. Operator allowance is fixed at the tier cap. If an Operator member needs more, the right move is to switch them to Pro or Max first — the overage checkbox unlocks once they’re on a Pro/Max seat.

Steps — turn overage off (or back on) for a member

  1. Go to /admin/members/.
  2. Find the member’s row. The Usage column shows how much of their own tier allowance they’ve used this billing cycle — handy for deciding who actually needs overage.
  3. Tick the Overage checkbox on their row. (Greyed out? Their seat is Operator or unassigned — move them to Pro or Max first, in the same row.)
  4. Click Save on that row.

The change is immediate. The member’s running desktop app picks up the new setting within one AI request, or within ~30 minutes if they’re idle.

To set overage on your own seat (admins are members too), use the checkbox on your own row the same way.

Steps — disable overage for a member

  1. Same Members page.
  2. Untick the member’s Overage checkbox and Save.

A member already past their allowance when you turn their overage off will be blocked from the next request onward. We don’t refund overage already spent in the current period — the usage was real. Moving a member off Pro/Max also switches their overage off automatically.

What about BYOK?

BYOK and overage stack. They’re two different escape hatches from the tier allowance:

  • BYOK — each member brings their own Anthropic or OpenAI key. AI calls on that key are billed by the provider directly to the member’s provider account, not to your team’s Stripe card. Free for every paid tier; no admin toggle required.
  • Overage — the team’s card pays for usage past the tier allowance, at the 1.25× / capped rate.

The most common team pattern:

Opt your heavy hitters into overage. Encourage members to enroll BYOK for their day-to-day. Members fall through BYOK → tier allowance → overage → cap, in that order. Heavy users mostly run on BYOK for free; the org card only catches the spillover.

See Bring your own key for the member-side BYOK setup.

When you’d turn overage off

  • Strict budgeting. Some teams want a hard cap matching the subscription — no surprise bills, period. Turn overage off for those members; they wait for renewal or coordinate with the admin when they exhaust their tier.
  • Cost control on specific seats. Overage is on by default, so the deliberate action is turning it off for members whose spend you want held to the tier allowance.

How to estimate overage exposure

The Members page shows each member’s current-cycle usage (their percentage of their own allowance, with token counts on hover, and the dollar amount once they’re actually in overage). The Billing tab shows the rolled-up view: how many members have overage on and the total overage invoiced this cycle.

Worst case = (# of Pro members with overage on × $158) + (# of Max members with overage on × $398)

If that number is uncomfortable, turn overage off for more members and rely on BYOK + tier upgrades instead.

Common issues

”Overage needs a Pro or Max seat” when saving

That member’s seat is Operator (or no tier yet). Operator doesn’t support overage. Either:

  • Move them to a Pro or Max seat (same row — tier dropdown, then tick overage, one Save does both), OR
  • Skip overage for them and rely on BYOK + tier upgrades.

Enabled overage, member still blocked

Check the member’s row on /admin/members/ — the checkbox must be ticked on their row (overage is per member; another member’s setting doesn’t carry over), and their seat must be Pro or Max.

Cost spike after enabling overage

The overage charge appears on your team’s next monthly invoice, not as a separate charge. The Members page shows who’s in overage and for how much this cycle. If the line item is larger than expected, the most likely cause is a member with a runaway session (long-running agent loop, repetitive prompts). Check in with them, then decide whether to keep their overage on or move them to BYOK.