Page history
Set a spend limit
claude-tag/admins/set-spend-limit
History
claude-tag/admins/set-spend-limit Changed · +3 / -11 lines
from line 6
<BetaNote /> -<div className="tm-stepbar"> - <a className="tm-stepbar-seg tm-done" href="/docs/docs/claude-tag/admins/pair-workspace">1 · Pair workspace</a> - <a className="tm-stepbar-seg tm-done" href="/docs/docs/claude-tag/admins/add-connections">2 · Give access</a> - <a className="tm-stepbar-seg tm-done" href="/docs/docs/claude-tag/admins/configure-github">3 · Connect GitHub</a> - <a className="tm-stepbar-seg tm-current" href="/docs/docs/claude-tag/admins/set-spend-limit">4 · Spend limit</a> - <a className="tm-stepbar-seg" href="/docs/docs/claude-tag/admins/test-it">5 · See it work</a> -</div> - 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. | Work | Bills to | Capped by |
from line 23
## Set the spend limit -If your organization bills through a reseller, this page is not available and these steps don't apply; your organization's usage is funded through the reseller instead. +Not every organization sees this page. A trial organization that hasn't enabled usage billing, a single-seat Team plan, an organization with a hybrid desktop deployment, or an admin whose role can't view billing is redirected to personal usage settings instead. If your organization bills through a reseller, the page is not available and these steps don't apply; your organization's usage is funded through the reseller instead. <Steps> <Step title="Open the usage page">
from line 70
## See spend by kind of work -On the analytics page at [`claude.ai/analytics/claude-tag`](https://claude.ai/analytics/claude-tag), you see channel spend split into four categories, so you can tell which kind of work is driving it. For each billed category you see its share of channel spend over the period you pick; Monitoring shows as not billed. The shares are approximate; for exact amounts, use your invoice. +On the analytics page at [`claude.ai/analytics/claude-tag`](https://claude.ai/analytics/claude-tag), you see channel spend split into four categories. The page refreshes once a day, so today's activity appears tomorrow and a new month is empty until its first complete day. The split shows which kind of work is driving spend. For each billed category you see its share of channel spend over the period you pick; Monitoring shows as not billed. The shares are approximate; for exact amounts, use your invoice. * **Engaged**: threads where someone @-mentioned Claude, replied to Claude, or asked it for a reminder * **Proactive**: work Claude picked up or started on its own, before anyone addressed it
from line 81
## Related resources -* [See it work](/docs/claude-tag/admins/test-it): run a first task in the pilot channel +* [Verify your setup](/docs/claude-tag/admins/setup-overview#verify-your-setup): run a first task in a channel * [Restrict where Claude Tag operates](/docs/claude-tag/admins/restrict-access#set-spend-limits): per-channel limits and the usage page in full
claude-tag/admins/set-spend-limit Changed · +3 / -2 lines
from line 9
<div className="tm-stepbar"> <a className="tm-stepbar-seg tm-done" href="/docs/docs/claude-tag/admins/pair-workspace">1 · Pair workspace</a> <a className="tm-stepbar-seg tm-done" href="/docs/docs/claude-tag/admins/add-connections">2 · Give access</a> - <a className="tm-stepbar-seg tm-current" href="/docs/docs/claude-tag/admins/set-spend-limit">3 · Spend limit</a> - <a className="tm-stepbar-seg" href="/docs/docs/claude-tag/admins/test-it">4 · See it work</a> + <a className="tm-stepbar-seg tm-done" href="/docs/docs/claude-tag/admins/configure-github">3 · Connect GitHub</a> + <a className="tm-stepbar-seg tm-current" href="/docs/docs/claude-tag/admins/set-spend-limit">4 · Spend limit</a> + <a className="tm-stepbar-seg" href="/docs/docs/claude-tag/admins/test-it">5 · See it work</a> </div> 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.
claude-tag/admins/set-spend-limit Changed · +11 / -0 lines
## See spend by kind of work
from line 75
DMs are separate. A DM bills to the sender's own seat, not to the organization's usage balance. +## See spend by kind of work + +On the analytics page at [`claude.ai/analytics/claude-tag`](https://claude.ai/analytics/claude-tag), you see channel spend split into four categories, so you can tell which kind of work is driving it. For each billed category you see its share of channel spend over the period you pick; Monitoring shows as not billed. The shares are approximate; for exact amounts, use your invoice. + +* **Engaged**: threads where someone @-mentioned Claude, replied to Claude, or asked it for a reminder +* **Proactive**: work Claude picked up or started on its own, before anyone addressed it +* **Scheduled**: recurring scheduled work +* **Monitoring**: Claude reading the channels it belongs to, which isn't billed + +Reading a channel Claude belongs to, whether or not anyone tags it, doesn't draw from the usage balance. When Claude starts a working session on its own, that session bills to the balance under Proactive. To stop Claude from starting work on its own in a channel, turn off the channel's [Respond automatically](/docs/claude-tag/users/when-claude-responds#turn-automatic-replies-on-or-off) setting. DMs aren't included, because they bill to the sender's seat. + ## Related resources * [See it work](/docs/claude-tag/admins/test-it): run a first task in the pilot channel
claude-tag/admins/set-spend-limit Changed · +5 / -4 lines
from line 15
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. -| Work | Bills to | Capped by | -| :--------------- | :-------------------------------- | :-------------------------------------------------------------------------------------------------- | -| Channel work | Your organization's usage balance | The spend limit, plus any [per-channel limits](/docs/claude-tag/admins/restrict-access#set-spend-limits) | -| A DM with Claude | The sender's own seat | The seat's usual limits, not the spend limit | +| Work | Bills to | Capped by | +| :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------- | :---------------------------------------------------------------------------------------------------- | +| Channel work | Your organization's usage balance | The spend limit, plus any [per-channel limits](/docs/claude-tag/admins/restrict-access#set-spend-limits) | +| Reading a channel, [deciding whether to reply](/docs/claude-tag/users/when-claude-responds#what-claude-does-with-a-channel-message), and short replies from what Claude already knows | Nothing | Not counted toward any limit. A working session Claude starts from the channel is channel work, above | +| A DM with Claude | The sender's own seat | The seat's usual limits, not the spend limit | ## Whether this step is required depends on your plan
claude-tag/admins/set-spend-limit First recorded · 80 lines, first recorded
# Set a spend limit ## Whether this step is required depends on your plan ## Set the spend limit ## What happens when the spend limit is reached ### Rate limits versus the spend limit ## Per-channel limits ## Attribute costs by channel ## Related resources
The first capture of this source. The page was already there, and this is what it said.
# 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 = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;
<BetaNote />
<div className="tm-stepbar">
<a className="tm-stepbar-seg tm-done" href="/docs/docs/claude-tag/admins/pair-workspace">1 · Pair workspace</a>
<a className="tm-stepbar-seg tm-done" href="/docs/docs/claude-tag/admins/add-connections">2 · Give access</a>
<a className="tm-stepbar-seg tm-current" href="/docs/docs/claude-tag/admins/set-spend-limit">3 · Spend limit</a>
<a className="tm-stepbar-seg" href="/docs/docs/claude-tag/admins/test-it">4 · See it work</a>
</div>
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.
| Work | Bills to | Capped by |
| :--------------- | :-------------------------------- | :-------------------------------------------------------------------------------------------------- |
| Channel work | Your organization's usage balance | The spend limit, plus any [per-channel limits](/docs/claude-tag/admins/restrict-access#set-spend-limits) |
| A DM with Claude | The sender's own seat | The seat's usual limits, not the spend limit |
## 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
If your organization bills through a reseller, this page is not available and these steps don't apply; your organization's usage is funded through the reseller instead.
<Steps>
<Step title="Open the usage page">
Go to [`claude.ai/admin-settings/usage/claude-tag`](https://claude.ai/admin-settings/usage/claude-tag).
</Step>
<Step title="Enter an amount">
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.
</Step>
</Steps>
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](/docs/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](/docs/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](/docs/claude-tag/admins/test-it): run a first task in the pilot channel
* [Restrict where Claude Tag operates](/docs/claude-tag/admins/restrict-access#set-spend-limits): per-channel limits and the usage page in full