Manage Unity Gateway budgets at scale
After you create budgets, this page shows how to handle limits and increase requests without routing every decision through account admins. To create budgets and set thresholds, see Set budgets and spend limits for Unity Gateway.
Budget management workflow

- Delegate: An account or workspace admin creates a budget for each team and makes the team owner its Budget Manager. See Delegate budget management to team owners.
- Show limits: Users check their remaining budget and know who to ask before they're blocked. See Show users their spend limits.
- Handle requests: A user who needs more requests an increase, and the team owner approves or declines it. See Automate budget increase requests and approvals.
- Adjust limits: Team owners review repeated requests, then change limits or reduce costs so the work fits the budget. See Analyze repeated requests and adjust limits.
Delegate budget management to team owners
Exceptions move faster when someone close to the workload can approve them. Each budget has an access control list (ACL), so you can grant a team owner a role that lets them adjust thresholds and overrides without an account admin. Grant one of these roles to a user, group, or Databricks service principal:
- Budget Manager (
roles/budget.manager): View the budget, edit its thresholds and per-user overrides, and grant or revoke roles for others. - Budget Viewer (
roles/budget.viewer): View the budget and its configuration.
Users who hold a budget role but are not admins use the Budget API instead of the Budgets UI. See Manage budget permissions for the full permission matrix.
To structure budgets for many teams:
- Separate a workspace, or a set of models, for each team. For example, use a
team-ml-platformworkspace, or tag the team's model services withteam=ml-platform. - Create one budget per team or cost center with Unity Gateway as the resource type, scoped by workspace, by a service tag such as
team=ml-platform, or both. See Create a budget. - Set a shared monthly threshold for the team, plus optional per-user daily and monthly thresholds and overrides.
- Grant the team owner or a delegate group the Budget Manager role. Grant Budget Viewer to anyone who needs read-only access, such as finance partners.
- Keep an account-wide Unity Gateway budget, with no workspace or tag filter, as a backstop. A user can count toward several budgets, and each budget enforces its own thresholds.
Grant a budget role with the account access-control Databricks CLI command group. Read the budget's rule set first, because an update replaces its entire grant_rules list and requires the etag from the latest read:
databricks account access-control get-rule-set \
"accounts/<ACCOUNT_ID>/budgets/<BUDGET_ID>/ruleSets/default" "" \
--profile <PROFILE_NAME>
databricks account access-control update-rule-set --json @<RULE_SET_FILE>.json --profile <PROFILE_NAME>
Verify by reading the rule set back. For the rule set file format and the full steps, see Manage budget permissions. Permission changes can take 30 seconds or longer to propagate.
To give team owners a report of their team's spend, see Report spend by department or cost center and Build a team spend dashboard for managers.
Show users their spend limits
Users who can see their remaining budget adjust their work before they're blocked. Developers using coding agents run ug usage --all to see each limit with the percentage used, the remaining amount, and the ID of the budget that enforces it. See Monitor budget spend. So users know who to ask for more, publish each budget's ID and its Budget Manager where they already look, such as your team onboarding docs.
As a user's spend approaches the limit, smart defaults can recommend a lower-cost model so the same work costs less. See Set model defaults and smart defaults.
Automate budget increase requests and approvals
Use your existing chat or ticketing system to collect requests for higher limits. Send each request to the manager of the budget that limits the user's spend. The manager can approve or decline the request in the same place. This workflow requires a custom integration.
Receive threshold events with webhooks
Budget webhooks can automatically notify a custom destination when spend reaches a threshold. For example, a webhook can notify the user who reached the threshold, who can then start a workflow to request a budget increase. Users can also request an increase directly, before they reach their limit. A webhook can start the review, but the budget manager decides whether to approve the increase.
Budget webhooks are in Beta and aren't available in government or regulated environments. To get started, enable the Account-level Webhook Destinations preview, create a webhook destination, and add it as a threshold action. See Trigger custom webhooks.
Give the approver enough context
Build a custom solution that lets users include the budget, the limit they want to change, the requested amount, and the reason for the increase. For a manual request, the user can share their limit and remaining budget from ug usage. For a webhook-triggered request, use the spend recorded in the event. The Budget Spend Status API returns only the caller's own spend.
Request BUD-1042: Raise my monthly personal limit from $20 to $40 so I can finish this month's evaluation runs.
Budget: ML Platform Unity Gateway budget
Spend when requested: $18.50 of $20
Approver: ML Platform Budget Manager
Apply and confirm the approved increase
After approval, you can configure automation to use the Budget API to update the requester's override on the applicable per-user threshold. If a shared threshold is blocking the user, route the request to the owner of that budget. A per-user override doesn't lift a shared limit.
Read the budget back to verify the new limit, then confirm it in the original thread or ticket. A per-user override stays in effect until someone changes or removes it.
Analyze repeated requests and adjust limits
Repeated exception requests are a signal that a limit no longer fits the work. Have your integration write each request and its outcome to a Unity Catalog table. Add that table and the combined spend view to a Genie Agent, then ask questions such as:
- Which teams requested a budget increase more than three times in the last 90 days?
- After each approved increase, did the team use the added headroom in the next 30 days?
- Should any team's per-user default change, based on how often its members request increases?
When recurring exceptions reveal costly usage patterns, see Control spending.