> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudthinker.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Credit Limits

> Set monthly credit budgets per workspace, choose throttle or notify-only enforcement, and alert the owner at 80% and 100%

Credit limits cap how much of your organization's shared [credit](/guide/billing/usage) pool each [workspace](/guide/workspaces) — an isolated environment for one team or project — can spend per month. Set one default policy, then override individual workspaces that need a bigger or smaller budget.

## Prerequisites

* A **Scale, Scale+, or Enterprise** plan — see [plan features](/guide/billing/pricing#ai-features-by-plan). On lower plans the page shows an upgrade prompt instead.
* An organization **Owner** or **Admin** account. Both roles can view and edit credit limits.

## Set the default policy

The default policy applies to every workspace that has no override of its own.

<Steps>
  <Step title="Open Credit limits">
    Go to **Admin Settings → Credit limits**.
  </Step>

  <Step title="Choose the enforcement mode">
    Under **When a workspace hits its monthly limit**, pick **Throttle** or **Notify only**. See [How enforcement works](#how-enforcement-works) for what each does.
  </Step>

  <Step title="Set the default monthly limit">
    Enter a credit amount per workspace, or choose **Unlimited** to track usage without a cap.
  </Step>

  <Step title="Pick the alert thresholds">
    Under **Alert the organization owner at**, check **80% of monthly limit**, **100% — limit reached**, or both.
  </Step>

  <Step title="Save">
    Click **Save**. **Success state:** the change counter clears and the policy summary shows your mode and limit.
  </Step>
</Steps>

## Override a single workspace

<Steps>
  <Step title="Find the workspace">
    On the same page, use **Search workspaces** to filter the table.
  </Step>

  <Step title="Edit its limit">
    Click the workspace's limit cell and enter a credit amount, or choose **Unlimited**. The meter beside it shows usage against the limit for the current cycle.
  </Step>

  <Step title="Set its enforcement">
    Use the row's enforcement control to pick **Throttle** or **Notify only** for that workspace alone.
  </Step>

  <Step title="Save">
    Click **Save**. Overrides win over the default policy; every other workspace keeps following the default.
  </Step>
</Steps>

## How enforcement works

| Mode            | What happens at the monthly limit                                                                                                                                                                                                         |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Throttle**    | Paid credit spend stops in that workspace — premium, bonus, and Pay-As-You-Go credits are all blocked. The 100 free daily credits keep working, so Light-tier chat continues. Spend resumes when the cycle resets or you raise the limit. |
| **Notify only** | Nothing is blocked. The workspace keeps spending; you rely on the alerts.                                                                                                                                                                 |

* **Limits follow your billing cycle.** Each workspace's counter resets when your credits do — monthly, including on annual plans.
* **Alerts go to the organization owner** as an in-app notification plus an email, once per threshold per cycle, usually within an hour of crossing 80% or 100%.
* **The summary cards** above the table show **Monthly usage** (pool spent so far), **Allocated** (the sum of all workspace limits — **Unlimited** if any workspace is uncapped), and **Resets in** (time to the next cycle).

<Tip>
  Allocated can exceed your organization's credit pool — limits are ceilings, not reservations. Use **Throttle** on experimental workspaces so a runaway agent run can't drain the budget production teams need.
</Tip>

## Next steps

<CardGroup cols={2}>
  <Card title="Usage" icon="coins" href="/guide/billing/usage">
    How credits work, model tiers, and the warnings CloudThinker sends
  </Card>

  <Card title="Pricing" icon="credit-card" href="/guide/billing/pricing">
    Compare plans and see which include credit limits
  </Card>
</CardGroup>