How to Set Up Claude Enterprise Pooled Budgets, Smart Reports and Surveys (Step by Step)

If you run Claude Enterprise, three new admin tools went live on October 28, 2026: pooled group budgets (one shared monthly budget per team), smart reports (Claude reads a sample of a team’s sessions and shows what the work produced and what it cost), and in-app surveys (a 90-second feedback card inside chat, Cowork or Claude Code). Start with a pooled budget of about 3x the group’s spend last month and a per-member limit of about 3x your top spender’s spend. Then turn on smart reports in Organization settings > Capabilities (they’re off by default) and run one report scoped to a single team. Everything is done in Claude’s settings screens, with no code and no API. This guide walks through each screen, explains which role can see which button, and lists the mistakes that cut a team off mid-month. Every step was checked against Anthropic’s announcement and Claude Help Center articles on October 30, 2026.

Key facts:

  • Status: Anthropic says all three features are “generally available today for Claude Enterprise,” with availability varying for HIPAA and customer-managed-key (CMEK) setups. (Anthropic)
  • Pooled budgets work on usage-based Enterprise plans and on Standard or Premium seat plans with usage credits turned on. They live in Organization settings > Usage. (Help Center)
  • Alerts: everyone with the Billing permission gets an email at 50%, 75%, 95% and 100% of a pooled budget. (Help Center)
  • Smart reports: up to 10 reports per month per organization at no charge, covering up to the last 28 days, and they usually take a few hours to generate. (Help Center)
  • Surveys take users about 90 seconds, each user sees a given survey once, and you can export responses as CSV. (Help Center)

New to Claude’s spending controls? On Pro and Max plans the equivalent problem is a personal usage limit, covered in our guide to what to do when Claude Code says you’ve hit your limit. The 7minai homepage lists our other no-code guides.

Who this guide is for

This is for Claude Enterprise owners, admins and the finance or IT person who handles the Claude bill. You don’t need to write code. Everything below happens in Claude’s web settings. One SCIM attribute example for identity-provider admins appears at the end and is optional.

What each feature fixes:

Problem you have todayFeatureWhere it lives
Heavy users hit their personal cap by mid-month while others leave budget unusedPooled group budgetOrganization settings > Usage
You can’t tell what a team’s Claude spend actually producedSmart reportsAnalytics > Smart reports
You want people to say, in their own words, what Claude helps withIn-app surveysAnalytics > Surveys

Part 1: Pooled group budgets

How a pooled budget differs from a group spend limit

Enterprise already had group spend limits. A group spend limit gives every member of the group the same monthly cap. A pooled budget adds one shared amount that the whole group draws from. (Help Center)

Every request counts against both numbers. A member stops when their own monthly limit runs out, or when every pooled budget they can use is used up, whichever comes first. When the pool runs dry, usage pauses for members who have no other pool until you raise the budget or it resets the next month. Once you raise it, they can send messages again right away. (Help Center)

Seat-plan gotcha: on Standard and Premium seat plans, a pooled budget only covers usage credits. What a seat includes never counts against the pool. When the pool is empty, members can still use what their seat includes but can’t use usage credits. (Help Center)

Who can set it up

Primary Owners, Owners, and custom roles with the Billing permission set to “Can manage”. One limitation: the Billing permission applies to the whole organization, so anyone who can edit one group’s pooled budget can edit every group’s. (Help Center)

Before you start (3 checks)

  1. The group exists in Organization settings > Groups. Groups can be made by hand or synced from your identity provider via SCIM, up to 1,000 per organization. (Help Center: groups)
  2. Usage credits are on (Standard and Premium seat plans only). The spend limits table doesn’t appear until they are.
  3. Pick one team to start with. Anthropic suggests a single team with a clear owner.

Choose your starting numbers: the 3x rule

Anthropic’s guidance is to base the first amounts on last month’s actual spend, not an estimate. You need two numbers:

  • Last month’s spend for the group. In Analytics, filter the members table to the group and add up the spend.
  • The group’s top spender. That’s the first row when you sort the same table by spend.

Then set:

  • Pooled budget ≈ 3x last month’s group spend
  • Member monthly limit ≈ 3x the top spender’s spend

Anthropic’s own example: a group that spent $1,450 last month, with a top spender at $310, gets a pooled budget of $4,350 and a member monthly limit of about $950. The setup screen also suggests both numbers for you. (Help Center)

The most common mistake: don’t set the member limit to “pool ÷ headcount.” Anthropic warns that this brings back one-person limits and removes the point of sharing. The member limit is a guard rail against one unusually heavy user, not a fair-share quota.

Set the pooled budget (6 steps)

  1. Go to Organization settings > Usage.
  2. Scroll to Spend limits and pick the “By group/tier” tab.
  3. Find the group, click the menu button on the right, and choose “Edit limit and budget.”
  4. Under Monthly pooled budget, choose “Set amount.” A suggested amount based on recent usage is filled in, and you can change it.
  5. Under Member monthly limit, click “Use” to accept the suggestion, enter your own number, or choose “No member limit.”
  6. Click “Save.”

If the member limit is too low for the pool, a warning appears with an option to raise it. If the group has no spend limit yet, click the add button on the same tab, pick the group, set the Monthly pooled budget, and click “Add spend limit”. A member limit is optional in that path. (Help Center)

Note that a pooled budget only starts counting spend after it is created, and it resets each month. (Help Center: groups) If you create one on the 20th, the first month’s numbers will look low.

Change, freeze, pause or remove

From the same row menu (“Edit limit and budget”):

You want to…Do this
Change the amountEnter a new amount
Freeze the team’s shared spendingSet the pooled budget to $0
Stop enforcing it but keep the numberChoose “Paused” (choose “Set amount” again to resume)
Delete the poolChoose “No pooled budget”

Watch out: removing the group’s spend limit also removes its pooled budget. (Help Center)

People in more than one group

If someone belongs to several groups that each have a pool, the largest pool pays first by default. Then the next largest with money left pays. To choose the order yourself:

  1. Go to Organization settings > Usage.
  2. In the Pooled budget priority row under Spending defaults, choose “Custom order.” This row only appears once at least two groups have pools.
  3. Use the arrows to put the most specific team first.
  4. Click “Save order.”

This order only decides which pool pays. The separate Member limit from groups setting under Spending defaults decides which group’s per-member cap applies, either “Higher group limit” or “Lower group limit”. An individual spend limit set on a person always beats any group limit. (Help Center: groups) These two settings are easy to confuse, and changing “Member limit from groups” affects everyone in more than one group, not just one team.

Monitor it, and know when to raise it

  • The Pooled budget column on the “By group/tier” tab shows each pool and how much has been used this month. The bar turns amber at 75% and red at 90%. A dash means no pool.
  • At 50/75/95/100%, Billing-permission holders get an email, and a notice appears at the top of Organization settings and the Usage page. Click “View group” to jump to the row.
  • Check Review requests too. When a user hits a limit, they see a “Request more” button in the message box, and the request lands there. Users never see the group’s name or the pool amount.

Anthropic’s own rules of thumb: if a pool is 75% used before the 20th of the month, consider raising it by 50%. If users keep requesting more, raise the member limit. (Help Center)

Not available yet: pooled budgets can only be managed in Organization settings, not through the Admin API. If your finance team automates limits through scripts, this one stays manual for now.

Part 2: Smart reports

What you get

You pick a team, a date range and the products to include. Claude reads a sample of that team’s transcripts, groups them into workstreams, and puts a cost on each group. The report has sections for workstreams, deliverables produced, cost per session by output type, task outcomes, the most common pain points (for example a connector that wasn’t set up, tool failures or rework loops), inefficiencies, the most expensive sessions, and one combined list of recommendations. Those recommendations include recurring workflows worth turning into shared skills. Every chart is clickable, and you can download the report as HTML with the drilldowns kept. (Help Center)

Costs are shown at list price, so they may not match your negotiated invoice.

If the report says a workflow keeps getting reinvented, the fix is usually a shared skill. Our guide on how to write Claude skills explains what a skill file contains.

Limits and who can’t use it

  • 10 reports per month per organization at no charge. Queued and in-progress reports count, failed ones don’t. The count resets on the first day of the next calendar month. For more, contact your account team.
  • Not available with customer-managed encryption keys (CMEK), a HIPAA configuration, or a hybrid deployment that runs inference on your own cloud provider.
  • If you use zero data retention for Claude Code, reports cover chat and Cowork but leave out Claude Code.
  • Anthropic states that smart reports “aren’t designed and should not be used for evaluating individual performance or making employment decisions.” (Help Center)

Step 1: Turn it on (Owner or Primary Owner)

  1. Go to Organization settings > Capabilities.
  2. Find the Analytics section.
  3. Turn on “Smart reports” (off by default).
  4. Optional: turn on “Allow attribution to individual users” (also off by default).

Think about step 4 before you flip it. With it off, every drilldown shows “User” instead of a name and hides session IDs. With it on, names are still hidden by default, but the viewer gets a control to reveal names and session IDs, and every reveal is logged. (Help Center) For a first rollout, most organizations will want to leave it off and talk to HR or the works council first.

Step 2: Create your first report

Primary Owners, Owners, Admins, and custom roles with Analytics view access can do this:

  1. Go to Analytics > Smart reports and click “New report.”
  2. Name it.
  3. Pick a team or department. This option only appears if you have at least one RBAC group, or SCIM sends department or cost-center fields.
  4. Pick a date range (up to the last 28 days).
  5. Pick the products: chat, Claude Code, Claude Cowork, or the unified chat-and-Cowork experience.
  6. Preview how many sessions will be sampled.
  7. Optional: click “Add files” to give Claude background documents.
  8. Choose who to share it with, and whether they get the attributed view (only possible if the org-level attribution toggle is on).
  9. Choose a template, the questions Claude will answer, and any custom insights.
  10. Click “Create report.”

You’ll get an email when it’s ready, usually after a few hours. (Help Center)

Tip: Anthropic recommends scoping to one functional team, such as sales, finance, marketing or engineering, rather than the whole company. The groupings come out specific enough to act on.

Custom insights: ask the same question of every session

Under Your custom insights, click “Add custom insight,” give it a name, describe what Claude should look for in each session, and choose the answer type: Categories, Yes or no, or Scale. Click “Save.” To reuse your questions next month, click “Save as template” under Report template. (Help Center)

Questions that work well for budget decisions:

  • “Did this session end with a finished deliverable?” (Yes or no)
  • “Which connector, if any, was missing?” (Categories)
  • “How complex was the task?” (Scale)

You can’t ask about restricted topics. These include protected characteristics, health, union activity, harassment or whistleblower matters, political or religious views, personal life, and feelings about a named person. Sessions that Claude flags as touching those topics are used only in aggregate, with no summary. Both guardrails are always on.

Let team leads run their own reports (without making them admins)

  1. Go to Analytics > Smart reports > “Manage access.” Only Owners, Primary Owners, or a custom role with both the Analytics and Identity & Access permissions see this button.
  2. Under Add people, pick the person. If they’re greyed out with “Not on Custom roles,” first change their access level in Organization settings > Members, then reopen the screen.
  3. Choose Group, Department or Cost center, then the values. Each change saves immediately. You can assign up to 50 of each kind per person.

The first time you do this, Claude automatically creates a group and a custom role, both named “Smart Reports delegates.” Anthropic recommends not editing those by hand. Delegates are not notified. Tell them to click their name in the lower-left corner and go to Analytics > Smart reports. Delegates never get a whole-organization option. (Help Center)

Sharing and deleting

Click “Share” and add people. The report only opens through its sharing link. To delete one, archive it first from the three-dot menu, turn on “Show archived,” then choose “Delete” and “Delete report.”

Part 3: In-app surveys

What users see

A small card appears in chat, Cowork or Claude Code at a natural break: after a reply in chat, between tasks in Cowork, or after Claude finishes responding in Claude Code. It never interrupts a running task. The card shows your organization’s name and says the answers go to your admins, not to Anthropic. Questions come one at a time, and dismissing the card declines the survey. (Help Center)

Create one in 7 steps

Primary Owners, Owners, Admins, and custom roles with Analytics view access can do this:

  1. Go to Analytics > Surveys and click “New survey.”
  2. Name it (users never see the name).
  3. Set start and end dates. It closes automatically.
  4. Choose the audience: all members, or one or more groups.
  5. Choose where it appears: chat, Cowork, or Claude Code.
  6. Review the questions, adding or removing as needed.
  7. Schedule it, or save it as a draft.

The four default questions ask about the most valuable recent thing someone did with Claude, how Claude changed the time it took (multi-select), one habit a teammate should copy, and what would break first if the team lost access tomorrow.

Results and export

The Surveys table shows each survey as Live, Scheduled or Closed, with response counts and rates. Results update while a survey is live, and you can close it early. The CSV export includes one row per response with the submission time, the user’s email, their group, the surface they answered on, and one column per question. Multi-select answers are separated by semicolons. (Help Center)

Privacy gotcha: the card tells users their answers go to admins, but the export ties every answer to an email address. If you promised staff anonymous feedback, strip that column before sharing the file. Also, surveys aren’t available with a HIPAA configuration, and Anthropic says regulated customers shouldn’t put regulated data such as PHI into responses.

A practical first-month plan

  1. Day 1: Pick one team. Pull last month’s group spend and top spender from Analytics. Set the pool at 3x and the member limit at 3x the top spender.
  2. Day 1: Turn on smart reports, leave attribution off, and run one report on that team for the last 28 days.
  3. Week 1: Launch a survey to the same group in the tool they use most, running for one or two weeks.
  4. Around the 20th: If the pool is past 75%, raise it by 50%. If “Request more” keeps showing up from the same people, raise the member limit instead.
  5. Month end: Compare the report’s top pain points with the survey’s “what would break” answers. Fix the missing connectors, and turn repeated workflows into skills.

That uses 1 of your 10 free monthly reports, so you have room to rerun the report after the fixes.

Troubleshooting

SymptomLikely causeFix
No spend limits table on the Usage pageSeat plan without usage credits turned onTurn on usage credits first
No “Pooled budget priority” rowFewer than two groups have poolsIt appears once a second group has a pool
A whole team suddenly can’t send messagesThe pool reached 100% (or was set to $0)Raise the pool. Members can continue right away
Team lead can’t find smart reportsDelegates aren’t notifiedTheir name (lower left) > Analytics > Smart reports
Person greyed out in Manage accessNot on the Custom roles access levelChange it in Organization settings > Members
Report shows no Claude Code sessionsZero data retention for Claude CodeExpected. The report covers chat and Cowork only
Can’t create a report10 reports used this month (queued ones count)Wait for the 1st or contact your account team
Smart reports missing entirelyCMEK, HIPAA or hybrid deployment, or the toggle is offCheck Organization settings > Capabilities > Analytics
Pool spend looks too lowPools only count spend after creationCompare full months only

Optional appendix: map department and cost center via SCIM

If your identity provider’s groups don’t match real teams, you can scope smart reports by department or cost center instead. Ask whoever manages your identity provider to map these two SCIM enterprise-extension attributes:

  • Department: urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department
  • Cost center: urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:costCenter

Send readable names like “Finance” rather than codes, because the value you send is exactly what appears in the filter. Most identity providers can map these in the SCIM app settings without custom code. (Help Center)

Sources