Guardrails — Budget Owners

What this page is for

Budget Owners lets admins manage responsibility for costs across scopes. The workflow is intentionally preview-first: users prepare a change, run an impact simulation, then save only after reviewing affected events and cost allocation changes.

Who uses it

• Admins
• Finance owners
• FinOps teams

What you see

• Owner, scope, scope type, status, effective dates, creator, and archive state.
• Filters for search, scope type, and archived assignments.
• Detail sheet with IDs, user references, created by, effective windows, and timestamps.
• Preview sheet with impacted event count, impacted cost, before/after owners, before/after cost centers, and sample changed events.

What you can do

• Create an assignment.
• Edit an assignment.
• Archive an assignment.
• Search users and scopes.
• Preview impact before saving.
• Confirm the save from the preview sheet.

Permissions and safety

• Actions are hidden in read-only mode.
• Budget ownership changes should be treated as finance-sensitive.
• Preview should remain part of the standard workflow.

Operational notes

• Workspace scope does not require a free scopeId.
• Some scopes use catalog selection while others can accept text input.
• Status can be active, upcoming, ended, or archived.

What this page is not for

• Changing spend caps.
• Changing budget totals.
• Replacing the allocation ledger.

Recommended workflow

1. Confirm that you are in the right workspace and environment.
2. Use filters before changing configuration or interpreting results.
3. Open the detail drawer when available.
4. Check related objects such as alerts, approvals, costs, policies, runs, deliveries, or audit entries.
5. Apply changes only when the impact is clear.
6. Re-check the page after the backend refreshes.
7. Export or copy IDs when you need to escalate.

Related product areas

• /docs/product-guides/costs/allocation
• /docs/product-guides/guardrails/budget