Product Guides•stable•Updated 2026-05-15

Guardrails — Caps

Create and manage spend caps across supported scopes.

What this page is for

Caps administrates spend thresholds by scope. It helps teams define limits, monitor current spend against those limits, and quickly request an exception when a cap is near or reached.

Who uses it

Admins
Finance users
Platform teams

What you see

Caps list with scope type, scope label, window, behavior, enabled state, archive state, limit, current spend, percentage used, and status.
Summary counts for caps near and reached.
Filters for search, scope type, status, enabled state, and archived state.
Window range and amount source.

What you can do

Create a cap.
Edit a cap.
Duplicate a cap.
Archive a cap.
Enable or disable a cap inline.
Request an exception when a cap is near or reached.

Permissions and safety

Editing requires the relevant cap permissions.
Read-only users should still see status and risk.
Archived caps are shown only when includeArchived is enabled.

Operational notes

Supported scopes include workspace, team, project, provider, model, feature, customer, and cost center.
Workspace caps do not require a scope ID.
Team and project scopes should use workspace catalog selections when available.
Provider, model, feature, customer, and cost center can use text input if no catalog exists.

What this page is not for

Editing exception approvals directly.
Explaining every cost driver behind the cap.
Replacing Forecast or Cost Signals.

Recommended workflow

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