Teams, Seats & Token Budgets

CodeProso runs on your organisation’s Proso.ai tenant, so the same governance console that manages AskProso manages CodeProso too.

How tenancy works

1. Your organisation buys a Proso.ai plan.
2. An admin creates groups that match your teams — Platform, Payments, Mobile.
3. The admin assigns seats to teammates. Each person signs in to CodeProso with their own account and inherits their group’s policy.

Token budgets per team

In AskProso’s admin console, each group can have:

• a monthly and a daily token budget,
• a warning threshold (for example 75%) and a critical threshold (for example 90%),
• an optional hard limit that blocks new requests once the budget is exhausted.

Budgets roll up: individual caps sit inside team budgets, which sit inside the organisation budget. Teams can be tightened below the org ceiling, never raised above it.

What developers see

• A notice in CodeProso when their team crosses a warning threshold.
• A clear message if a hard limit blocks a request — work already on disk is never affected.
• Only the models their group is allowed to use.

Dashboards

Admins see CodeProso usage alongside AskProso in the same dashboards:

• tokens and spend by person, team and model,
• active teammates this week, and seats that were never activated,
• the audit log — every request attributed to a person, a team and a model.

Policy and features

Model access and feature gates are set per group — allowed, by exception or blocked. See the AskProso governance guide for the full model.