Claude Enterprise consumption guide (original) (raw)

Claude Enterprise gives your organization access to powerful AI across chat, Claude Code, and Claude Cowork. With that access comes the responsibility of managing consumption effectively—ensuring your team gets maximum value while keeping usage predictable and within budget.

This guide walks Enterprise admins through the key levers available to control and optimize token consumption: setting spend caps, configuring role-based access controls, educating users, and choosing the right model and effort level for the right task.

Why consumption management matters

Claude Enterprise is priced on a per-seat, usage-based model. Your org's consumption pool is shared across all users, and some surfaces—particularly Claude Code and Cowork—consume tokens at a significantly higher rate than standard chat.

Admins who proactively configure spend limits and educate users can reduce waste and ensure that high-value use cases get the capacity they need.

Understanding token intensity across surfaces

Role-based access controls

Role-based access controls (RBAC) let you group users and manage their access to Claude surfaces and consumption budgets as a unit rather than individual by individual. This is the most scalable way to govern usage in larger organizations.

How to structure groups

Think about groups in terms of job function and use case, not organizational hierarchy. A few principles:

Group spend management

Once groups are configured:

Set spend limits

Spend limits are your primary tool for controlling consumption. Claude Enterprise lets admins set limits at three levels: the organization level, the group level (with RBAC), and the individual user level. Our recommended approach is to start with RBAC group-level limits and per-user limits—these give you precise, targeted control without the risk of cutting off your entire org if a limit is hit.

Org-level spend limits

The org-level limit is available as a hard ceiling across all users and surfaces, but use it carefully: hitting it affects everyone simultaneously, which can be disruptive. Most admins find that managing consumption at the group and user level gives them better outcomes with less operational risk.

Group spend limit

Group spend limits let you assign a per-user monthly spend limit to an entire group, so every member of that group inherits the same limit without setting it individually. This is the most scalable way to manage consumption in mid-to-large orgs, and it's where admins should start.

Note the following precedence rules:

How to configure: Organization settings → Usage → By group. Set limits to either a specific dollar amount or "Unlimited."

User-level spend caps

User-level caps let you set consumption limits for individual accounts. These are essential for organizations where usage varies significantly across roles—a developer using Claude Code daily has very different needs than a marketer using chat for copywriting.

Best practices for user-level caps:

Recommended starting points

*These figures are rough planning estimates. Actual consumption will vary based on your team's size, workflows, and usage patterns.

Model selection guidance

One of the most impactful things an admin can do is set clear guidance for users on which model to use for which tasks. Model choice has a direct and significant impact on token consumption—Opus can consume several times more tokens than Sonnet for the same task.

Effort level is a second consumption lever. Users can choose how much thinking Claude applies to each response, and higher effort levels consume more tokens than lower ones. Encourage users to reserve Max effort for more complex work and to use lower effort for routine tasks.

The right model for the right task

Setting your organization's default model (beta)

Beyond guiding users toward the right model, you can set the model that new conversations start with for everyone in your org. This is one of the most direct consumption levers available—the default shapes what the majority of users run day to day.

You have two options:

This setting applies to chat and Cowork only. Claude Code model defaults are managed separately through managed settings.

You can also set model defaults by role through Custom Roles, so different groups can start on different models—for example, defaulting your engineering group to one model and the rest of the org to another. This pairs naturally with the RBAC groups you've already configured (see Section 2).

How to configure: Organization settings → Models.

Admin configuration recommendations

What to tell your users about model choice

Sonnet is your daily driver. It's fast, highly capable, and is designed for the vast majority of tasks—writing, analysis, coding help, and Q&A.

Opus is for the harder, more complex work. Use it when you're working on a genuinely complex multi-step problem, or when quality matters more than speed.

When in doubt, start with Sonnet. You can always switch the model mid conversation to Opus if you need more depth.

Using org preferences to shape user behavior

Org Preferences let admins inject standing guidance into every Claude conversation across your organization—effectively giving Claude a system prompt that reflects your team's norms, best practices, and guardrails. This is a high-leverage tool for shifting user behavior without adding friction, because the guidance shows up in-product at the moment of use rather than in documentation users have to go find.

A few ways you can use Org Preferences to manage consumption and usage patterns:

Tracking usage and spend

Analytics page

The Analytics page within the user menu (claude.ai/analytics) is the fastest way to get a read on your org. It shows weekly active users, seat utilization, top connectors, total spend (MTD/QTD/YTD), spend by model, and a top-10 users-by-spend leaderboard. Product-specific views for Claude.ai, Claude Code, and Cowork break down activity for each surface. Learn more.

Spend report CSV export

If you need a one-off detailed breakdown, you can export a per-user, per-model spend report as a CSV from Analytics → All Activity → Spend → Export Spend. Choose MTD, last month, last 90 days, or a custom range up to 90 days back. The CSV includes user email, user ID, account UUID, product, model, request count, prompt and completion tokens, and net and gross spend in USD.

Analytics chat

Analytics chat lets you ask questions about your org's usage in plain language. Type a question—"show me daily spend for the last 30 days," "who are our top spenders," "what's our seat utilization rate"—and Claude returns a chart and a short written summary of what it found. You can follow up to refine, drill in, or pivot without starting over.

Use this when you have a specific question and don't want to navigate the dashboard, or when you're exploring trends and want fast back-and-forth. Results cover the last 30 days by default; specify a different range in your question if you need it. Data refreshes daily. Learn more.

Analytics API

For programmatic access, use the Claude Enterprise Analytics API. Pull a ranked list of users by tokens used or dollars spent, or look at usage and cost trends over time broken down by product, model, context window, or region. Each request is capped at 31 days wide, starting within the last 365 days, and no earlier than Jan 1, 2026.

Your Primary Owner can generate an admin API key. Data refreshes every four hours; for invoicing-grade totals, query dates 30+ days in the past so late events have time to reconcile. Learn more and review the API reference guide.

End user education

Technology controls will get you most of the way, but user behavior drives the rest. A team that understands how consumption works will make better choices independently—and surface fewer edge cases for you to troubleshoot.

What to communicate to end users

When you onboard users, share the following:

How Claude is billed

How to choose a model

What happens when they hit a cap

Related Articles

How large is the context window on paid Claude plans?Claude Code model configurationRelease notesManage usage credits for paid Claude plansModels, usage, and limits in Claude Code