--- title: "Manage Users and Credit Limits" canonical: "https://documentation.chaos.com/space/LIC5/860651522/Manage%20Users%20and%20Credit%20Limits" format: markdown --- This page explains how to set per-user credit limits and how to respond when users request more credits. ## **Floating Credit Limit** --- When the Chaos Credits system is set up for your organization, **every user starts with Unlimited access to the Floating pool**. This applies to anyone whose access was migrated from the previous credit systems on May 27, 2026. > ℹ️ You only need to read further if you want to *restrict* a user's access — by capping them at a specific number, or by blocking them entirely. A Credit Limit is a per-user spending cap on the Shared pool. It controls how much an individual user can draw from the pool within a cycle. A few key things to know: - **Limits are caps, not reservations.** Setting a 500-credit limit on a user doesn't lock 500 credits in the pool for them. If the pool only has 50 credits left, that user can spend at most 50 — regardless of their limit. - **Limits are independent of subscription changes.** When a subscription expires and the pool shrinks, per-user limits don't automatically adjust. You decide when to update them. - **Limits apply only to the shared pool.** They don't restrict Named credits — those have their own per-user allowance. ## **How limits reset** --- A credit limit resets **one month after it was set**. For example, if you set a 500-credit limit on a user on the 15th of March, their usage against that limit resets on the 15th of April — they get a fresh 500-credit cycle to spend. From then on, it resets monthly on the 15th. This means each user's limit cycle is tied to when *their* limit was created, not to your subscription billing dates or the calendar month. If you set limits for different users on different days, they'll reset on different days too. If you change a user's limit, the new value applies immediately and the existing cycle continues — only the cap changes. The reset date doesn't shift. ## **When to set a limit** --- Set per-user credit limits when you want to: - Prevent unintentional consumption from the shared pool. - Give certain roles (interns, contractors, occasional users) a smaller share. - Plan ahead for project budgets — for example, capping a department at a fixed monthly amount. ## **How to set a limit** --- You can set limits **in bulk** (for multiple selected users) or **per user**. Both routes open the same **Set credit limit** dialog. The user's new limit takes effect immediately. Credits they've already used in the current cycle count against the new limit. > ℹ️ The 1,000 and 5,000 chips are starting points, not Chaos-recommended values. Pick whatever fits your budget and team size. > ℹ️ > ℹ️ **Custom** lets you set anything from 1 credit upward. ## **Reading the user table** --- ## **When a user requests more credits** --- When a user runs out of credits — either because the pool is empty or they've hit their credit limit — they can click **Request credits** on their Credits page or inside their product. The button immediately changes state to **Requested**, and an email is sent to you. You have three options: 1. **Raise their limit.** From the **⋯** menu next to their row, choose **Set credit limit** and set a higher number. 2. **Buy a credit pack.** If the whole pool is dry, top up to refill it for everyone. 3. **Deny the request.** If you've intentionally capped this user, no action is needed — they'll wait until the next reset or refresh. The user can’t override their limit. ## **Notifications** --- At the May 27, 2026, launch, the credit system includes one built-in notification: **an email to admins when a user clicks *****Request credits***. No additional configuration is needed — this happens automatically. You can monitor pool health by checking the dashboard's color-coded usage indicators or by reviewing the **Usage overview** chart on the Credits page. ## **Admin vs. User permissions at a glance** --- | **Capability** | **Admin** | **User** | | --- | --- | --- | | View pool balance (summary) | :check_mark: | :check_mark: | | View **Shared pool details** breakdown across all sources | :check_mark: | :cross_mark: | | View **Usage overview** chart (own) | :check_mark: | :check_mark: | | View other users' usage | :check_mark: | :cross_mark: | | Set, edit, or remove per-user credit limits | :check_mark: | :cross_mark: | | Allocate Named licenses to users | :check_mark: | :cross_mark: | | Export usage report (CSV) | :check_mark: | :cross_mark: | | Request more credits (**Request credits**) | (sees **Buy credits** instead) | :check_mark: | ## **Tips for managing usage well** --- - **Trust the default.** Every user starts with **Unlimited** access. Only step in when you see a specific reason to cap someone — there's no need to set limits proactively. - **Watch the orange and red flags.** The usage table color-codes users so you can act before someone hits their limit and gets blocked. - **Use the usage report.** The **View usage report** button (top right of the dashboard) shows which features and which users are driving the most consumption. That data is your best guide for adjusting limits, planning top-ups, or making the case for a subscription upgrade. - **Communicate limit changes.** When you lower a user's floating credit limit, let them know — otherwise, they may run into a "credit limit reached" message without warning.