Smart reports analyze how a team uses Claude and report on the work getting done, what it costs, where sessions run into friction, and which repeated patterns are worth packaging as shared skills. This guide explains how smart reports work, what appears in a smart report, and how to create, share, and delete them.
During beta, each organization can run up to 10 reports per month for free, and the limit resets on the first day of every calendar month. If you need more reports during beta, please reach out to your account team or submit a request in the smart report page once you've hit the 10 report limit.
Smart reports are available in beta on Claude Enterprise plans and aren’t available for organizations using customer-managed encryption keys (CMEK), HIPAA configurations, or Access Transparency. Smart reports are also unavailable for Claude Code for Claude Enterprise organizations that use zero data retention.
Important: Smart reports help you understand adoption and plan your investment in Claude. They aren't designed and should not be used for evaluating individual performance or making employment decisions.
How smart reports work
First, a Primary Owner, Owner, Admin, or someone with a custom role with analytics view access chooses what the report covers: a team, a time range of up to the last 28 days, one or more products (chat, Claude Code, or Claude Cowork), the focus areas for the analysis, and any custom questions you’d like Claude to answer while analyzing the transcripts.
Claude then reads a sample of transcripts in that scope, groups them into workstreams and types of outputs, attaches spend to each group, and writes up what it found. Every chart is interactive. Click a workstream to open the sessions inside it, ranked by cost, each with a one-paragraph summary, the product used, the date, and the output type. You can filter by subcategory and download the report as HTML with drilldowns intact.
Each report includes the following sections:
Workstreams: shows what the group used Claude for most, by sessions and by spend, side by side.
Deliverables produced: groups sessions by the type of output that was produced. For example, analysis, documentation, content drafts, and code.
Cost per session by type of output: shows the average spend per session for each kind of output so you can see what's cheap or expensive to produce.
Task outcomes: shows what each session produced.
Most common frictions: shows what got in the way, by category. For example, a connector that wasn’t set up, output that didn’t match the ask, approval or sign-in gating, tool failures, or rework loops.
Inefficiencies: counts sessions that produced nothing usable and sessions that were personal or off-topic, with their cost (shown only as an aggregate count and cost, with no summaries or drilldown).
Reusable skills and workflows to build: identifies repeated patterns that could be packaged as a shared skill so the whole team gets the same result faster. For example, turning call notes into follow-ups, building account briefs, and drafting QBR outlines. Each card includes a suggested prompt you can copy to set up the skill.
Most expensive sessions: lists where spend concentrates.
Complex, autonomous work: shows sessions scoring highest on task complexity, time saved, how long Claude worked on its own, and the expertise required.
Answers to custom questions: before running a smart report, you can select specific pre-built templates to steer the analysis towards those questions, and customize those questions to your specific requirements. If you added custom questions, the answers appear in their own section with the sessions that informed them.
Report analysis excludes personal conversations and conversations that touch restricted topics such as HR, health, and legal matters. Those sessions are set aside before analysis begins, and the report header shows how many were excluded. Admins can delete any report (see Delete smart reports).
Before you begin
You'll need Owner or Primary Owner access to your Enterprise organization to enable smart reports. Once they're enabled, Primary Owners, Owners, Admins, and custom roles with analytics view access can create and view reports.
Enable smart reports for your organization
An Owner or Primary Owner can take the following steps to enable smart reports for their organization:
Navigate to Organization settings > Capabilities.
Find the Analytics section.
Turn on the "Smart reports (beta)" toggle, which is off by default. This makes smart reports available to your organization’s admins with analytics access.
(Optional) Turn on the "Allow attribution to individual users" toggle, which is off by default. This toggle controls whether report viewers can ever see who ran a given session, and each time a viewer reveals names, that action is logged.
If the toggle is off: every drilldown shows "User" in place of a name and hides session IDs.
If the toggle is on: drilldowns still show "User" by default. The person viewing the report gets an in-report control to reveal member names and session IDs. Unveils are logged.
After you've successfully completed these steps, smart reports are enabled for your Enterprise organization.
Scope smart reports to specific teams
Smart reports are more useful when they’re scoped to a functional team rather than the whole organization. For example, you can scope your report to sales, finance, marketing, or engineering. Team-level reports produce clusters specific enough to act on and keep the analysis on spend and adoption: what kinds of tasks, which surfaces and connectors, what it costs.
You can scope by:
Groups: You can filter reports by groups that use role-based permissions. Groups can be created manually in Organization settings > Groups, or you can sync groups from your identity provider (IdP) if you use SCIM directory sync.
Department or cost center: If your identity provider groups don’t map cleanly to functional teams, pass department and cost center from your IdP and filter on those instead. See the Pass department and cost center via SCIM section for setup instructions.
Create a smart report
Once smart reports have been turned on for your organization, Primary Owners, Owners, Admins, and custom roles with analytics view access can create and view reports.
To create a smart report:
Navigate to Analytics > Smart reports (beta).
Click "New report."
Type a name for your report.
Select a specific team or department. Note that this option is only available if you have at least one RBAC group or your organization is in SCIM provisioning and the user payload contains department or cost center fields.
Select a date range.
Select the products to include in your report.
Click "Add files" to add documents to help Claude tailor the report.
Choose who you want to share the report with.
(Optional) Turn on the "Allow attributed view for people you share with" toggle. Note that this option is only available when the org-level "Allow attribution to individual users" toggle is on.
Choose a report template and the questions Claude will answer. You can customize the questions to your specific requirements.
Click "Create report."
Generating a report takes a few hours. You’ll get an email when the report is ready, and reports also appear in the "Smart reports" list in Analytics > Smart reports (beta).
Pass department and cost center via SCIM
If your identity provider groups don’t map to functional teams, you can push the department and cost center as SCIM attributes and filter smart reports on them.
Which value is used
The value you send in the attribute is what appears in the filter. Send a name (for example, "Finance") rather than a code unless you want the code shown.
Attribute paths
Use the SCIM enterprise extension:
Department:
urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:departmentCost center:
urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:costCenter
Example PATCH request
User creation and updates use the same structure as today, with the new attributes added:
{
"schemas": ["urn:ietf:params:scim:api:messages:2.0:PatchOp"],
"Operations": [
{ "op": "replace", "path": "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department", "value": "Finance" },
{ "op": "replace", "path": "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:costCenter", "value": "CC-1234" }
]
}
Most IdPs can map their department and cost center user attributes to these paths in the SCIM app configuration. Once values are flowing, they appear as filter options when you create a new report.
Share smart reports
Smart reports can be shared to individual users in your organization. To share a report:
Click "Share."
Add people to share with.
(Optional) Turn on the "Allow attributed view for people you share with" toggle. Note that this option is only available when the org-level "Allow attribution to individual users" toggle is on.
The report only opens through the sharing link. Only the people it's shared with, and admins who can already view reports, can open that link. You can also pre-share a report while you’re creating it or while it’s still generating, so those people can open the report as soon as it’s ready without the admin having to set up sharing again.
Delete smart reports
To delete a smart report:
Navigate to Analytics > Smart reports (beta).
Click on the three-dot menu for your smart report.
Select "Archive."
Toggle on "Show archived" at the top of the page.
Click on the three-dot menu for your smart report.
Select "Delete."
Click "Delete report."
Use cases
Attach cost to the work. See which kinds of work a team does with Claude and what each costs.
Find the integration you haven't enabled. When the same friction shows up across many sessions, the report names it. The fix is often a connector or setting an admin can turn on in minutes.
Turn repeated work into a shared skill. The report identifies the patterns a team keeps reinventing and gives you a starting prompt to package them.
Share examples. Point the rest of the team to sessions that produced a complete pipeline digest or a batch of account briefs so they can follow the same pattern.
Bring evidence to renewals. Walk into a budget conversation with a per-team view of adoption, cost, and output instead of a blended usage number.