Budget management

Budgets let a Business workspace cap what any one member can spend from the shared credit pool, so one person building hard can't burn the whole month for everyone else. Manage them from Settings → Plans → Budgets (admins only).

Budgets are an allocation layer above the pool described in Plans and credit usage: that page covers where credits come from and what spends them; this one covers how you divide them up between members.

Turning it on

Budgets are a Business plan feature. On Pro or Free, the page shows an upgrade prompt instead. Once you're on Business, flip Enforce budget on — until you do, budgets are tracked and shown but nobody is actually blocked at their limit.

The default policy

With enforcement on, one editable sentence sets the rules everyone falls back to:

• Each member can spend N credits per month — the workspace default allowance.
• Warn them at N% — members see a warning in chat as they approach their limit.
• At the limit, stop new runs / allow a small overdraft of up to N% — a hard stop refuses new builds outright; a soft overdraft lets a member run a bit past their allowance (a share of the budget, not of whatever's left in the pool) before they're blocked.
• Someone who joins mid-month gets only the rest of the month / a full month's budget — whether a new member's first allowance is prorated to the days left in the period.

Change any part of the sentence and a Save defaults button appears — nothing is saved until you click it.

Per-member budgets

The Members table lists everyone who spends credits, with what they've used this period next to their budget. Click the pencil next to a member's budget to give them their own number, overriding the workspace default; clear it with the × to fall back to the default again. The Set by column shows where each member's current limit comes from — workspace default, a role default, a group, or a per-member override — so it's always clear why a number is what it is.

For a lot of members at once, use Import CSV: one row per member as email,credits, or email,clear to remove an override and fall back to the default.

Requests

When enforcement blocks someone, they can ask for more from inside chat. Pending requests land in Waiting on you at the top of the Budgets page, with who's asking, how much, and their note if they left one. Raise by N approves the request and raises that member's budget immediately; Decline dismisses it without changing anything.

Reading the pool card

Alongside the policy sentence, the Available credits card shows the workspace's overall pool balance, spend this month, and average daily burn, with a projection of whether the pool lasts the rest of the period at the current rate. This is the same shared pool from Plans and credit usage — member budgets divide it up; they don't add to it. If everyone's individual budgets add up to more than the pool holds, that's usually fine (budgets are ceilings, not reservations) but the pool can still run out before every budget is spent.

Who can do what

• Admins manage the policy, per-member budgets, and the request inbox.
• Members see their own remaining budget in chat as they build, get warned as they approach it, and can request more once they're blocked — they never see other members' numbers.

Next steps

• Plans and credit usage — where the shared pool comes from and what spends it
• Teams — the workspace members budgets apply to
• Roles and permissions — who has admin access to change budgets