Skip to main content
The team plan centers on a shared credit pool: every member’s AI spending debits the same pool, topped up and managed by admins.

​
Default allowances

Stability: configurable defaults. The table above is the zero-config fallback in code (SUBSCRIPTION_PLANS.team); operations can override it through system_config.subscription_catalog, after which the pricing page is authoritative.The yearly 1.2M credits are injected in full at payment, not monthly, and their validity follows the team license expiry. So yearly is both cheaper (¥9,999 versus ¥11,988) and front-loaded — but it also means anything unused lapses with the license if you do not renew.

​
Two billing modes

A shared pool hitting zero does not stop anyone. The underlying debit is clamped to the available balance (recorded as a 0-credit consumption) instead of throwing — this keeps the consumption record and the debit atomic inside one transaction.What that means: do not treat “members got blocked” as your balance alarm. Either watch the balance in the portal, or switch to quota mode for explicit blocking.(The settle-delta path permits a small overdraft; the database floor is −10,000 credits.)

​
Topping up the pool

1

Confirm your role

Only Owners and Admins can top up the pool. Make sure your active billing subject is Team.
2

Open the top-up page

From the billing page or the team portal.
3

Pick an amount

Same packs as personal top-ups. Both base and bonus credits land in the team pool.
4

Pay

Credits arrive immediately and every member can use them.
Members cannot top up the pool; they see “Team credits are topped up by admins.” Injection is idempotent per order number — one payment injects once, and a replayed callback never double-credits.

​
Usage reports

Owners and Admins get consumption reports in the team portal:
Per-member credit consumption — who the heavy users are, and how to allocate.

​
Switching billing subject

If you hold both a personal plan and team membership, the subject switcher decides which wallet is active.
  • Spending debits the team pool
  • The Team plan badge is shown
  • Shared org storage quota applies
  • The team portal entry appears in the avatar menu
  • Spending debits your personal credit account
  • Your personal plan is shown
  • Your personal storage quota applies
  • The team portal entry is hidden
Switch from the avatar menu in the top right.
Switching changes only the wallet and the plan display, never your conversations or files. All history is reachable under either subject.

​
Account isolation

The two accounts never merge or transfer. Leaving a team takes none of the pool balance with you.

​
Credit ledger

The billing page follows your active subject: under Team it shows the pool’s full ledger (every member’s consumption plus top-ups); under Personal it shows your own.

​
Failures and what to do

​
FAQ

Yes. Owners and Admins see per-member detail in the usage reports.
In shared-pool mode, nothing blocks immediately — debits clamp to zero and conversations continue while nothing further comes out of the pool. That means there is no loud signal that the pool is empty, so watch the balance. For explicit blocking, use quota mode.
The pool’s, shared by every member. The admin’s personal account is untouched.
No. Injection is idempotent per order number; a replayed payment callback does not double-credit.

​
Keep reading

Team overview

Entitlements and dual subjects

Member management

Invites, roles, seats

Expiry and renewal

Freezing and restoration

Billing units

How each unit is computed