Govern AI spend

Who can do this

Every Admin can open the Control Center and set weekly budgets on its People and Rules tabs. Allocations, build mode, model choice and the Spend response tab, and the Usage page, are available to Admins in organizations where Ronja has enabled billing access. Buying credits requires the Super Admin.

You govern AI spend from two places in the admin sidebar’s Billing & Control group: the Control Center, which sets the rules, and the Usage page, which shows where credits went. Usage needs billing access; the Control Center opens for every Admin, and without billing access it shows weekly budgets only. This page is the map; each lever links to its deep dive. What credits are and what happens at depletion is covered in Credits and AI spend.

The levers in the Control Center

The Control Center has three tabs: People (what each member can do right now, and why), Rules (what each limit does, and every rule in one table) and Spend response (what happens as the organization spends, and the default models). The levers it holds:

• Weekly budget: a per-person cap on credits for chats, every week, open to every Admin; see Weekly AI budgets below.
• Billing-period allocation: a per-person cap for each billing period (Credits per billing period, No limit or Blocked), set as a default, per role, or for one person. A limited allocation never stops an Admin; Blocked stops everyone.
• Build mode: which roles and people can use Build mode. Deep-analysis chats don’t need it.
• Choose model & effort: who may pick their own model and effort in chat (everyone, by default). It is a permission, not a spending limit, and nobody can pick while the organization is out of credits.
• Spend steps on Spend response: at a percentage of the organization’s credits for the billing period, Email a warning, Warn members in chat, or Switch chats to the reduced models (a member’s own pick is kept).
• Default models on Spend response: the standard and reduced model and effort for Analyst chats and for Build & deep analysis chats.

A person’s weekly budget and allocation never switch their model: only the organization’s reduced-models step does, and it fires on the whole organization’s credits. See What each limit does, and for the full walkthrough of each tab, Control Center.

Weekly AI budgets

A weekly budget caps how many credits each person can spend in their chats each week, as a default for each person, per access group, or as a personal exception. It is the one lever every Admin can reach, with or without billing access, because it binds Admins too: unlike a limited allocation, which never stops an Admin, a used-up weekly budget stops an Admin’s chats until Monday 00:00 UTC. See Set weekly AI budgets.

Buying credits (Super Admin)

Topping up the wallet happens on the separate Billing page and requires the Super Admin. In an organization billed by invoice, enter a Credit amount, check the live cost preview, and confirm: credits land immediately, and “the cost is added as a line on your next invoice — your card is not charged.” An organization that pays by card buys with its saved card instead: Buy credits charges it, and the credits appear in the wallet once the charge succeeds. The full flow is in Usage & billing.

Seeing where credits went

The Usage page traces every credit from the source that triggered it to the model behind it, and lets you group spend by user, model, or mode. See Usage & billing.

See also

• Control Center — the deep dive on People, Rules and Spend response.
• Usage & billing — the deep dive on the Usage page and buying credits.
• Credits and AI spend — the concept behind it all.
• Monitor activity and usage — the counts side of admin monitoring.