Limit Increase Requests
When model policies include spending limits, users can request higher limits and admins can resolve those requests.
User Flow
Section titled “User Flow”When blocked by policy limits, users can submit a limit increase request from policy warning workflows.
Admin Flow
Section titled “Admin Flow”In Admin Controls, admins can:
- View pending and historical requests
- Approve a request with an updated monthly limit
- Reject a request with resolution notes
Best Practices
Section titled “Best Practices”- Review requester usage context before approval.
- Set updated limits that match expected project demand.
- Revisit approvals in Analytics to confirm trend stability.
Related Guides
Section titled “Related Guides”Operational Playbook
Section titled “Operational Playbook”Use this playbook for repeatable administration:
- Review metrics and policy thresholds on a regular schedule.
- Apply the smallest viable permission or policy change first, then observe impact.
- Communicate policy changes to affected teams before enforcement windows.
Troubleshooting
Section titled “Troubleshooting”If governance controls are not behaving as expected:
- Confirm scope (global vs team vs user) and precedence rules.
- Validate that users are assigned to the correct teams and role groups.
- Re-check policy thresholds and effective dates when behavior appears delayed.
Frequently Asked Questions
Section titled “Frequently Asked Questions”Why are users still blocked after a policy change?
Section titled “Why are users still blocked after a policy change?”They may be affected by a stricter scope layer or stale session context.
How do we avoid over-permissioning?
Section titled “How do we avoid over-permissioning?”Use role-based defaults and grant temporary exceptions with explicit review dates.
What should we monitor weekly?
Section titled “What should we monitor weekly?”Spend trends, failure rates, exception volume, and policy-threshold pressure by team.