Govern AI spend

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 and the daily AI safety limit 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:

Monthly budget: where your organization has one, a limit on the whole organization’s usage each billing period, open to every Admin; see Monthly budget below.
Daily AI safety limit: an organization-wide safeguard that pauses all AI until 00:00 UTC once today’s AI use reaches it, open to every Admin; see Daily AI safety limit below.
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.

Monthly budget

An organization Ronja bills by invoice can have a monthly budget: a limit on the whole organization’s usage each billing period, counted as on your invoice without the platform fee. Any Admin raises or lowers it in the Monthly budget section of the Rules tab; only Ronja can remove it. Admins are emailed at 80% and when it is used up, your spend steps act at percentages of it, and once it is used up new chats and runs stop for everyone, admins included, until the next billing period or a raise. See Monthly budget.

Daily AI safety limit

The daily AI safety limit protects the organization from an unexpected spike in AI use, such as a runaway agent or a loop. Ronja sets a limit for every organization, and any Admin can set your organization’s own, lower one on the Rules tab, in Credits per day, counted as on your bill; the lower of the two applies. When today’s AI use reaches it, AI pauses for everyone, admins and automations’ Agents included, until 00:00 UTC; workflows that don’t use AI keep running, and so does Ronja’s own background work, such as naming chats, which still counts. Admins are told at 80% or more and when it is reached, and every Admin sees today’s percentage on People and Rules. It is a safeguard, not a billing problem. See Daily AI safety limit.

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.