Loading
Default enabled budget_caps_graphql_api and add usage cap documentation
What does this MR do and why?
This change adds a new "Usage caps" feature to GitLab's credit system that helps prevent unexpected billing charges. Organizations can now set monthly spending limits on GitLab Credits at both the subscription level (affecting all users) and individual user level. When these limits are reached, GitLab automatically suspends access to AI-powered features like Duo Chat and Code Suggestions until the next billing period starts or an administrator increases the cap. The system includes email notifications to billing managers when caps are hit, a dashboard to see which users are affected, and the ability to configure these limits through GitLab's customer portal. This gives administrators better control over AI feature costs and prevents surprise overage charges.
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to:
Edited by Suraj Tripathi