Attribute costs to users changedclaude-tag/admins/attribute-costs

Nearest release: v2.1.283, published 5 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 25 Sep 2026 23:59 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 26 Sep 2026 00:07 UTC.

Upstream edited 25 Sep 2026 23:59 UTC

Recorded here 26 Sep 2026 00:07 UTC

Lines+6added

Lines−1removed

From line 37 where the diff opens

First seen 10 Sep 2026 this site's first read of the page

Recorded edits2to this page, all time

The whole hunk

from line 37, old and new numbered

lines

from line 37

3737* **Work someone asked for goes to the person who asked.** Spend for each of Claude's replies goes to the member whose message Claude was responding to, so when several people address Claude in one thread, the spend is split across them.

3838* **Work Claude picks up on its own goes to a person in the thread where it did the work.** That person is the member whose message Claude acted on, if there is one. Otherwise it is whoever mentioned Claude into the thread, or, if no one did, the person who started the thread.

3939* **Scheduled routines go to the person who set the routine up.**

40* **The null row collects spend with no attributable person.** Examples are work Claude started on its own in a thread that another app or bot posted, and a routine whose creator can't be identified. Monitoring, meaning Claude reading a channel it was asked to watch, is never attributed to a user. Per-user rows therefore sum to less than your total channel spend.

40* **The null row collects spend with no attributable person.** Examples are:

41 * the [channel session's](/docs/claude-tag/concepts/how-it-works#lifecycle-of-a-request) own work

42 * work Claude started on its own in a thread started by Claude, another app, or a bot

43 * a routine whose creator can't be identified

45Per-user rows therefore sum to less than your total channel spend.

4146

4247Per-user attribution doesn't change billing. Channel work still bills to your organization's usage balance, not to any user's seat. See [Set a spend limit](/docs/claude-tag/admins/set-spend-limit) for the billing split.

4348