01 THE RUNAWAY BILL
One invoice. No idea who spent it.
Without a cap, a handful of accounts can consume a month of budget in days, and nobody notices until the invoice arrives.
02 WHERE THE CAP SITS
Four places to stop the spend.
Each scope answers a different failure. Tenant protects the invoice, group protects a department, user protects everyone else from one person, agent protects you from the public.
03 ENFORCEMENT MODE
Which limits get checked.
Set the situation
Both is the strictest and the recommended default: a request has to clear every budget that applies to it, not just one.
04 THE PUBLIC AGENT
Anyone on the internet can use it.
A capped agent fails alone. An uncapped one takes the institution with it.
An agent budget is charged to the agent, not to whoever happened to open the widget, so abuse exhausts one line item instead of a real person's allowance.
05 WHO SPENT WHAT
The invoice, itemised.
Every figure here is attributable. Replenish a single user, raise one group, or cap an agent, without touching anyone else.
06 ROLES & PERMISSIONS
Same platform. Different powers.
Permissions are per role and per capability, so a tool can be switched off for students and left on for staff without deploying anything.
07 MAKE IT YOURS
Your name on the door.
Which of these would your CIO ask about first?
Illustrative figures · not product output