Skip to main content

Manage budgets

The Budgets screen is where you set what people may spend. It has three tabs, which correspond to the three decisions involved: the group budgets, the user budgets, and the defaults that apply to everyone without one.

For how enforcement behaves, including the fact that a caller with no budget is refused rather than allowed, read Budgets and pricing first. This page covers doing it in the console.

Defaults​

Start here on a new deployment. A default gives every user a budget without you creating one per person, which matters because enforcement is fail-closed: a user with no applicable budget cannot make requests at all.

Set a default limit and period, and every user who has no budget of their own inherits it.

Group budgets​

The Group budgets tab lists each group's budget with its period, limit, current spend, and utilization.

Each group budget carries a priority. When a user's own budget is absent or exhausted, the request charges the first group budget, in priority order, that still has headroom. Priority is what you use to express "charge the team budget before the department budget".

Create a group budget by choosing a group, a period of daily, monthly, or yearly, and a limit. Periods are calendar-aligned rather than rolling from first use, so a monthly budget resets on the first of the month.

User budgets​

The User budgets tab lists every user with their budget source, period, and limit. The source column distinguishes a user on the organization default from one with a custom limit, which is the quickest way to see who has been given an exception.

Editing a user's limit takes effect on the next request. There is no restart and no counter reset, so raising a limit is the way to restore access to someone who has run out mid-period without waiting for the period to roll over.

Which budget gets charged​

A user's own budget is always tried first, whatever their group membership and whatever the group priorities say. Only when it is absent or exhausted does the request fall to group budgets, in priority order.

That ordering is fixed rather than configurable, so a per-user exception always wins over the group's cap.

Next steps​