The News, Explained
On November 6, Anthropic announced beta project tags for eligible Claude Enterprise organizations. A project is a workspace for keeping conversations and materials for the same piece of work. By giving a project an existing company cost code, you can group Claude spending under that code. If two teams keep separate projects for the same campaign, for example, giving both projects the same cost code lets you see that spending together. Source Source
An organization owner creates a tag such as “cost code” and manages its allowed values. A project editor picks the value for that project. Each tag takes one value, and a project can have up to 16 tags. You can label a project by department and campaign separately, but a single tag cannot split its spend across two departments. People across the organization can see tag names and values, so an internal identifier makes more sense than a customer’s name. Source
Chat and Cowork inside a project are covered. Cowork is Claude’s tool for work that takes several steps, such as organizing material for a document. Desktop Cowork and the coding tool Claude Code need an assigned project. This requires Claude Desktop 3.6556.1 or later for the desktop app or Claude Code 2.1.305 or later in a terminal. Claude Code on the web and direct API usage do not get project tags. The beta excludes, among others, organizations that store data outside the US or use customer-managed encryption keys or zero data retention. Source
The Spend by project view in organization settings covers activity through the end of the previous day using the UTC time standard. A new tag takes about two hours to take effect. Spending in that window can stay under the old tag or remain untagged, and a later change does not reclassify past spending. Usage already covered by a subscription seat, the access assigned to one user, is left out. The amount shown reflects discounts but comes before credits, so it can differ from the invoice. Source
OYOPICK’s Take
Suppose a team adds a campaign code at 10 a.m. and starts work immediately. Spending before the tag takes effect may be missing from that campaign. For allocating costs across teams, it makes sense to tag the project before work starts and read the new code alongside untagged spend in the next report. The view can help explain how projects use Claude. If you need a total that includes seat-covered usage and work on excluded surfaces, you will also need the invoice and separate usage records. Source