Anthropic gives Claude Enterprise teams shared budgets and AI usage reports
The release combines transcript-based reports, employee surveys and spending controls. Anthropic says the reports are for adoption planning, not employment decisions.
Loading page…
The release combines transcript-based reports, employee surveys and spending controls. Anthropic says the reports are for adoption planning, not employment decisions.
Listen to this story
Anthropic made three Claude Enterprise controls generally available on October 28, 2026: smart reports, employee surveys and shared monthly group budgets. Reports turn sampled conversations into workstreams, costs, deliverables and workflow recommendations, while surveys capture employees’ own accounts of where Claude helps—giving administrators input for adoption planning, not individual performance reviews. Budgets pool funds but retain member-level caps, so usage stops when either the group allowance or a person’s limit is exhausted. Access still depends on organization configuration.
Organization owners can let team leads run reports for their groups; billing admins can raise a member’s spending limit from a report.
Survey questions, recipients, timing and placement are configurable, and responses can be viewed as they arrive or exported to a spreadsheet.
Billing administrators receive email alerts when a pooled budget reaches 50%, 75%, 95% and 100%.
Claude Enterprise administrators can now examine how teams use the AI, ask employees which work benefits most, and manage a shared monthly spending pool. Anthropic made smart reports, in-app surveys and pooled group budgets generally available on October 28, 2026, pairing a closer view of team activity with controls over how usage is funded.
A smart report starts with a team, a date range and a choice of products to include. Claude analyzes a sample of that team’s transcripts, then groups the work into categories called workstreams. The resulting report shows spending, deliverables and common obstacles, such as a missing connection to another service or a failed tool call.
The output goes beyond a spending breakdown. Recommendations can identify recurring workflows to turn into reusable skills, or rules to add to a team’s code repository. A finding can be shared as an artifact inside Claude with the people responsible for acting on it.
Administrators can also ask custom questions about model usage and cost, saving questions and insights as templates for later reports. Organization owners can give non-admin team leads permission to run reports for their own groups. Administrators with billing permission can raise a member’s spending limit directly from a report.
Anthropic places a stated boundary around that visibility: the reports are intended to help organizations understand adoption and plan investment, rather than assess individual employees.
Smart reports help admins understand adoption and inform investment planning, but they aren’t for evaluating individual performance or making employment decisions.
Anthropic, in its Claude Enterprise announcement
The surveys collect employees’ own accounts of the work. Default questions ask about their most valuable recent use of Claude, how it changed the time a task took, and which use a colleague should copy. Another asks what would break or slow down first if the team lost access.
Administrators can edit or remove questions and choose recipients, timing and placement. Employees see a short survey card after a reply in the tool they are already using. Responses appear as they arrive on the survey page and can be exported to a spreadsheet.
Surveys can now be enabled for organizations using customer-managed encryption keys. Where an organization applies one retention period to all data, surveys and responses are deleted on that schedule. Anthropic says it accesses survey data only as necessary to operate the service.
Pooled group budgets give each group one shared monthly allowance. Anthropic positions this as a way to reduce cases where heavy users hit an individual limit while teammates leave money unspent. But pooling does not remove individual controls: every request counts against both the group budget and the member’s limit.
Usage stops when either limit runs out. A member who reaches a limit can request more inside Claude, with the request sent to administrators for review. During setup, Claude suggests a group budget based on recent usage. Billing administrators receive email alerts when spending reaches 50%, 75%, 95% and 100% of the budget.
General availability does not mean every configuration has identical access. Anthropic says eligibility varies, including for organizations configured for HIPAA requirements or customer-managed encryption keys, and directs administrators to its Help Center for setup and eligibility details.
Story updates
Claude Enterprise’s smart reports hide worker names by default, but organizations can allow viewers to reveal them. Sessions Claude identifies as sensitive receive aggregate-only treatment. Anthropic made the reports generally available on October 28, 2026; its help guide, which still uses beta terminology, describes these controls—not a blanket ban on identifying who did the work.
Claude Enterprise’s smart reports hide worker names by default, but organizations can allow viewers to reveal them. Sessions Claude identifies as sensitive receive aggregate-only treatment. Anthropic made the reports generally available on October 28, 2026; its help guide, which still uses beta terminology, describes these controls—not a blanket ban on identifying who did the work.
The help guide describes two steps before names become visible. An owner must enable organization-level attribution, which is off by default. Report drilldowns still display “User” until a viewer chooses to reveal member names and session IDs. Each reveal of names is logged.
That matters because reports offer more than team totals. Interactive charts open into sessions ranked by cost. Ordinary entries include a one-paragraph summary, the product used, date and output type. Sensitive conversations have separate protections that administrators cannot switch off:
Custom questions cannot target restricted topics, including health, union activity, protected characteristics, personal life, harassment or discrimination complaints, and whistleblower reports.
Sessions Claude identifies as involving restricted topics contribute only to aggregate analysis, without session summaries. Personal conversations also omit individual sessions and names.
The guide’s “inefficiencies” section counts sessions producing nothing usable and sessions considered personal or off-topic, with aggregate counts and costs rather than summaries or drilldowns. Those categories do not provide a named view of an employee’s personal conversation.
Smart reports help admins understand adoption and inform investment planning, but they aren’t for evaluating individual performance or making employment decisions.
Managers choose a team, date range and Claude products. Claude analyzes a sample of transcripts, groups work into categories called workstreams, and connects spending with deliverables and recurring problems. Recommendations include workflows worth turning into reusable skills and rules worth adding to a code repository. Findings can be shared as artifacts inside Claude.
Admins can save custom questions about model use and cost as templates. Owners can let non-admin team leads run reports for their own groups, while admins with billing permission can raise a member’s spending limit directly from a report.
The launch announcement says eligibility varies by configuration, including organizations using customer-managed encryption keys or a HIPAA configuration. General availability does not mean every Enterprise deployment can use the feature.
Pricing remains unclear. The beta guide allows 10 free reports per organization each month, then blocks new reports and directs customers to their account team. Mashable describes a fee beyond that allowance. The general-availability announcement specifies neither pricing nor an allowance, so the beta cap should not be treated as confirmed post-launch terms.
Loading discussion...
Join the conversation
Explain what would make that visibility useful or uncomfortable.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.