> ## Documentation Index > Fetch the complete documentation index at: https://claude.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Set a spend limit > Claude Tag draws from your organization's usage balance, not individual seats. See whether you need to fund usage, how to set the spend limit, and what happens when it's reached. export const BetaNote = () => Claude Tag is in public beta. Features and behavior described here may change before general availability.;
1 · Pair workspace 2 · Give access 3 · Spend limit 4 · See it work
Work Claude does in channels bills to your **organization's usage balance**, not to individual seats. The **spend limit** is a cap you set on how much of that balance Claude Tag can use each billing period. (DMs are separate: a DM bills to the user's own seat, not to this balance.) ## Whether this step is required depends on your plan | Your plan | What you need to do here | | :------------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Team** | **Required, before anything runs.** A Team plan has no usage balance until it's funded, and Claude won't respond in channels until it is. A [launch usage credit](https://support.claude.com/en/articles/15575654-claude-tag-launch-promo-for-claude-team-and-enterprise) counts as a funded balance, so check for one before buying credits. Then set a spend limit. | | **Enterprise (invoiced)** | **Recommended.** Usage bills to your invoice with no upper bound until you set a spend limit. Set one to cap exposure during the pilot. | ## Set the spend limit Go to [`claude.ai/admin-settings/usage/claude-tag`](https://claude.ai/admin-settings/usage/claude-tag). Enter an amount in your organization's billing currency. The spend limit resets at the start of each billing period and applies across every paired workspace. You can change it any time. There's no published per-task cost guidance. For a pilot, set a spend limit you're comfortable with for the first billing period, then watch the per-channel usage breakdown on the same page and adjust. ## What happens when the spend limit is reached When usage reaches the spend limit, Claude stops and tells the requester in the thread that it couldn't finish. The requester can ask an admin to raise the limit. The spend limit counts usage at list price. If your organization has a negotiated discount, that discount applies at invoice time, not to the cap. ### Rate limits versus the spend limit The spend limit caps how much your organization is charged. It doesn't change how fast Claude can work. Claude Tag also applies its own throughput limits on how quickly threads can be started and messages delivered, and an organization with many busy channels can hit one while the spend limit still has plenty of room. When that happens, Claude tells the requester in the thread that it hit a rate limit and names a short wait, usually a few seconds. Re-send the message after the wait. Raising the spend limit doesn't clear a rate limit, and a rate-limited request doesn't spend anything. | Claude says | Limit reached | What to do | | :--------------------------------------------------------------------- | :--------------- | :------------------------------------------------------------------------------------------------------------------- | | The spend limit is reached | Spend limit | Raise it on the usage page above | | It hit the session rate limit, or is rate limited delivering a message | Throughput limit | Wait the few seconds the reply names, then re-send. If your organization hits this often, contact your account team. | ## Per-channel limits Per-channel limits and the per-channel spend breakdown are on the same usage page. See [Set spend limits](/claude-tag/admins/restrict-access#set-spend-limits) for the full set of controls. ## Attribute costs by channel Channel work can't be attributed to individual users. It bills to your organization's usage balance, not to any user's seat, and often has no single requesting user (several people contribute to one thread, and scheduled jobs run without anyone asking). The channel is the unit you can attribute. The usage page at [`claude.ai/admin-settings/usage/claude-tag`](https://claude.ai/admin-settings/usage/claude-tag) shows spend broken down by channel. To attribute spend to teams or departments for showback or chargeback reporting, structure channels so each maps to one team or department, and give those channels [their own scopes](/claude-tag/admins/attach-to-scope). The per-channel breakdown then reads as your per-team report, and per-channel spend limits act as team-level budgets. DMs are separate. A DM bills to the sender's own seat, not to the organization's usage balance. ## Related resources * [See it work](/claude-tag/admins/test-it): run a first task in the pilot channel * [Restrict where Claude Tag operates](/claude-tag/admins/restrict-access#set-spend-limits): per-channel limits and the usage page in full