> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/organization-administration/usage-entitlements-and-policy-limits.md). # Usage, entitlements, and policy limits Usage settings show resource consumption and the limits that apply to your organization. Set custom policies when a user, group, or project needs a different allowance. {% embed url="" %} ## Before you start Agree on the budget or allowance and its owner before changing limits. Record whether you are managing a user, a shared group, a project, or the organization plan. Use [Model usage analytics](/guides-and-quickstarts/evaluations-and-observability/model-usage-analytics.md) to investigate model usage and this page to understand policy enforcement. You need permission to view usage and manage limit policies. ## Review organization usage and defaults Open Settings → Usage and review runs, credits, seats, projects, and storage. ![Organization resource usage](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/9GJ43cdaPKe55LFacgUL/assets/g095-g095-01-overview.png) Read the units and limits associated with each measure. Review Organization Limits and per-user defaults. ![Organization limits and per-user defaults](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/6MQFRP3wHWWRYEMto8ks/assets/g095-g095-02-defaults.png) Confirm the scope and unit before changing a policy value. ## Understand which limits apply A custom value replaces the organization default for that same policy and target. Removing the custom value restores that policy's default. An unlimited value for one policy does not remove other policies or your organization's plan entitlement. Zero means no allowance under that policy. Credit policies for a workflow are checked together: the project policy, the authenticated user's policy, and the policies of each group that user belongs to. The organization credit entitlement also applies. Group credit usage is shared across that group's members; project credit usage is shared across runs of that project. Anonymous runs have no authenticated-user or user-group policy to check, but project and organization limits still apply. For example, if a user's credit policy has 100 remaining, their group has 20 remaining, and the project has 50 remaining, the user does not receive a combined allowance of 170. Each applicable policy must permit the run; an exhausted group policy can block it even when the user and project have remaining allowance. Raising only the user limit does not fix that block. Daily credit counters reset on the UTC day boundary. Policies labeled monthly reset on the UTC calendar-month boundary. Count-based limits, such as active project counts, measure existing resources and do not reset just because a day passes. Read the policy's unit and cadence rather than treating credits, runs, seats, and storage as interchangeable. Credit limits gate new runs and usage is recorded after execution. A run's final cost can take usage beyond the remaining allowance; these controls are not a promise to interrupt a running workflow at an exact spend amount. ## Set custom limits In Custom limits, select Add Limit and choose the intended user. ![Custom user limit selection](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/GdDFEyq7KWvKbMLDpxrF/assets/g095-g095-03-user.png) Set the policy values and review the selected account before saving. Choose Group scope when the limit should apply to a group. ![Custom group limit](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/PcXH5kI0iLy8BAXC9aa9/assets/g095-g095-04-group.png) Confirm the group and its credit or run limits together. Choose Project scope when the policy applies to a particular project. ![Custom project limit](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/D3JsoaSKyqJooMP321vG/assets/g095-g095-05-project.png) Keep the target project visible while reviewing the limit values. ## Maintain existing limits Open an existing limit's edit control to review or change it. ![Existing limit editing controls](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/tzpIHWdXADFQ821FpRgR/assets/g095-g095-06-edit.png) Check the saved scope and values before updating or removing the policy. Review the remaining custom limits and organization defaults. ![Custom limits and organization defaults](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/8dftXa4EcqWr88M4U9qy/assets/g095-g095-07-verify.png) A saved policy confirms the configuration, not the behavior of a request that exceeds it. ## Recover from a limit block 1. Read the blocked request's message and record the project, user, time, and named policy or entitlement. 2. In **Settings → Usage**, inspect the relevant organization entitlement, project policy, user's policy, and group policies with their current usage and reset cadence. 3. If the allowance is intentionally exhausted, wait for its reset or ask the authorized administrator to approve a change. For a count limit, reduce the relevant resource count or adjust the permitted allowance; waiting for a daily reset does not reduce a count. 4. Change only the intended policy after reviewing the scope and budget. If the organization plan entitlement is the blocker, changing a custom user limit will not remove it; involve the organization owner or support. 5. Retry a small representative request and confirm its actual result. If it remains blocked, pass the message and the inspected limits to [Support and deployment diagnostics](/guides-and-quickstarts/personal-settings-and-support/support-and-deployment-diagnostics.md). ## Important behavior Check each limit’s unit and scope before saving. Removing a custom limit does not remove plan entitlements or other applicable policies. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.stackai.com/guides-and-quickstarts/organization-administration/usage-entitlements-and-policy-limits.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.