Skip to content

Set weekly AI budgets

A weekly AI budget caps how many credits one person can spend in their chats with Ronja each week. Each person gets their own amount every week. It isn’t a shared pool: one person using theirs doesn’t reduce anyone else’s. Weeks run from Monday 00:00 UTC to the next Monday 00:00 UTC, when everyone’s budget resets; the Control Center shows the current week’s dates.

You set the budgets on the Rules tab of the Control Center (admin sidebar → Billing & Control → Control Center → Rules), and see each person’s budget on its People tab. If your organization doesn’t have billing access, those two tabs show weekly budgets, the daily AI safety limit and, where your organization has one, the monthly budget only.

A weekly AI budget is separate from the billing-period allocation that Admins with billing access can set. Both apply at the same time, and a prompt is refused as soon as either one is used up. See Weekly AI budget vs Allocation.

A weekly budget never switches anyone to a different model, and your organization’s spend steps (such as reduced models at 95%) never apply to it. See What each limit does.

Above every weekly budget sits the organization’s daily AI safety limit, a safeguard shared by the whole organization: once it is reached, it pauses all AI, automations’ Agents included, until 00:00 UTC. While it has paused AI, a person sees that pause rather than their weekly budget, and extra weekly credits don’t lift it. It counts credits as on your bill, so its numbers aren’t directly comparable with a weekly budget’s.

  1. A personal exception wins over everything else, even when it is lower.
  2. Otherwise the person gets the highest budget among the access groups they belong to. No limit beats any number. A group budget applies even if it is lower than the default, so you can give Interns 20 credits while everyone else has 100.
  3. Otherwise the Default for each person applies.
  4. With none of these set, the person has no weekly limit.

Weekly budgets have no role rule: access groups take that place.

  1. Open the Control Center and go to the Rules tab.
  2. In the Weekly budget row, click the value in the Default for each person column (for example 100 / week or No weekly limit). The dialog is titled Weekly budget: default for each person.
  3. Under Weekly budget, choose Credits per week and type an amount, or choose No weekly limit to remove it.
  4. Click Save.
  1. In the Weekly budget row, click Set a group budget, or click the budget of a group that already has one.
  2. Choose the Access group.
  3. Under Weekly budget, choose Credits per week and type an amount, or No limit. Use the default for each person removes the group’s own budget.
  4. Click Save.

Access groups that include everyone in the organization can’t carry a budget: they always use the default. A group budget stops counting as soon as the group is moved to the trash or starts including everyone. The row then marks it “not in effect”, and Remove deletes it. When someone is in several groups with a budget, the row says which group’s budget applies to them.

  1. In the Weekly budget row, click Add exception under Personal exceptions, or click Add exception in the Weekly budget section of that person’s panel on the People tab.
  2. Choose the Person.
  3. Under Weekly budget, choose Credits per week and type an amount, or choose No limit.
  4. Enter a Reason. It’s kept with the exception and recorded in the audit log.
  5. Click Add exception.

To change an exception, click its value in the row (or Edit exception in the person’s panel). Remove (or Remove exception) deletes it.

The People tab lists every member with their Weekly budget, the rule it came from (Personal, an access group’s name, or Default), and how much of it they have used this week as a bar and a percentage. Near a limit filters to the people at 75% or more; Stopped to the people whose chats are refused. Click a person to see every rule that could apply to them, with the one that does marked. See A person’s panel.

The page shows usage only as a percentage of each person’s own budget. It never shows how many credits someone spent.

When someone runs out before Monday, you can top them up for the rest of the week without changing their budget.

  1. On the People tab, click the person, then Give extra credits this week. The button is there for anyone whose budget has a limit.
  2. The dialog shows how much of their budget they have used so far. Extra credits starts at 50; change it if you like, up to 1,000,000 credits at a time.
  3. Enter a Reason. It’s kept in the audit log.
  4. Click Give credits.

The extra credits are added to their budget until Monday at 00:00 UTC, then they disappear, so they never turn into a permanent raise. If you give extra credits more than once in a week, they add up. The person can send again straight away and isn’t sent a message about it. Their budget then shows the extra credits, for example “200 + 50 this week”.

To take extra credits back before Monday, click Remove extra credits in the person’s panel on the People tab, or next to their name under This week only in the Weekly budget row on the Rules tab. It removes all of that person’s extra credits for this week at once.

Extra weekly credits only lift the weekly budget. If the person is stopped by their billing-period allocation or because the organization has used all its credits, they won’t help, and the dialog says so. They don’t lift a used-up monthly budget or a pause by the daily AI safety limit either.

When someone uses up their weekly budget, your admins hear about it by email (titled “Someone used up their weekly AI budget”) and in Ronja’s notifications, or in Slack if that is how your organization routes this notification. It names the person and links to the People tab with their panel and the Give extra credits dialog already open. You hear about each person once a week, and again only if they also use up extra credits you gave them. The person themself isn’t told, even if they’re one of the people who normally get this notification.

This notification is on by default: until your organization sets up notification delivery, it goes to your admins. To send it somewhere else, or turn it off, use the Someone used up their weekly AI budget row on the Notification routing page (admin sidebar → Governance).

When someone has used 75% or more of their weekly budget, a grey line above the chat box says how much, and when it resets in their own time zone. For example: “You’ve used 82% of your weekly AI budget. Resets Mon 02:00.” Once it’s used up, the line reads “You’ve used your weekly AI budget. Resets Mon 02:00. Contact an administrator if you need more.” and new prompts are refused until the reset.

A refused prompt keeps its own message, which gives the reset time in UTC: “You’ve used your weekly AI budget. It resets on Monday at 00:00 UTC. Contact an administrator if you need more.” People only ever see their own budget, never the organization’s.

Anyone with a weekly budget can also check it at any time in the account menu (click your name at the bottom of the sidebar). Weekly AI budget shows how much is left, for example “53% left”, and when it resets, for example “Resets in 4 days”. Once it’s used up, it reads Used up with the reset time in your own time zone. The row is shown only while a weekly budget limits you; it isn’t shown if you have no limit, or if your billing-period allocation has already stopped your chats.

Only a person’s own chats in Ronja count, including the work Ronja does with her tools during a chat. The runs of automations, workflows and Saved Agents, and conversations in Slack or Microsoft Teams, don’t count toward anyone’s weekly budget, and a weekly budget never stops them. Work a chat hands to a Saved Agent doesn’t count either.

Budgets are checked before each prompt, so a chat that started under the budget runs to the end, and spending can go a little past a budget before the next prompt is refused.

Answering or skipping a form, or approving a step, in a chat continues Ronja’s work, so it’s checked too:

  • Once your weekly budget is used up, Approve, Skip for now and submitting a form are refused with the same message, and the form or step waits until your budget resets or a colleague who still has budget answers it. Credentials you typed into a refused form stay in the form.
  • Reject still works: it ends the step without Ronja continuing, so it costs nothing.
  • In a shared chat, the budget that counts is that of the person answering.
  • In a chat an automation started, answering or deciding in the chat itself counts toward your budget, and everything except Reject is refused once it’s used up. A decision made from an emailed or Slack approval link isn’t refused, and counts toward the chat owner’s budget. So does a request for approval that expires unanswered, which Ronja treats as rejected before carrying on.

To see where the organization’s credits go overall, see Govern AI spend and Credits and AI spend.