Claude Enterprise adds project tags for tracking costs Claude Enterprise adds project tags for tracking costs

A project becomes a reporting unit

The release connects an existing unit of work to the codes a business already uses. Consider a hypothetical consultancy whose engineer spends $30 on one client assignment and $70 on another. A member-level total would show $100 for that engineer. An assignment-level report can instead support a discussion about the two clients, provided the underlying work qualifies for attribution. These are illustrative amounts, not measured results or Anthropic prices. The distinction becomes useful when several employees contribute to one assignment, or one employee handles several assignments. Neither the employee total nor the client total alone describes both relationships.

The tag is not a spending gate

Anthropic's documentation explicitly excludes spending limits by tag. Attribution also has timing rules: a new tag takes about two hours to take effect, and the report extends through the previous UTC day. Earlier spending is not reassigned. Claude Code requires a project mapping in its settings; an unmapped session remains untagged without a warning. That creates a concrete setup dependency for teams combining browser conversations and terminal work. The reporting unit follows the configured project, so installing the feature and correctly assigning work are separate steps.

Existing controls still decide when work pauses

The Enterprise consumption guide distinguishes organization ceilings, member limits and pooled group budgets. A group default assigns a limit to each member; a pool provides one shared monthly amount. Consider an illustrative team of four people, each with a $100 member limit. Those four limits do not create a shared $100 budget. A separate $100 pool would constrain their combined consumption, subject to the documented enforcement behavior. This example uses invented amounts to explain the mechanics, not an Anthropic price. Project reporting and pooled budgets therefore answer different questions even when the same people use both.

Automation has its own control path

Anthropic's Enterprise Admin API exposes effective member limits alongside spending during the current period. It also supports individual overrides and a separate process for approving or denying requests for more usage. Removing an override returns the member to the inherited limit. Its eight spend-control endpoints share an organization-wide allowance of 60 requests per minute. Monetary values use minor currency units, with fractional amounts possible, and the current recurring period is monthly. The API distinguishes an unlimited allowance from a zero allowance, which disables usage credits for that member. Those values need different treatment in an internal budget tool.