llms.txt@17-Billing-Plans · git:20261024.48b8a60 · 2026-10-24 · sha256 fc176469c6b04db2
llms.txt@17-Billing-Plans git:20261024.48b8a60F
Immutable. This exact content never changes and is served at /api/v1/blob/fc176469c6b04db2.
# Billing & Plans
> Every page below, concatenated. Each section gives the page title, its upstream source and its path in this repository.
---
## Pricing - Claude Platform Docs
Source: https://platform.claude.com/docs/en/about-claude/pricing
Path: 17-Billing-Plans/about-claude-pricing.md
- [Managed Agents](../04-API-Reference/Other/managed-agents-overview.md)
- [Admin](../04-API-Reference/Other/manage-claude-admin-api.md)
- Resources
- [Best practices](../04-API-Reference/About/about-claude-use-case-guides-overview.md)
- [Models & pricing](../20-Models/about-claude-models-overview.md)
- [SDKs, CLI, and libraries](../04-API-Reference/Other/cli-sdks-libraries-overview.md)
- [Claude API skill](../04-API-Reference/Agents-Tools/agents-and-tools-agent-skills-claude-api-skill.md)
- [Release notes](../20-Models/release-notes-overview.md)
[API reference](../04-API-Reference/Endpoints/overview.md)
[Console](../04-API-Reference/Other/playground.md)[Log in](https://platform.claude.com/login?returnTo=%2Fdocs%2Fen%2Fabout-claude%2Fpricing)
SearchCtrlK
Models
[Models overview](../20-Models/about-claude-models-overview.md)
[Claude Fable 5.1](../20-Models/models-fable-5-1-overview.md)
[Claude Opus 5.5](../20-Models/models-opus-5-5-overview.md)
[Claude Sonnet 5.5](../20-Models/models-sonnet-5-5-overview.md)
[Claude Haiku 5.5](../20-Models/models-haiku-5-5-overview.md)
Specialized models
Legacy models
Guides
[Choosing a model](../20-Models/about-claude-models-choosing-a-model.md)[Optimizing for cost and intelligence](../20-Models/about-claude-models-optimizing-for-cost-and-intelligence.md)[Upgrade between model versions](../20-Models/about-claude-models-migration-guide.md)
Lifecycle and reference
[Model IDs and versioning](../20-Models/about-claude-models-model-ids-and-versions.md)[Model deprecations](../20-Models/about-claude-model-deprecations.md)[Model cards](../04-API-Reference/Other/resources-overview.md)[Pricing](about-claude-pricing.md)[API credits for subscribers](../04-API-Reference/About/about-claude-api-credits-for-subscribers.md)
[System prompts](../20-Models/release-notes-system-prompts-overview.md)
[Console](../04-API-Reference/Other/playground.md)
[Models & pricing](../20-Models/about-claude-models-overview.md)Lifecycle and reference
# Pricing
Copy page
Learn about Anthropic's pricing structure for models and features
Copy page
This page provides detailed pricing information for Anthropic's models and features. All prices are in USD.
For the most current pricing information, visit [claude.com/pricing](pricing.md).
## Model pricing
The following table shows pricing for all Claude models:
[TABLE]
Additional notes
All other models use the standard 0.1x multiplier.
Claude 4.7 and later models and Claude Mythos Preview use a newer tokenizer that contributes to their improved performance on a wide range of tasks. This tokenizer produces approximately 30% more tokens for the same text. The exact increase depends on the content and workload shape. Claude Sonnet 4.6 and earlier models use the previous tokenizer.
## Cloud platform pricing
This section covers partner-operated cloud platforms, where the cloud provider invoices you. For Anthropic-operated cloud platforms billed through a marketplace, see [Claude Platform on AWS pricing](#claude-platform-on-aws-pricing) and [Claude in Microsoft Foundry pricing](#claude-in-microsoft-foundry-pricing).
Claude models are available on [Amazon Bedrock](../04-API-Reference/Guides/build-with-claude-claude-in-amazon-bedrock.md) and [Google Cloud](../04-API-Reference/Guides/build-with-claude-claude-on-vertex-ai.md). For official pricing, visit:
- [Amazon Bedrock pricing](https://aws.amazon.com/bedrock/pricing/)
- [Google Cloud pricing](https://cloud.google.com/vertex-ai/generative-ai/pricing#claude-models)
**Regional and multi-region endpoint pricing for Claude 4.5 models and beyond**
Starting with Claude Sonnet 4.5, Haiku 4.5, and Opus 4.5:
- **Bedrock** offers two endpoint types: global endpoints (dynamic routing for maximum availability) and regional endpoints (guaranteed data routing through specific geographic regions).
- **Google Cloud** offers global endpoints and multi-region endpoints (dynamic routing within a geographic area) for these models, and regional endpoints for Claude Sonnet 4.6 and earlier models.
Regional and multi-region endpoints include a 10% premium over global endpoints. The Claude API (first-party) is global by default; for first-party data residency options and pricing, see [Data residency pricing](#data-residency-pricing).
**Scope:** This pricing structure applies to Claude Sonnet 4.5 (deprecated), Haiku 4.5, Opus 4.5, and all future models. Earlier models (Claude Opus 4.1 and prior releases) retain their existing pricing.
For implementation details and code examples:
- [Amazon Bedrock global vs regional endpoints](../04-API-Reference/Guides/build-with-claude-claude-in-amazon-bedrock.md#regions) for Opus 4.7, Haiku 4.5, and later models, or [the legacy integration](../04-API-Reference/Guides/build-with-claude-claude-on-amazon-bedrock-legacy.md#global-vs-regional-endpoints) for all other models on Bedrock
- [Google Cloud global, multi-region, and regional endpoints](../04-API-Reference/Guides/build-with-claude-claude-on-vertex-ai.md#global-multi-region-and-regional-endpoints)
## Claude Platform on AWS pricing
[Claude Platform on AWS](../04-API-Reference/Guides/build-with-claude-claude-platform-on-aws.md) bills through AWS Marketplace using Claude Consumption Units (CCUs). Anthropic rates your token usage in USD at standard per-model, per-feature rates, applies any negotiated discount, converts the result to CCUs at \$0.01 per CCU, and reports the CCU quantity to AWS Marketplace hourly. Your AWS bill shows a single CCU line item.
[TABLE]
### Inference geography
For Claude 4.6 and later models, using `inference_geo: "us"` applies a 1.1x pricing multiplier. `inference_geo: "global"` (default) uses standard pricing. See [Data residency](../04-API-Reference/Other/manage-claude-data-residency.md) for details.
### Private offers
When you sign up on the AWS Console **Claude Platform on AWS** service page, the AWS Console looks up any private offer associated with your account and prompts you to accept it in AWS Marketplace. Contact your Anthropic account representative for private offer terms.
If you have an existing Amazon Bedrock private offer, contact your Anthropic or AWS account representative before getting started with Claude Platform on AWS to ensure your discounts are applied correctly. Discounts cannot be applied retroactively to usage incurred before your private offer is accepted.
## Claude in Microsoft Foundry pricing
[Claude in Microsoft Foundry](../04-API-Reference/Guides/build-with-claude-claude-in-microsoft-foundry.md) bills through the Azure Marketplace using Claude Consumption Units (CCUs). Anthropic rates your token usage in USD at standard per-model, per-feature rates, applies any negotiated discount, converts the result to CCUs at \$0.01 per CCU, and reports the CCU quantity to the Azure Marketplace hourly. Your Azure bill shows a single CCU line item.
[TABLE]
### Inference geography
Deployments hosted on Azure can use the US Data Zone Standard deployment type, which keeps inference within the United States. This is equivalent to `inference_geo: "us"` on the Claude API and applies the same 1.1x pricing multiplier. See [Data residency](../04-API-Reference/Other/manage-claude-data-residency.md) for details.
## Feature-specific pricing
### Prompt caching
Prompt caching reduces costs and latency by reusing previously processed portions of your prompt across API calls. Instead of reprocessing the same large system prompt, document, or conversation history on every request, the API reads from cache at a fraction of the standard input price.
There are two ways to enable prompt caching:
- **Automatic caching:** Add a single `cache_control` field at the top level of your request. The system automatically manages cache breakpoints as conversations grow. This is the recommended starting point for most use cases.
- **Explicit cache breakpoints:** Place `cache_control` directly on individual content blocks for fine-grained control over exactly what gets cached.
Prompt caching uses the following pricing multipliers relative to base input token rates:
| Cache operation | Multiplier | Duration |
|:---------------------|:-------------------------------------------------------------------------------------------------------------------------|:-------------------------------------|
| 5-minute cache write | 1.25x base input price | Cache valid for 5 minutes |
| 1-hour cache write | 2x base input price | Cache valid for 1 hour |
| Cache read (hit) | 0.1x base input price (0.025x on Claude Fable 5.1 and Claude Mythos 5.1; 0.05x on Claude Opus 5.5 and Claude Sonnet 5.5) | Same duration as the preceding write |
Cache write tokens are charged when content is first stored. Cache read tokens are charged when a subsequent request retrieves the cached content. A cache hit costs 10% of the standard input price, which means caching pays off after one cache read for the 5-minute duration (1.25x write), or after two cache reads for the 1-hour duration (2x write). On Claude Fable 5.1 and Claude Mythos 5.1, a cache hit costs 2.5% of the standard input price (\$0.25 USD per million tokens). On Claude Opus 5.5 and Claude Sonnet 5.5, a cache hit costs 5% of the standard input price (\$0.20 USD per million tokens on Claude Opus 5.5, \$0.10 USD on Claude Sonnet 5.5).
These multipliers stack with other pricing modifiers, including the Batch API discount and data residency.
For implementation details, supported models, and code examples, see [Prompt caching](../04-API-Reference/Guides/build-with-claude-prompt-caching.md).
### Data residency pricing
For Claude 4.6 and later models, specifying US-only inference through the `inference_geo` parameter incurs a 1.1x multiplier on all token pricing categories, including input tokens, output tokens, cache writes, and cache reads. On Claude Haiku 5.5, the multiplier also applies to the higher prices for prompts over 100,000 tokens (see [Long context pricing](#long-context-pricing)). Global routing (the default) uses standard pricing.
This applies to the Claude API (first-party) and Claude Platform on AWS. On Claude in Microsoft Foundry, the same 1.1x multiplier applies to deployments that use the US Data Zone Standard deployment type (see [Inference geography](#foundry-inference-geography)). Partner-operated platforms (Bedrock and Google Cloud) have independent regional pricing. See [Bedrock](https://aws.amazon.com/bedrock/pricing/) and [Google Cloud](https://cloud.google.com/vertex-ai/generative-ai/pricing#claude-models) for details. Earlier models do not support the `inference_geo` parameter and always use standard pricing; requests that include the parameter on these models return a 400 error.
For more information, see [Data residency](../04-API-Reference/Other/manage-claude-data-residency.md).
### Fast mode pricing
[Fast mode](../04-API-Reference/Guides/build-with-claude-fast-mode.md) provides significantly faster output for Claude Opus 5.5, Claude Opus 5, and Claude Opus 4.8 at premium pricing. Fast mode for Claude Opus 5 and Claude Opus 4.8 is in research preview. Fast mode pricing applies across the full context window, including requests over 200k input tokens. Fast mode is available on the Claude API (first-party) and, for Claude Opus 5.5, on [Claude in Microsoft Foundry](../04-API-Reference/Guides/build-with-claude-claude-in-microsoft-foundry.md) for deployments hosted on Azure; it is not available on Claude Platform on AWS or partner-operated cloud platforms.
| Model | Input | Output |
|:--------------------------------|:----------------|:----------------|
| Claude Opus 5.5 | \$8 USD / MTok | \$40 USD / MTok |
| Claude Opus 5 / Claude Opus 4.8 | \$10 USD / MTok | \$50 USD / MTok |
Fast mode pricing stacks with other pricing modifiers:
- [Prompt caching multipliers](#prompt-caching) apply on top of fast mode pricing
- [Data residency](../04-API-Reference/Other/manage-claude-data-residency.md) multipliers apply on top of fast mode pricing
Fast mode is not available with the [Batch API](#batch-processing).
For more information, see [Fast mode](../04-API-Reference/Guides/build-with-claude-fast-mode.md).
### Batch processing
The Batch API allows asynchronous processing of large volumes of requests with a 50% discount on both input and output tokens.
[TABLE]
For more information about batch processing, see [Batch processing](../04-API-Reference/Guides/build-with-claude-batch-processing.md).
### Long context pricing
Claude 4.6 and later models (except Claude Haiku 5.5) and [Claude Mythos Preview](../22-Safety-Policy/glasswing.md) include the full [1M token context window](../04-API-Reference/Guides/build-with-claude-context-windows.md) at standard pricing. (A 900k-token request is billed at the same per-token rate as a 9k-token request.) Prompt caching and batch processing discounts apply at standard rates across the full context window.
Claude Haiku 5.5 is priced by prompt length: a request whose prompt is over 100,000 tokens pays higher prices. A request's prompt length counts all of its input tokens, including cache reads and cache writes. Each request is priced on its own: a request over the threshold pays the higher prices even when part of its prompt is a cache hit, and earlier requests keep the prices they were billed at. [Model pricing](#model-pricing) and [Batch processing](#batch-processing) list both sets of prices.
### Tool use pricing
Tool use requests are priced based on:
1. The total number of input tokens sent to the model (including in the `tools` parameter)
2. The number of output tokens generated
3. For server-side tools, additional usage-based pricing (for example, web search charges per search performed)
Client-side tools are priced the same as any other Claude API request, although server-side tools can incur additional charges based on their specific usage.
The additional tokens from tool use come from:
- The `tools` parameter in API requests (tool names, descriptions, and schemas)
- `tool_use` content blocks in API requests and responses
- `tool_result` content blocks in API requests
When you use `tools`, the API also automatically includes a special system prompt for the model that enables tool use. The number of tool use tokens required for each model is listed in the following table (excluding the additional tokens listed earlier). Note that the table assumes at least 1 tool is provided. If no `tools` are provided, then a tool choice of `none` uses 0 additional system prompt tokens.
[TABLE]
These token counts are added to your normal input and output tokens to calculate the total cost of a request.
For current per-model prices, refer to the [model pricing](#model-pricing) section.
For more information about tool use implementation and best practices, see [Tool use](../04-API-Reference/Agents-Tools/agents-and-tools-tool-use-overview.md).
### Specific tool pricing
#### Bash tool
The bash tool definition adds the following input tokens to your request. This is in addition to the per-model [tool use system prompt](../04-API-Reference/Agents-Tools/agents-and-tools-tool-use-overview.md#pricing) that applies whenever any tool is present.
| Model | Additional input tokens |
|-------------------------------------------------------|-------------------------|
| Claude 4.7 and later models and Claude Mythos Preview | 325 tokens |
| Claude 4.6 and earlier models | 244 tokens |
Additional tokens are consumed by:
- Command outputs (stdout/stderr)
- Error messages
- Large file contents
See [tool use pricing](#tool-use-pricing) for complete pricing details.
#### Code execution tool
**Code execution is free when used with web search or web fetch.** When `web_search_20260209` (or later) or `web_fetch_20260209` (or later) is included in your API request, there are no additional charges for code execution tool calls beyond the standard input and output token costs.
When used without these tools, code execution is billed by execution time, tracked separately from token usage:
- Execution time has a minimum of 5 minutes
- Each organization receives **1,550 free hours** of usage per month
- Additional usage beyond 1,550 hours is billed at **\$0.05 USD per hour, per container**
- If files are included in the request, execution time is billed even if the tool is not called, because files are preloaded onto the container
Code execution usage is tracked in the response:
```python
{
"usage": {
"input_tokens": 105,
"output_tokens": 239,
"server_tool_use": {
"code_execution_requests": 1
}
}
}
```
#### Text editor tool
The text editor tool uses the same pricing structure as other tools used with Claude. It follows the standard input and output token pricing based on the Claude model you're using.
In addition to the base tokens, the following additional input tokens are needed for the text editor tool:
| Tool | Additional input tokens |
|--------------------------------------------------------------------------------|-------------------------|
| `text_editor_20250728` (Claude 4.7 and later models and Claude Mythos Preview) | 974 tokens |
| `text_editor_20250728` (Claude 4.6 and earlier models) | 745 tokens |
See [tool use pricing](#tool-use-pricing) for complete pricing details.
#### Web search tool
Web search usage is charged in addition to token usage:
```python
{
"usage": {
"input_tokens": 105,
"output_tokens": 6039,
"cache_read_input_tokens": 7123,
"cache_creation_input_tokens": 7345,
"server_tool_use": {
"web_search_requests": 1
}
}
}
```
Web search is available on the Claude API for **\$10 per 1,000 searches**, plus standard token costs for search-generated content. Web search results retrieved throughout a conversation are counted as input tokens, in search iterations executed during a single turn and in subsequent conversation turns.
Each web search counts as one use, regardless of the number of results returned. If an error occurs during web search, the web search will not be billed.
#### Web fetch tool
Web fetch usage has **no additional charges** beyond standard token costs:
```python
{
"usage": {
"input_tokens": 25039,
"output_tokens": 931,
"cache_read_input_tokens": 0,
"cache_creation_input_tokens": 0,
"server_tool_use": {
"web_fetch_requests": 1
}
}
}
```
The web fetch tool is available on the Claude API at **no additional cost**. You only pay standard token costs for the fetched content that becomes part of your conversation context.
To protect against inadvertently fetching large content that would consume excessive tokens, use the `max_content_tokens` parameter to set appropriate limits based on your use case and budget considerations.
Example token usage for typical content:
- Average web page (10 kB): ~2,500 tokens
- Large documentation page (100 kB): ~25,000 tokens
- Research paper PDF (500 kB): ~125,000 tokens
#### Computer use tool
Computer use follows the standard [tool use pricing](../04-API-Reference/Agents-Tools/agents-and-tools-tool-use-overview.md#pricing). When using the computer use tool:
**Toolset definition overhead:** Declaring `computer_toolset_20260801` with its default members adds about 4,500 input tokens to a request (about 4,590 on Claude Sonnet 5 and about 4,520 on the other supported models), which covers the member tool definitions and the tool use system prompt. Disabling `zoom` with `configs` removes about 410 of those tokens. The exact count for a request is reported in the response `usage`, and you can estimate it in advance with the [token counting endpoint](../04-API-Reference/Guides/build-with-claude-token-counting.md).
**Earlier tool versions:** The following figures apply to the `computer_20251124` and `computer_20250124` tool versions, not to `computer_toolset_20260801`:
- System prompt overhead: 466–499 tokens added to the system prompt
- Tool definition: about 735 input tokens per tool definition (measured with `computer_20250124`)
**Additional token consumption:**
- Screenshot and zoom images returned in tool results, billed as image input (see [Vision pricing](../04-API-Reference/Guides/build-with-claude-vision.md#evaluate-image-size))
- Tool execution results returned to Claude
If you're also using bash or text editor tools alongside computer use, those tools have their own token costs as documented in their respective pages.
#### Browser use tool
Browser use follows the standard [tool use pricing](../04-API-Reference/Agents-Tools/agents-and-tools-tool-use-overview.md#pricing). When using the browser use tool:
**Toolset definition overhead:** Declaring `browser_toolset_20260801` with its default members adds about 6,600 input tokens to a request (about 6,670 on Claude Sonnet 5 and about 6,610 on the other supported models), which covers the member tool definitions and the tool use system prompt. Enabling all four optional members adds about 880 tokens, and disabling members with `configs` reduces the count. The exact count for a request is reported in the response `usage`, and you can estimate it in advance with the [token counting endpoint](../04-API-Reference/Guides/build-with-claude-token-counting.md).
**Additional token consumption:**
- Screenshot and zoom images returned in tool results, billed as image input (see [Vision pricing](../04-API-Reference/Guides/build-with-claude-vision.md#evaluate-image-size))
- Text tool results returned to Claude, such as accessibility trees, page text, and console or network entries
If you also use the computer use tool, bash tool, text editor tool, or your own tools alongside browser use, those tools have their own token costs as documented on their respective pages.
## Claude Managed Agents pricing
[Claude Managed Agents](../04-API-Reference/Other/managed-agents-overview.md) is billed on two dimensions: tokens and session runtime.
### Tokens
All tokens consumed by a Claude Managed Agents session are billed at the rates shown in [Model pricing](#model-pricing). [Prompt caching](#prompt-caching) multipliers apply identically. Web search triggered inside a session incurs the standard \$10 per 1,000 searches. On [Claude Platform on AWS](#claude-platform-on-aws-pricing), session token and runtime charges convert to Claude Consumption Units at the standard rate. [Fast mode](#fast-mode-pricing) premium pricing applies when an agent's `model.speed` is set to `"fast"`.
The [data residency multiplier](#data-residency-pricing) also applies: when an agent's `model.inference_geo` is pinned to `"us"`, tokens consumed by sessions running that agent are billed at 1.1x the standard rates, the same multiplier that applies to US-only inference on the Messages API.
The following Messages API modifiers do **not** apply to Claude Managed Agents sessions:
| Modifier | Why it doesn't apply |
|---------------------------------------------------|----------------------------------------------------------------|
| [Batch API discount](#batch-processing) | Sessions are stateful and interactive. There is no batch mode. |
| [Cloud platform pricing](#cloud-platform-pricing) | Not available on partner-operated cloud platforms. |
### Session runtime
| SKU | Rate | Metering |
|-----------------|-------------------------|---------------------------|
| Session runtime | \$0.08 per session-hour | `running` status duration |
Runtime is measured to the millisecond and accrues only while the session's status is `running`. Time spent `idle` (waiting for your next message or a tool confirmation), `rescheduling`, or `terminated` does not count toward runtime.
Session runtime replaces the [code execution](#code-execution-tool) container-hour billing model when using Claude Managed Agents. You are not separately billed for container hours on top of session runtime.
### Worked example
A one-hour coding session using Claude Opus 5.5 that consumes 50,000 input tokens and 15,000 output tokens:
| Line item | Calculation | Cost |
|-----------------|---------------------------|------------|
| Input tokens | 50,000 × \$4 / 1,000,000 | \$0.20 |
| Output tokens | 15,000 × \$20 / 1,000,000 | \$0.30 |
| Session runtime | 1.0 hour × \$0.08 | \$0.08 |
| **Total** | | **\$0.58** |
If prompt caching is active and 40,000 of the input tokens are cache reads:
| Line item | Calculation | Cost |
|-----------------------|---------------------------------|-------------|
| Uncached input tokens | 10,000 × \$4 / 1,000,000 | \$0.04 |
| Cache read tokens | 40,000 × \$4 × 0.05 / 1,000,000 | \$0.008 |
| Output tokens | 15,000 × \$20 / 1,000,000 | \$0.30 |
| Session runtime | 1.0 hour × \$0.08 | \$0.08 |
| **Total** | | **\$0.428** |
## Additional pricing considerations
### Cost optimization strategies
When building agents with Claude:
1. **Use appropriate models:** Choose Haiku for simple tasks, Sonnet for most production workloads, and Opus for the most complex reasoning
2. **Implement prompt caching:** Reduce costs for repeated context
3. **Batch operations:** Use the Batch API for non-time-sensitive tasks
4. **Monitor usage patterns:** Track token consumption to identify optimization opportunities
For high-volume agent applications, contact the [enterprise sales team](https://claude.com/contact-sales) for custom pricing arrangements.
### Rate limits
Rate limits vary by usage tier and affect how many requests you can make:
- **Start tier:** Entry-level limits for getting started
- **Build tier:** Increased limits for growing applications
- **Scale tier:** Highest standard limits for production workloads
For detailed rate limit information, see [Rate limits](../04-API-Reference/Endpoints/rate-limits.md).
For limits beyond the Scale tier or custom pricing arrangements, [contact the sales team](https://claude.com/contact-sales).
### Volume discounts
Volume discounts may be available for high-volume users. These are negotiated on a case-by-case basis.
- Standard usage tiers use the pricing shown in [Model pricing](#model-pricing)
- Enterprise customers can [contact sales](mailto:sales@anthropic.com) for custom pricing
- Academic and research discounts may be available
### Enterprise pricing
For enterprise customers with specific needs:
- Custom rate limits
- Volume discounts
- Dedicated support
- Custom terms
Contact the sales team at <sales@anthropic.com> or through the [Claude Console](../04-API-Reference/Other/playground.md) to discuss enterprise pricing options.
## Billing and payment
- Billing is based on actual monthly usage
- All payments are in USD
- Credit card and invoicing options available
- Usage tracking available in the [Claude Console](../04-API-Reference/Other/playground.md)
## Frequently asked questions
### How is token usage calculated?
Tokens are pieces of text that models process. How many tokens the same text produces depends on the model's tokenizer, the language, and the type of content. Claude 4.7 and later models and Claude Mythos Preview use a newer tokenizer that produces approximately 30 percent more tokens for the same text than earlier models. To see how many tokens a request uses on a specific model, count it with [token counting](../04-API-Reference/Guides/build-with-claude-token-counting.md) and that model's ID.
### Are there free tiers or trials?
New users receive a small amount of free credits to test the API. [Contact sales](mailto:sales@anthropic.com) for information about extended trials for enterprise evaluation.
### How do discounts stack?
Batch API and prompt caching discounts can be combined. For example, using both features together provides significant cost savings compared to standard API calls. See [prompt caching pricing](#prompt-caching) for how the multipliers interact.
### What payment methods are accepted?
Major credit cards are accepted for standard accounts. To buy credits or manage your payment methods, go to the [Billing](../04-API-Reference/Other/playground.md) page (`platform.claude.com/settings/billing`) in the Claude Console. Enterprise customers can arrange invoicing and other payment methods.
For additional questions about pricing, contact <support@anthropic.com>.
---
## Claude Help Center
Source: https://support.claude.com/en/articles/11014257-about-claude-s-max-plan-usage
Path: 17-Billing-Plans/about-claude-s-max-plan-usage.md
# Search for answers or browse by topic
Search for articles...
Uh oh. That page doesn’t exist.
Try searching for your answer or just send us a message.
---
## Add or update your Claude Console organization's tax or VAT ID | Claude Help Center
Source: https://support.claude.com/en/articles/9889428-add-or-update-your-claude-console-organization-s-tax-or-vat-id
Path: 17-Billing-Plans/add-or-update-your-claude-console-organization-s-tax-or-vat-id.md
# Add or update your Claude Console organization's tax or VAT ID
## Add your tax or VAT ID during sign-up
When create a Claude Console organization, you may have the option to enter your tax or VAT ID depending on your location:
1. During the signup process, enter your address information.
2. If your address is eligible for tax purposes, an optional field for your tax or VAT ID will appear.
3. Enter your tax or VAT ID in the provided field.
4. If the ID is entered correctly, you'll be able to proceed with your signup.
## Update your tax or VAT ID after sign-up
If you need to add or update your tax or VAT ID after you've already created a Claude Console organization, follow these steps:
1. Log in to your API Console account.
2. Go to the **Organization** page (platform.claude.com/settings/organization).
3. Enter or modify your tax or VAT ID as needed.
4. Click "Save changes" when you're finished.
**Note:** Your billing address determines your tax jurisdiction. For details on how to view or update your billing address, see **[Understanding your billing address and tax calculation](understanding-your-billing-address-and-tax-calculation.md)**.
---
## Artifacts admin guide for Team and Enterprise plans | Claude Help Center
Source: https://support.claude.com/en/articles/16994751-artifacts-admin-guide-for-team-and-enterprise-plans
Path: 17-Billing-Plans/artifacts-admin-guide-for-team-and-enterprise-plans.md
# Artifacts admin guide for Team and Enterprise plans
Updated today
This guide is for Owners and Primary Owners of Team and Enterprise plans, and explains how to turn on artifacts for your organization, choose which templates users can start from, control who has access, and manage whether or not artifacts can be shared outside your organization.
## Turn on artifacts for your organization
To change organization settings, you need to be an Owner or Primary Owner, or in a custom role (Enterprise plans) with the appropriate admin permissions.
1. Turn on “Cloud code execution and file creation” in Organization settings \> Capabilities first.
2. Navigate to **[Organization settings \> Artifacts](https://claude.ai/admin-settings/artifacts)**.
3. Turn on **Artifacts**.
This lets users create and publish artifacts to a shareable Anthropic-hosted page, and share artifacts within your organization.
**Important:** Turning **Artifacts** off stops users from sharing artifacts with your organization. Links they already shared keep working.
## Choose which templates users can start from
Templates are the starting points users pick when they create an artifact.
[TABLE]
**To enable a template:**
1. Navigate to **[Organization settings \> Artifacts](https://claude.ai/admin-settings/artifacts)**.
2. Under **Templates**, turn on the templates you want to make available.
**Note:** Turning a template off doesn't impact artifacts users already made using that template.
**Defaults:**
- **Docs, Slides, and Design:** On by default on Team plans. On Enterprise plans, they turn on by default on October 15, 2026. Turn any of them off before then if you don't want them on.
- **Motion:** On by default on Team plans, and off by default on Enterprise plans.
- **Dashboards:** Available on paid plans. Off by default on Enterprise plans.
### Standalone Claude Design at claude.ai/design
Standalone Claude Design at **claude.ai/design** closes on December 14, 2026. Until then, it has its own setting in **[Organization settings \> Claude Design](https://claude.ai/admin-settings/claude-design)**, separate from the **Design** template. Users' existing projects stay at **claude.ai/design** until it closes, and up to 60 of them also appear in the **Artifacts** tab.
Moving projects to Claude is rolling out gradually to paid plans, and a project or design system that moves to Claude becomes an artifact. To let users move their projects and move their design systems, keep **Artifacts** and **Design systems** on for your organization. On Enterprise plans with custom roles, each user's role needs them too. Learn more in **[Move from standalone Claude Design to Claude](../15-Claude-AI-Features/migrate-from-standalone-claude-design-to-claude-claude-help-center.md)**.
------------------------------------------------------------------------
## Manage sharing outside your organization
Two separate settings control what users can share outside your organization. Turning on one doesn't turn on the other. For what users see and which artifacts can't leave your organization, see **[Share artifacts](https://support.claude.com/en/articles/9547008-publish-and-share-artifacts)**.
### External sharing
**External sharing** lets users share artifacts with anyone who has the link.
1. Navigate to **[Organization settings \> Artifacts](https://claude.ai/admin-settings/artifacts)**.
2. Turn on **External sharing**.
**Important:** Turning **External sharing** off also stops existing public links from working until you turn it back on, except for artifacts you allow individually.
### Allow external sharing for a single artifact
While **External sharing** is off, you can still let a specific artifact be shared with anyone who has the link.
1. Navigate to **[Organization settings \> Artifacts](https://claude.ai/admin-settings/artifacts)**.
2. Under **Published artifacts**, find the artifact. It must already be shared with your organization or invited people to appear here.
3. Open the artifact's menu and select "Allow external sharing."
4. Confirm by selecting "Allow external sharing."
The artifact's owner can then share it with anyone who has the link. **External sharing** stays off for every other artifact in your organization.
### Email invitations outside your organization
**Email invitations outside your organization** lets users invite specific people outside your organization to an artifact by email. It's a separate setting from **External sharing**, so turning on one doesn't turn on the other.
1. Navigate to **[Organization settings \> Artifacts](https://claude.ai/admin-settings/artifacts)**.
2. Turn on **Email invitations outside your organization**.
**Important:** Turning **Email invitations outside your organization** off blocks access for people users already invited, until you turn it back on. Accepted invitations aren't deleted, and pending ones still expire 30 days after they were sent.
### See and remove outside access
1. Navigate to **[Organization settings \> Artifacts](https://claude.ai/admin-settings/artifacts)**.
2. Under **Published artifacts**, find an artifact marked **Shared outside**.
3. Open the artifact's menu and select "Manage outside access."
4. Select the remove button next to the person, then confirm with "Remove access" or "Remove invitation."
Owners can remove people here but can't change their access level.
### What stays inside your organization
Some artifacts can't leave your organization even with these settings on:
- Docs can't be shared outside your organization yet.
- Artifacts that use connected apps, or that ask Claude questions, can't use “Anyone with the link.”
People need a Claude account to open any artifact except a legacy artifact published from chat.
Learn more about **[sharing artifacts](https://support.claude.com/en/articles/9547008)**.
------------------------------------------------------------------------
## Let users see who else has an artifact open
**Artifact presence** lets users see who else in your organization has an artifact open, along with live activity in it. Turn it on or off in **[Organization settings \> Artifacts](https://claude.ai/admin-settings/artifacts)**.
It's on by default on Team and Enterprise plans, and it only applies while **Artifacts** is on for your organization.
**Note:** Turning **Artifact presence** off applies to new page loads right away, and to tabs that are already open within an hour.
------------------------------------------------------------------------
## Let artifacts use connected apps
**Enable artifact connectors** lets users work with artifacts that read from and write to their connected apps. Each user connects their own apps, even in a shared artifact. You can turn this on or off for your whole organization, but you can't limit which apps artifacts can reach.
1. Navigate to **[Organization settings \> Capabilities](https://claude.ai/admin-settings/capabilities)**.
2. Under **Visuals**, turn on **Enable artifact connectors**.
------------------------------------------------------------------------
## Limit access to specific groups on Enterprise plans
On Enterprise plans, custom roles let you turn a feature on for specific groups instead of your whole organization. The organization setting is the main switch, and custom roles are the per-user switches underneath it. If a feature is off at the organization level, no custom role can grant access to it.
The capabilities that cover artifacts are:
[TABLE]
Users without the **Artifacts** capability can still open artifacts shared with them, comment on them, and change their data, at the sharing level they were given, up to Contributor. Contributor lets someone use an artifact, save what they enter in it, and comment, without editing the artifact itself. A user without the capability who was shared as an Editor gets Contributor access at most. They can't create, edit, publish, or share artifacts.
Learn more about **[managing custom roles on Enterprise plans](https://support.claude.com/en/articles/13930452)** and **[setting up role-based permissions on Enterprise plans](https://support.claude.com/en/articles/13930458)**.
------------------------------------------------------------------------
## Manage your organization's design systems
Design systems shared with everyone in your organization are listed in **[Organization settings \> Artifacts](https://claude.ai/admin-settings/artifacts)**, under **Design systems**, with their owner and when they were last updated. Users see these when they start a new artifact, and the default is preselected.
### Restrict who can manage design systems
In Artifacts, any user with access to design systems can create one, share it with specific people, and delete their own, and the owner of a design system can delete it. Only an Owner or Primary Owner can share a design system with everyone in your organization, set the organization default, or delete a design system that’s shared with everyone.
To share someone else’s design system with everyone, an Owner or Primary Owner first needs its creator to invite them in the Share dialog at the highest access level. A design system must be shared with everyone before it can be set as the organization default.
On Enterprise plans, custom roles control who can create design systems. Turn **Design systems** on or off under **Artifacts** in a role’s **Capabilities** tab.
Design systems moved from standalone Claude Design can arrive already shared with everyone. Published design systems that weren’t private there are shared with everyone in your organization, and if your organization’s default design system moves, it becomes the default in Artifacts too, unless you’ve already set one.
**In standalone Claude Design**
The **Claude Design Admin** permission applies only to the standalone Claude Design app. It doesn’t let anyone share, set as default, or delete a design system created in artifacts. In standalone Claude Design, Enterprise plans can reserve the following for users in custom roles with the permission set to “Can manage”
- **Publish a design system:** make it available across your organization so anyone can attach it to a project.
- **Set the organization default:** choose the design system new projects use automatically.
- **Delete a design system:** permanently remove it from your organization.
Everyone else can still create, edit, and use any published design system. If a user without the permission tries to publish, set the default, or delete, they'll see a note directing them to contact their administrator.
**To grant the permission:**
1. Navigate to **[Organization settings \> Roles](https://claude.ai/admin-settings/roles)** and create or edit a custom role.
2. In the “Admin permissions” tab, find **Claude Design Admin** under **Product admin** and set it to “Can manage.”
3. Assign the role to a group. Users in that group inherit the permission.
4. Set each user's role to “Custom.”
Learn more about **[setting up your design system](../21-Account-Support/set-up-your-design-system-in-claude-design-claude-help-center.md)**.
------------------------------------------------------------------------
## Usage and billing
Artifacts, including designs, decks, and docs, count toward each user's existing usage limits, shared with the rest of Claude, including Claude Code. There's no separate allowance to provision.
- **Team and seat-based Enterprise plans:** Usage draws from each user's seat usage limits, including session and weekly limits. Admins can purchase **[usage credits](https://support.claude.com/en/articles/12005970)** for users who need more.
- **Usage-based Enterprise plans:** Usage bills from your organization's consumption at standard API rates. Organization, group, and per-user spend limits apply.
## Monitor usage
- **Compliance API:** Artifacts made in conversations and the **Artifacts** tab are recorded at the artifact level. For docs, events for the doc itself are recorded, but activity inside a doc, like edits and comments, isn't recorded yet.
- **Analytics:** These analytics cover claude.ai/design only, and don't include designs made in conversations or the **Artifacts** tab.
- **Audit logs:** Standalone Claude Design doesn't support audit logs.
Learn more about **[viewing usage analytics for Team and Enterprise plans](https://support.claude.com/en/articles/12883420)**.
------------------------------------------------------------------------
## Data handling and privacy
When users create designs and docs, they may upload design assets, brand guidelines, screenshots, and other materials.
- Uploaded assets are stored persistently, and fall under the same **[data retention and deletion policies](https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data)** as other Anthropic products for organizations.
- A custom retention period set on an Enterprise plan can cover artifacts, including projects and design systems moved from standalone Claude Design. An artifact can be permanently deleted if nobody opens it for that period. For a moved project or design system, the period starts on the day of the move and restarts when someone opens or edits the artifact. Learn more in **[Configure custom data retention controls for Enterprise plans](https://support.claude.com/en/articles/10440198)**.
- Claude Design doesn't currently support data residency requirements.
### When someone leaves your organization
Removing someone from your organization, including through your identity provider, removes their access to artifacts at the same time.
### Organizations with special configurations
- **HIPAA-ready configurations:** An Owner can turn on Claude Docs, Slides, Design, Dashboards, and Motion in **[Organization settings \> Artifacts](https://claude.ai/admin-settings/artifacts)** after accepting the terms. These aren't covered under your Business Associate Agreement (BAA), so keep protected health information (PHI) out of them.
- **CMEK:** Artifacts are available.
- **Education and K-12 organizations:** Email invitations aren't available.
------------------------------------------------------------------------
## Third-party platform availability
Artifacts are available in Claude on web and desktop, in Claude Code, and at claude.ai/design for standalone Claude Design until it closes. In Claude for iOS and Claude for Android, users can ask for an artifact, view the result, and edit docs, decks, and designs. Artifacts aren't available through third-party cloud platforms.
------------------------------------------------------------------------
## Frequently asked questions
### Do I need to turn a feature on for the whole organization if only some users need it?
Yes. The organization setting must be on before custom roles can control per-user access. If a feature is off at the organization level, no one can use it regardless of their role.
### Can I restrict templates to specific departments?
Yes, on Enterprise plans, with custom roles. Each template has its own capability, and standalone Claude Design has a separate capability from the **Design** template.
### What's the difference between external sharing and email invitations?
**External sharing** lets users publish an artifact that anyone outside your organization can open with a link. **Email invitations outside your organization** lets users invite named people outside your organization to a specific artifact. Each has its own setting.
### Who can share a design system with everyone, set the default, or delete one?
In Artifacts, an organization Owner or Primary Owner can share a design system with everyone in your organization and set or remove the organization default. Members with the User, Admin, or custom role can't. A design system's owner, normally the person who created it, can delete it, and an organization Owner or Primary Owner can delete one that’s shared with everyone.
The **Claude Design Admin** permission applies only in the standalone Claude Design app. It doesn't let anyone share, set as default, or delete a design system created in Artifacts.
### Can users export what they make?
Yes. For more information, refer to **[View and export](https://support.claude.com/en/articles/9487310-what-are-artifacts-and-how-do-i-use-them#h_71205f2c4b)** in **[What are artifacts and how do I use them?](../15-Claude-AI-Features/what-are-artifacts-and-how-do-i-use-them-claude-help-center.md)**
---
## Auto mode classifier request charges - Claude Code Docs
Source: https://code.claude.com/docs/en/auto-mode-classifier-billing
Path: 17-Billing-Plans/auto-mode-classifier-billing.md
## On this page
- [Respond to the notice](#respond-to-the-notice)
- [Make the session eligible](#make-the-session-eligible)
- [Why the notice appears](#why-the-notice-appears)
- [Related resources](#related-resources)
Permissions and sandboxing
# Auto mode classifier request charges
Copy pageCopy page
Resolve the Claude Code notice saying this session isn’t eligible for auto mode’s no-charge classifier requests: what it means, why it appears, and what to do.
Copy pageCopy page
In [auto mode](../02-Claude-Code-CLI/permission-modes.md#eliminate-prompts-with-auto-mode), a classifier checks actions such as shell commands and network requests before they run. Wherever [server-side checks are on](../02-Claude-Code-CLI/permission-modes.md#server-side-classifier-review), the server performs those checks as part of the session’s own model requests, at no charge. This notice means the server’s checks aren’t reaching your session, so Claude Code is making its own classifier requests instead, and on your account those requests count toward your token usage:
```python
We're changing auto mode to no longer charge for classifier requests in Claude Code. However, this session isn't eligible.
```
At the prompt, Claude Code holds the first action it would check that way until you answer. Auto mode keeps working, and its classifier requests are billed as they were before. The most common cause is an LLM gateway or proxy between Claude Code and the API, and when Claude Code can identify one, the notice names it. Press **Enter** to continue, or see [Make the session eligible](#make-the-session-eligible) to keep it from appearing in new sessions.
[](#respond-to-the-notice)
Respond to the notice
The notice holds the action until you answer it:
- **Enter** continues: the held action and the rest of the session use Claude Code’s own classifier requests, billed as token usage as before, and the notice doesn’t appear again in that session. When the notice named a gateway, acknowledging it keeps it from reappearing on this machine for 24 hours. When it didn’t, the notice returns the next time a session falls back.
- **Esc** or **Ctrl+C** cancels: the held action doesn’t run and the current turn stops, with the session still in auto mode. Nothing is remembered, so the notice appears again before the next checked action.
To stop using auto mode instead, switch permission modes with `Shift+Tab` after you answer. Where the notice can’t wait for an answer, Claude Code reports the same text and the session continues in auto mode, unless a gateway acknowledgment on this machine in the last 24 hours has dismissed it. In [non-interactive mode](../02-Claude-Code-CLI/headless.md) with `-p` it prints the text to stderr, and in `stream-json` output it emits a `system` warning message, which Agent SDK applications can read from the message stream.
[](#make-the-session-eligible)
Make the session eligible
If a gateway is the cause, ask your company’s admin or your gateway provider to pass requests and replies through unchanged. That means forwarding request headers and body fields as they are, including ones the gateway doesn’t recognize such as the `safeguards` request field, and returning responses and streaming events without dropping keys such as the `safeguard_results` field or rewriting tool-use IDs, as the [gateway compatibility guide](../13-Enterprise-Admin/llm-gateway-protocol.md#feature-pass-through) describes. A gateway that passes traffic through this way keeps working with this feature and with future ones. New sessions then use the server’s checks again. If you already know that your gateway can’t provide the server’s checks, tell Claude Code not to ask for them there by setting `CLAUDE_CODE_AUTO_MODE_SERVER` to `0` before you start the session, in your shell or in the [`env` settings key](../02-Claude-Code-CLI/settings-reference.md#env):
```python
export CLAUDE_CODE_AUTO_MODE_SERVER=0
```
Classifier requests are then always Claude Code’s own, billed the same way, and the notice doesn’t appear. On a direct connection to the Anthropic API, the variable requires Claude Code v2.1.281 or later. Setting `CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS=1` while `CLAUDE_CODE_AUTO_MODE_SERVER` is unset turns the server’s checks off as well, except as [Disable pre-release capabilities](../13-Enterprise-Admin/llm-gateway-protocol.md#disable-pre-release-capabilities) describes. `CLAUDE_CODE_AUTO_MODE_SERVER` is a temporary setting and may be removed in a later release.
[](#why-the-notice-appears)
Why the notice appears
[Server-side classifier review](../02-Claude-Code-CLI/permission-modes.md#server-side-classifier-review) lists which sessions ask the server for the classifier checks. Pro, Max, and Team plans never show the notice. When it appears, the usual causes are:
- **An LLM gateway or proxy is in the path**: one that strips or rewrites request headers, drops request fields it doesn’t recognize, or edits responses. The server then never receives the request for checks, or Claude Code never receives the results. When your configuration or the responses identify the gateway, the notice names it.
- **Server-side checks haven’t reached your platform, region, or credential yet**: whether a platform or region performs them depends on that platform’s rollout. If you see the notice with no gateway or proxy in the path and it keeps appearing, this is the likely cause. To confirm, contact support or your company’s admin, or report it with `/feedback`.
To check a session that’s in auto mode, run `/status` at the Claude Code prompt: its **Auto mode server** row reads `Enabled` while the server’s checks decide the session’s actions and `Disabled` once the session has fallen back. When a gateway cuts responses short or rewrites the results into a form Claude Code can’t read, you get denials with no verdict in place of this notice; see [Server-side classifier review](../02-Claude-Code-CLI/permission-modes.md#server-side-classifier-review).
[](#related-resources)
Related resources
- [Auto mode](../02-Claude-Code-CLI/permission-modes.md#eliminate-prompts-with-auto-mode): what auto mode is and what it blocks by default
- [Server-side classifier review](../02-Claude-Code-CLI/permission-modes.md#server-side-classifier-review): which sessions ask the server to check actions, and the Claude Code version each one requires
- [Gateway compatibility guide](../13-Enterprise-Admin/llm-gateway-protocol.md#feature-pass-through): what breaks when a gateway strips headers or body fields
- [The server returned no safety verdict](../02-Claude-Code-CLI/errors.md#the-server-returned-no-safety-verdict): the denial you see when the server gives no verdict for an action
- [Manage costs effectively](costs.md): track token usage and reduce Claude Code costs
---
## Can you delete data that I sent via Team and Enterprise plans? | Claude Help Center
Source: https://support.claude.com/en/articles/9796617-can-you-delete-data-that-i-sent-via-team-and-enterprise-plans
Path: 17-Billing-Plans/can-you-delete-data-that-i-sent-via-team-and-enterprise-plans.md
# Can you delete data that I sent via Team and Enterprise plans?
March 16, 2026
*This article is about our commercial products such as Claude for Work and the Anthropic API. For our consumer products such as Claude Free, Pro, Max and when accounts from those plans use Claude Code, see* *[here](https://privacy.claude.com/en/collections/10663362-consumers).*
While using Team and Enterprise plans, prompts and conversations in the product are maintained so you can see your conversation history in the product. You can [delete your chats](https://privacy.claude.com/en/articles/11117329-how-can-i-delete-or-rename-a-conversation) to remove them from your visible history.
We also retain data in our backend systems as described [here](https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data).
Read more [here](https://privacy.claude.com/en/articles/7996875-can-you-delete-data-that-i-sent-via-api) about deleting data sent via API.
Enterprise plan customers can also set [custom retention timelines](https://support.claude.com/en/articles/10440198-custom-data-retention-controls-for-claude-enterprise) for their organization’s data.
---
## Cancel your organization's Team plan subscription | Claude Help Center
Source: https://support.claude.com/en/articles/9267323-cancel-your-organization-s-team-plan-subscription
Path: 17-Billing-Plans/cancel-your-organization-s-team-plan-subscription.md
# Cancel your organization's Team plan subscription
An Owner or Primary Owner can cancel Team plan access by navigating to **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**. Canceling your Team plan subscription means that your organization won't be charged for the next billing cycle. Your team will continue to have access to Claude until the end of the current billing cycle.
After you cancel, the option to remove members from **[Organization settings \> Members](https://claude.ai/admin-settings/members)** will no longer be available. If you need members removed from your organization while your subscription is cancelled (for example, before resubscribing at a lower seat count), **[reach out to our Support team](../15-Claude-AI-Features/how-to-get-support.md)**.
If your team has claimed monthly API credits, new monthly credits stop when you cancel, and credits you already have stay usable until they expire at the end of each billing cycle. Monthly API credits included with Max and Team plans aren’t purchased, so they can’t be refunded.
---
## Change your Team plan from monthly to annual billing | Claude Help Center
Source: https://support.claude.com/en/articles/12083917-change-your-team-plan-from-monthly-to-annual-billing
Path: 17-Billing-Plans/change-your-team-plan-from-monthly-to-annual-billing.md
# Change your Team plan from monthly to annual billing
August 6, 2026
Owners and Primary Owners of Team plans with monthly subscriptions can switch from the monthly plan to an annual plan by following these steps:
1. Navigate to **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)** or **[claude.ai/upgrade](https://claude.ai/upgrade)**.
2. You’ll see a banner confirming your current monthly plan in your Billing settings; click the “Switch to Annual” button.
3. Or from /upgrade, click the “Switch to Annual plan” button:
4. The confirmation screen will display the total cost for your upgrade from monthly to annual billing:
5. Click “Confirm subscription.”
6. Your new annual Team plan will start immediately and you will be credited for any unused time on your previous monthly plan.
---
## Choose a Claude plan | Claude Help Center
Source: https://support.claude.com/en/articles/11049762-choosing-a-claude-plan
Path: 17-Billing-Plans/choosing-a-claude-plan.md
# Choose a Claude plan
May 19, 2026
Use the following guide to determine which plan is right for you.
[TABLE]
The plans listed above are intended for individual users. Looking for a plan for your organization or company? Read more about our Team and Enterprise plans:
- **[What is the Team plan?](what-is-the-team-plan.md)**
- **[What is the Enterprise plan?](what-is-the-enterprise-plan.md)**
---
## Claude Fable 5 one-time free credits promotion | Claude Help Center
Source: https://support.claude.com/en/articles/15862783
Path: 17-Billing-Plans/claude-fable-5-one-time-free-credits-promotion-claude-help-center.md
# Claude Fable 5 one-time free credits promotion
September 1, 2026
**Note:** This promotion applied to Claude Fable 5 only. It didn't include Claude Fable 5.1, and the claim window closed on August 2, 2026.
***This promotion applies to Pro plans and standard seats on Team plans.*** When the Claude Fable 5 weekly usage promotion ends on July 19, 2026 at 11:59:59 PM PT, Fable 5 will still be available to you but moves from your plan's weekly usage limits to pay-as-you-go usage credits.
To make the change easier, we're giving eligible subscribers free one-time promotional credits. The free credits are standard usage credits, so they're not limited to Fable 5. You can use them on any model, and they can be used if you have reached your plan limit. Learn more about **[usage credits](https://support.claude.com/en/articles/12429409)**.
This article explains what the credits are, who's eligible, how to claim them, and when they expire.
**Note:** Claude Fable 5 is now a standard part of Max plans, premium seats on Team plans, and premium seats on seat-based Enterprise plans. You can continue to spend up to 50% of your weekly limits on Fable 5, with no additional charge beyond the rate of your subscription, so those plans aren’t eligible to receive these particular promotional credits. For more details, see **[Claude Fable 5 on your plan](https://support.claude.com/en/articles/15424964)**.
The free promotional credits are available to eligible Pro plans and standard seats on Team plans. Max and Enterprise plans are not eligible for these particular promotional credits. For eligibility details, see **[Who's eligible](#h_b1b3133207)** below. Additional **[offer terms apply](https://www.anthropic.com/legal/promotion-credit-terms)**.
## What you get
Claude Fable 5 was previously included in your plan for a limited time, and let you use up to 50% of your weekly subscription limits on Fable 5 at no extra cost. Now you can keep using Fable 5 with usage credits and we’re offering \$100 worth of usage credits to cover your initial use.
The amount of credits you’ll receive depends on your plan:
- **Pro plans (monthly and annual plans):** \$100 worth of usage credits
- **Team plans:** \$100 worth of usage credits per *purchased* standard seat, up to \$2500 per organization. These credits are pooled into a single balance your whole team can draw from. A seat must be purchased, not just assigned to a team member, to count toward eligibility. Only an Owner or Primary Owner can claim them for the organization.
**Note:** The free promotional credits are non-refundable. The promotional credits expire 60 days after they become available.
## Promotion timing and expiration
- These promotional credits will gradually become available starting July 20, 2026, and you can claim your promotional credits through August 2, 2026 at 11:59 PM PT. After this window closes, the credits can no longer be claimed.
- These new promotional credits expire on September 17, 2026 at 11:59 PM PT, 60 days after the promotion begins, regardless of when you’ve claimed them.
## Who's eligible
You're eligible if you held a qualifying Pro plan or Team plan with standard seats as of July 19, 2026 at 11:59 PM PT. Free trials are not included in this promotion.
**Note:** On Team plans, members don't see the promotion. Only an Owner or Primary Owner can claim the free credits for the organization.
## How to claim your free credits
Claiming turns on usage credits for your account so they're ready to use.
### Pro plans
1. Go to the free credits prompt that appears when you open Claude, or the banner in **[Settings \> Usage](https://claude.ai/settings/usage)**. It shows the amount of free credits you'll get.
2. Review the terms, then select "Claim free credits."
3. If your account doesn't have a payment method on file, add one when prompted.
**Note:** On Claude Mobile, claiming takes you to claude.ai to finish, since some steps aren't yet available in the mobile apps.
### Team plans
1. As an Owner or Primary Owner, open the free credits prompt or the banner in **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**.
2. Review the details, including your organization's total credit amount.
3. Select "Claim free credits" to enable them for your organization.
Members don't need to request access. Once an Owner or Primary Owner claims the free credits, the credits are pooled for the whole organization.
## How to see your credit amount
Before you claim, the amount of free credits you'll get is shown in the claim prompt. On Team plans, the Owner or Primary Owner sees the organization's total amount when they go to claim their credits.
After you claim, you can see your credit balance in your usage settings. Your balance stays visible even if your subscription lapses or is canceled, so you can still use any remaining credits until they expire if you’re on an eligible plan.
Free credits are calculated in US dollars. If your account is billed in a different currency, the credit is converted to your local currency when it's added to your account, and that's the amount you'll see in your usage settings.
## What happens when your credits run out or expire
- **If you have other usage credits:** Your free promotional credits are spent first, then your other credits, including auto-reload if you have it turned on. You won't see a separate message when this happens.
- **If you have no credits left:** You'll see the standard prompt to add usage credits.
- **When your free credits expire:** The promotional credit expires on September 17, 2026 at 11:59 PM PT, 60 days after the promotion begins, regardless of when you’ve claimed them. To keep using models beyond your plan's limits, you can add more usage credits. Usage credits unrelated to this promotion will expire according to their own terms.
## Frequently asked questions
### Do I have to pay anything to claim my free credits?
No. The credits are free for eligible subscribers. Claiming them turns on usage credits for your account, but you're only charged if you buy additional usage credits later.
### How do I see how much free credit I'm getting?
The promotional credit amount is shown in the claim prompt before you claim. On Team plans, the Owner or Primary Owner sees the organization's total amount at that point. After you claim, your balance appears in your usage settings.
### Can I use my free credits on any model?
Yes. They're standard usage credits and aren't limited to Fable 5. You can use them on any model, and they also cover you if you reach a plan limit.
### What happens to my credits if I cancel my subscription?
Free credits are non-refundable. Your balance stays visible and you can use any remaining credits until they expire if you’re on an eligible plan.
### I'm on a Team plan. How do we get the free credits?
Free credits are granted per purchased standard seat and pooled at the organization level, up to a limit. Only an Owner or Primary Owner can claim them for the organization. When an Owner or Primary Owner claims the free credits, they'll see the organization's total credit amount.
### My account isn't billed in US dollars. What amount will I see?
Free credits are calculated in US dollars for all eligible subscribers. If your account is billed in another currency, the credit is converted to your local currency when it's added to your account, and your usage settings show that local-currency amount. Once added, the balance doesn't change with exchange rates.
### I'm on the Max plan or a premium seat on the Team plan. Do I get these credits?
No. On the Max plan and premium seats on the Team plan, Fable 5 stays included in your plan's usage limits, so those plans don't receive these credits.
### I'm on a legacy seat-based Enterprise plan. Do I get these credits?
No. On seat-based Enterprise plans, premium seats include Fable 5 in your plan's usage limits, so they don't receive these credits. Standard seats access Fable 5 through usage credits only and aren't eligible for this particular one-time promotional credit.
---
## Claude Fable models on your plan | Claude Help Center
Source: https://support.claude.com/en/articles/15424964-claude-fable-models-on-your-plan
Path: 17-Billing-Plans/claude-fable-5-promotional-access.md
# Claude Fable models on your plan
September 2, 2026
We previously ran a promotion that allowed you to use up to 50% of your weekly subscription limit on Claude Fable 5 at no extra cost. That promotion ended on July 19, 2026 at 11:59:59 PM PT, and it applied to Fable 5 only. Claude Fable 5.1 was never part of it.
Fable 5 and Fable 5.1 work the same way on your plan. On Max plans, premium seats on Team plans, and premium seats on legacy seat-based Enterprise plans, both are a standard part of your plan. On Pro plans, standard seats on Team plans, and standard seats on legacy seat-based Enterprise plans, both models run on pay-as-you-go usage credits. This article explains how they work on each plan, how to access them, and what happens when you reach your usage limits.
Claude Fable 5 and Claude Fable 5.1 are available on all paid plans (Pro, Max, Team, and Enterprise).
## How Fable models work on each plan
- **Max plans, premium seats on Team plans, and premium seats on seat-based Enterprise plans:** Fable 5 and Fable 5.1 are included as a standard part of your plan. You can use up to 50% of your weekly usage limits on Fable models at no extra cost. They draw from your plan's regular weekly usage limits and use them faster than other Claude models. When you reach your Fable limit, you can keep using Fable models with usage credits, or switch to another model to stay within your plan's usage limits.
- **Pro plans and standard seats on Team plans:** Fable 5 and Fable 5.1 aren’t included in your plan's usage limits. You can use them with usage credits, which let you pay for usage beyond what your plan includes. Eligible Pro and Team standard seats qualified for a one-time credit when Fable 5 moved to usage credits in July 2026. That credit applied to the Fable 5 change only, and there's no equivalent credit for Fable 5.1. Learn more about the **[Claude Fable 5 one-time free credits promotion](claude-fable-5-one-time-free-credits-promotion-claude-help-center.md)**.
- **Standard seats on seat-based Enterprise plans:** Fable 5 and Fable 5.1 aren’t included in your plan's usage limits. You can use them if your organization has enabled usage credits, which let you pay for usage beyond what your plan includes. Standard seats on seat-based Enterprise plans don't qualify for the one-time promotional credit.
- **Usage-based Enterprise plans:** Access to Fable 5 and Fable 5.1 is billed at standard API rates. For current per-model pricing, see our **[API pricing page](https://www.anthropic.com/pricing#api)**.
- **Claude API:** Access to Fable 5 and Fable 5.1 is billed at standard API rates. For current per-model pricing, see our **[API pricing page](https://www.anthropic.com/pricing#api)**.
## How to access Claude Fable models
You can access Claude Fable 5 and Fable 5.1 on:
- Claude on the web
- Claude Mobile
- Claude Desktop
- Claude Cowork
- Claude Code
- Claude Design
- Claude for Microsoft 365
- Claude Tag
In Claude on the web, Claude Desktop, and Claude Mobile, select "Fable 5" or “Fable 5.1” from the model picker. In Claude Code, Fable 5 requires version 2.1.170 or later and Fable 5.1 requires version 2.1.255 or later. To use Fable models in Claude Cowork, you need to be on the latest version of Claude Desktop.
## When you reach your Fable usage limit
On Max plans, premium seats on Team plans, and premium seats on seat-based Enterprise plans, once you use up to 50% of your weekly usage limits on Fable models, you can continue in one of two ways: keep using Fable models with usage credits, or switch to another Claude model to keep working within your plan's usage limits.
On Pro plans, standard seats on Team plans, and standard seats on seat-based Enterprise plans, Fable models run on pay-as-you-go usage credits from the start, since they aren’t included in your plan's usage limits.
This works the same way across Claude on the web, Claude Mobile, Claude Desktop, Claude Cowork, and Claude Code. Learn more about **[usage credits](https://support.claude.com/en/articles/12429409)**.
## Frequently asked questions
### Why can’t I see Claude Fable 5 or Fable 5.1?
Check the following:
- You’re on a paid Claude plan. Fable 5 isn’t available on the Free plan.
- If you’re using Claude Code, you’re on version 2.1.170 or later for Fable 5, or 2.1.255 or later for Fable 5.1.
- If you’re using Cowork, you’re on the latest version of Claude Desktop.
- Your organization hasn't enabled Fable models.
### Will this use my regular usage limits?
It depends on your plan. On the Max plan, premium seats on the Team plan, and premium seats on the seat-based Enterprise plan, Fable models count toward your plan's usage limits, and you can use up to 50% of your weekly usage limits on Fable models at no extra cost. On the Pro plan, standard seats on the Team plan, and standard seats on the seat-based Enterprise plan, Fable models run on usage credits rather than your plan's usage limits.
### Will I get 50% more for my weekly limit for Fable models if I’m on the Max plan, Team plan with premium seats, or a seat-based Enterprise plan with premium seats?
No. You can use up to 50% of your weekly limit on Fable models, but your use of other models draws from the same usage limits and you can never use more than your weekly limit. You can track both in your usage settings.
### I'm on the Pro or Team plan. Why is Fable 5 no longer included?
The earlier promotion that included Fable 5 in your plan's weekly usage limits ended on July 19, 2026 at 11:59:59 PM PT. On the Pro plan and standard seats on the Team plan, you can keep using Fable 5 with usage credits or by upgrading to the Max plan. You may also be eligible for a one-time credit. Learn more about the **[Claude Fable 5 one-time free credits promotion](claude-fable-5-one-time-free-credits-promotion-claude-help-center.md)**.
Fable 5.1 works the same way on these plans: it isn't included in your plan's usage limits, and it wasn't part of the earlier promotion.
---
## Claude Team plan for scientists | Claude Help Center
Source: https://support.claude.com/en/articles/16634237-claude-team-plan-for-scientists
Path: 17-Billing-Plans/claude-team-plan-for-scientists.md
# Claude Team plan for scientists
## What is the Claude Team plan for scientists?
The **[Claude Team plan for scientists](../15-Claude-AI-Features/programs-team-plan-for-scientists.md)** gives academic and non-profit research groups and labs discounted access to a Claude Team subscription plan. Standard seats are free, and Premium seats are \$15 per user per month. This discounted pricing is for verified research groups, available for 12 months and offered to a limited number of groups. Final pricing is confirmed after verification at sign up; **[terms apply](https://anthropic.com/legal/team-plan-for-scientists-terms)**.
A principal investigator (PI) can sign up directly, verify their eligibility, and then invite their whole group.
## What’s included?
Every seat includes everything in Claude Team:
- Claude Science, Claude Code, and Claude Cowork
- Central billing and administration
- Single sign-on (SSO)
This plan has Claude Science on by default. An Owner or Primary Owner can turn it off at any time in **[Organization settings \> Claude Science](https://claude.ai/admin-settings/claude-science)**.
Premium seats add five times more usage and higher limits for long-running analyses.
Claude Max and Team plans include monthly credits for the Claude API. On the Team plan for scientists, you’ll receive \$20 USD per Standard seat and \$100 USD per Premium seat. Credits for all seats are pooled into one monthly balance, capped at \$500. Learn more about **[monthly API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)**.
## What does it cost?
- **Standard seats: \$0 per user per month**
- **Premium seats: \$15 per user per month**, or \$180 per user per year with annual billing
This discounted pricing is available for 12 months from when you sign up. After 12 months, seats renew at the then-current price for this plan. We’ll notify workspace admins before that happens. **[Terms apply](https://anthropic.com/legal/team-plan-for-scientists-terms)**.
## Who is eligible?
Principal investigators (PIs) or equivalent at accredited universities and nonprofit research institutes working in the natural sciences, mathematics, computer science, engineering, and related fields are eligible to apply. Once verified, PIs can add additional group members including postdocs, graduate students, and researchers. Eligibility as PI is verified when you sign up.
If you’re at a for-profit company, contract research organization, or industry R&D team, this plan isn’t the right fit—see our standard Team and Enterprise plans. Visit **[our pricing page](pricing.md)** to compare.
## How do I sign up?
1. Go to **[the program page](../15-Claude-AI-Features/programs-team-plan-for-scientists.md)** and start an application as the PI or lab lead.
2. Verify your eligibility. You’ll confirm your institutional affiliation. Most applications are reviewed within seven business days.
3. Once approved, you’ll get an email and can set up your workspace and invite your group right away.
## How many seats can I have?
From 1 to 25 seats per group.
## Frequently asked questions
### I’m already on the discounted Team plan. What changes?
This applies only to workspaces that were already on the discounted Team plan before August 27, 2026. If you’re applying the discount to a standard Team plan for the first time, see **[Can I apply the discounted Team plan pricing to my existing Team plan?](#h_80d427d957)** below. Your plan moves to the new pricing automatically for billing charges after August 27, 2026—no action needed. Any seats you add to your plan after August 27, 2026 will be billed at the new pricing. Your workspace admin will get an email with the details.
### My university already has a Claude Enterprise agreement. Should I use this?
Check with your institution first. If your campus has a Claude agreement, contact your account administrator. This plan is for small research groups whose institutions don’t have an enterprise agreement in place. If you’re an institution interested in Claude Enterprise, please **[contact us](https://claude.com/contact-sales)** and a member of our team will get in touch.
### What if my group stops using it?
If a group has no activity for 90 days, we may return it to standard Team pricing so that discounted seats go to active researchers. We’ll email the workspace admin before that happens.
### What if my project needs more than a seat provides?
AI for Science is Anthropic’s grant program for ambitious research projects that need more capacity than a seat provides. It’s application-based and reviewed on merit. Learn more about the program and how to apply here: **[Introducing Anthropic's AI for Science Program](../19-Reference/ai-for-science-program.md)**.
### Does Claude train on my data?
By default, Anthropic doesn’t train its models on user data from Team and Enterprise plans. If you explicitly opt in or submit feedback, those conversations may be used to improve our models or products.
### Can I apply the discounted Team plan pricing to my existing Team plan?
First, you must complete the **[application flow](https://claude.ai/labs-verification/attestation)** to verify your eligibility for the discounted plan. Once you are verified, you can apply the discounted pricing to an existing plan that you manage in **Settings \> Account** under **Program verifications**.
If your existing Team plan is billed annually and you apply the discounted pricing partway through your annual term, your plan switches to monthly billing at the discounted rate. The unused portion of your prepaid annual term becomes a credit on your workspace’s billing account, and it’s applied automatically to your future monthly invoices until it’s used up. This is an account credit, not a refund to your original payment method.
**Note:** If all your seats are Standard seats (\$0 per user per month), your monthly invoices will be \$0. The credit stays on your account until a charge is generated, for example when you add Premium seats.
---
## Manage costs effectively - Claude Code Docs
Source: https://code.claude.com/docs/en/costs
Path: 17-Billing-Plans/costs.md
## On this page
- [Track your costs](#track-your-costs)
- [Using the /usage command](#using-the-%2Fusage-command)
- [Prompt cache statistics](#prompt-cache-statistics)
- [Plan usage breakdown](#plan-usage-breakdown)
- [Apply recommendations with the fix shortcut](#apply-recommendations-with-the-fix-shortcut)
- [Check your usage-credits spend](#check-your-usage-credits-spend)
- [When the usage request fails](#when-the-usage-request-fails)
- [Read the token count beside the spinner](#read-the-token-count-beside-the-spinner)
- [Analyze your usage patterns](#analyze-your-usage-patterns)
- [Add usage credits to your subscription](#add-usage-credits-to-your-subscription)
- [Manage costs for your organization](#manage-costs-for-your-organization)
- [Report spend at your contracted rates](#report-spend-at-your-contracted-rates)
- [Claude for Teams and Enterprise](#claude-for-teams-and-enterprise)
- [Claude Console](#claude-console)
- [Rate limit recommendations](#rate-limit-recommendations)
- [Cloud providers](#cloud-providers)
- [When a developer asks about a limit](#when-a-developer-asks-about-a-limit)
- [Agent team token costs](#agent-team-token-costs)
- [Reduce token usage](#reduce-token-usage)
- [Manage context proactively](#manage-context-proactively)
- [Choose the right model](#choose-the-right-model)
- [Reduce MCP server overhead](#reduce-mcp-server-overhead)
- [Install code intelligence plugins for typed languages](#install-code-intelligence-plugins-for-typed-languages)
- [Offload processing to hooks and skills](#offload-processing-to-hooks-and-skills)
- [Move instructions from CLAUDE.md to skills](#move-instructions-from-claude-md-to-skills)
- [Adjust extended thinking](#adjust-extended-thinking)
- [Delegate verbose operations to subagents](#delegate-verbose-operations-to-subagents)
- [Manage agent team costs](#manage-agent-team-costs)
- [Write specific prompts](#write-specific-prompts)
- [Work efficiently on complex tasks](#work-efficiently-on-complex-tasks)
- [Background token usage](#background-token-usage)
- [Why usage climbs in a long session](#why-usage-climbs-in-a-long-session)
- [Understanding changes in Claude Code behavior](#understanding-changes-in-claude-code-behavior)
Usage and costs
# Manage costs effectively
Copy pageCopy page
Track token usage, set team spend limits, and reduce Claude Code costs with context management, model selection, extended thinking settings, and preprocessing hooks.
Copy pageCopy page
Claude Code charges by API token consumption. For subscription plan pricing (Pro, Max, Team, Enterprise), see [claude.com/pricing](pricing.md). Per-developer costs vary widely based on model selection, codebase size, and usage patterns such as running multiple instances or automation. Across enterprise deployments, the average cost is around \$13 per developer per active day and \$150-250 per developer per month, with costs remaining below \$30 per active day for 90% of users. To estimate spend for your own team, start with a small pilot group and use the tracking tools below to establish a baseline before wider rollout. This page covers Claude Code usage only: how to [track your costs](#track-your-costs), [manage costs for your organization](#manage-costs-for-your-organization), and [reduce token usage](#reduce-token-usage). For usage limits in other Claude products, see the [Claude Help Center](https://support.claude.com).
[](#track-your-costs)
Track your costs
[](#using-the-/usage-command)
Using the `/usage` command
The Session block in `/usage` shows API token usage and is intended for API users. Claude Max and Pro subscribers have usage included in their subscription, so the session cost figure isn’t relevant for billing purposes. Subscribers see plan usage bars, activity stats, and a usage breakdown on the same screen.
The Session block at the top of `/usage` shows detailed token usage statistics for your current session. Claude Code computes the dollar figure locally from token counts at list price, unless a [`modelPricing`](../02-Claude-Code-CLI/settings-reference.md#modelpricing) table is in effect. An administrator sets one in your organization’s managed settings so the figure uses your contracted rates, and while a table is in effect the `Total cost` line carries the note `at your organization's configured rates`. The figure is an estimate, so for authoritative billing see the Usage page in the [Claude Console](../04-API-Reference/Other/playground.md).
```python
Total cost: $0.55
Total duration (API): 6m 20s
Total duration (wall): 6h 33m 10s
Total code changes: 0 lines added, 0 lines removed
Usage by model:
claude-sonnet-4-6: 1.2k input, 5.3k output, 940.0k cache read, 50.0k cache write ($0.55)
```
These totals reset when `/clear` starts a new session, so the next session’s total cost starts at \$0. Before v2.1.211, they kept accumulating across `/clear` for the lifetime of the Claude Code process. For a response from the Claude API billed at the 1.1× [data residency rate](about-claude-pricing.md#data-residency-pricing), Claude Code multiplies the list price of that response’s tokens by 1.1 in the session cost figure. The same total appears in the [status line’s cost field](../02-Claude-Code-CLI/statusline.md#cost-and-duration-tracking), and the multiplied figure also counts toward [`--max-budget-usd`](../02-Claude-Code-CLI/cli-reference.md#cli-flags).
[](#prompt-cache-statistics)
Prompt cache statistics
After the main conversation’s first API response, Claude Code also adds a `Prompt cache (main)` line to the Session block, summarizing the session’s [prompt cache](../02-Claude-Code-CLI/prompt-caching.md) use: the request count, the share of input tokens served from cache, cache misses, and whether the cache is warm right now. Requires Claude Code v2.1.251 or later.
```python
Prompt cache (main): 14 requests · 91% of input tokens from cache · 2 misses (last 6m 10s ago, 310.2k tokens re-cached) · 1 expected rebuild (compaction or tool-result clearing) · warm (1h TTL, last activity 40s ago)
```
The misses, expected rebuilds, and warm or cold parts of the line mean the following:
- **Misses**: requests that re-processed content the cache already held, with the time of the last miss and how many tokens those requests wrote back to the cache. [Actions that invalidate the cache](../02-Claude-Code-CLI/prompt-caching.md#actions-that-invalidate-the-cache) lists the usual causes. When Claude Code can identify a likely cause for the last miss, the line names it too, for example `likely cause: tool definitions changed`. The likely-cause text requires Claude Code v2.1.260 or later.
- **Expected rebuilds**: when Claude Code has itself just rewritten the conversation, by [compaction](../02-Claude-Code-CLI/prompt-caching.md#compacting-the-conversation) or by clearing old tool results from context, it counts the same kind of miss as an expected rebuild instead. This part appears only after at least one expected rebuild has happened.
- **Warm or cold**: whether the cached prefix is still within its [cache lifetime](../02-Claude-Code-CLI/prompt-caching.md#cache-lifetime), with the TTL in effect. When the cache is cold, the line shows how long the session has been idle. When no response has reported cache tokens, the line ends with `no prompt caching reported by the API` instead.
The counts come from the cache token fields in the API’s responses, so the line works on every provider and gateway. It covers the main conversation only, not subagents. `/clear` resets it with the rest of the Session block. Status line scripts can read the same numbers from the [`prompt_cache` object](../02-Claude-Code-CLI/statusline.md#prompt-cache-fields).
[](#plan-usage-breakdown)
Plan usage breakdown
On a Pro, Max, Team, or Enterprise plan, `/usage` also shows a breakdown of what counts against your plan limits, with recommendations:
- **Attribution**: recent usage attributed to skills, subagents, plugins, and individual MCP servers, each shown as a percentage of the total. An MCP server’s share counts only the requests that consumed one of its tool results. Before v2.1.222, after one call to an MCP server, Claude Code attributed every subsequent request to that server, overstating its share.
- **Recommendations**: suggested changes, one per row. Each row starts with a share of your recent usage, at least 10%, as in `25% Trim ~/code/api/CLAUDE.md · 49k tokens per request`.
- **How to read the share**: it tells you how much of your usage the row applies to, not how much the change saves. One request can count toward several rows, so the shares can add up to more than 100%.
- **How to apply recommendations**: to have Claude Code apply the ones it can, see [Apply recommendations with the fix shortcut](#apply-recommendations-with-the-fix-shortcut)
- **Loops**: a row for each of the heaviest [`/loop` or other session-scoped scheduled tasks](../02-Claude-Code-CLI/scheduled-tasks.md) that ran recently, ordered by total tokens, with a count of the rest. Requires Claude Code v2.1.242 or later.
- **What each row reports**: how often the task fires, how many times it ran, its total and per-run tokens, and when it last ran
- **Stopped and re-created loops**: Claude Code keys a row by the task’s prompt, so a loop you stop and re-create stays one row
Press `d` or `w` to switch between the last 24 hours and the last 7 days. The figures are approximate and computed from local session history on this machine, so usage from other devices or claude.ai is not included. In the [VS Code extension](../03-IDE-Integrations/vs-code.md#check-account-and-usage), the attribution shares and recommendations appear in the Account & usage dialog with a Day and Week toggle, without the Loops rows.
[](#apply-recommendations-with-the-fix-shortcut)
Apply recommendations with the fix shortcut
When the `/usage` footer shows a hint such as `f to fix 2 of 3`, press `f` to have Claude Code act on the recommendations it can. The `f` shortcut requires Claude Code v2.1.305 or later.
1. After any turn in progress ends, Claude Code runs each [`/effort`](../02-Claude-Code-CLI/model-config.md#adjust-effort-level) command shown in a row without `run`.
2. Claude then gets one prompt with a step for each of the other rows it can act on. The prompt asks Claude to show you each change before making it.
To see what pressing `f` does with each of your rows, find the row’s shape in the first column:
| Row shape | Example row | When you press `f` |
|:-----------------------------------------------------|:---------------------------------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Ends in an `/effort` command with no `run` before it | `40% Switch from max to high effort · /effort high` | Claude Code runs the command |
| Ends in `run` and a command | `30% Compact before you step away · run /compact` | Nothing happens for this row. Run the command yourself at the Claude Code prompt |
| Ends in anything else | `25% Trim ~/code/api/CLAUDE.md · 49k tokens per request` | Claude gets a step in the prompt for some of these rows, and nothing happens for the rest. If Claude shows you no change for a row, follow that recommendation yourself |
In `f to fix 2 of 3`, the first number counts the rows Claude Code acts on when you press `f`, and the second counts the rows shown. A hint with no `of` in it, such as `f to fix both`, means Claude Code acts on every row shown. While [Remote Control](../02-Claude-Code-CLI/remote-control.md) is connected, the footer shows no `f` hint. If pressing `f` closes `/usage` with `Nothing was sent. Turn off Remote Control to use fixes.`, Remote Control connected while `/usage` was open. To use `f` again, [disconnect Remote Control](../02-Claude-Code-CLI/remote-control.md#check-connection-status), then run `/usage` at the Claude Code prompt and press `f` again.
[](#check-your-usage-credits-spend)
Check your usage-credits spend
`/usage` also shows a usage-credits row while [usage credits](#add-usage-credits-to-your-subscription) are on. What the row shows depends on your plan:
- **Pro and Max**: your spend for the current month, measured against your monthly spend limit when you have set one. When you haven’t set a limit, the row shows `Unlimited` and no spend figure.
- **Team and Enterprise**: your own spend for the current month, measured against any [limit your organization set](#claude-for-teams-and-enterprise) that applies to you. A limit that covers the whole organization doesn’t appear in the row. When you have no limit of your own, the row shows your spend with no limit beside it. While usage credits are off for you, `/usage` shows no usage-credits row.
When you have a spend limit, the row appears as soon as usage credits are on and shows 0% until you first spend usage credits. Before v2.1.236, `/usage` showed the row only on Pro and Max plans, and a row with a spend limit stayed hidden until you had spent something.
[](#when-the-usage-request-fails)
When the usage request fails
When the request for your plan limits fails, most often because the usage endpoint is rate limited, `/usage` shows the last usage bars it loaded on this machine within the past 60 minutes, along with a `Showing last-known usage` note stating how long ago that data was fetched. Press `r` to retry; a successful retry replaces the last-known bars with fresh data. Without a snapshot from the past 60 minutes, `/usage` reports that the usage endpoint is rate limited and offers the same retry shortcut. Before v2.1.208, a rate-limited request in a session that hadn’t loaded usage yet always showed the error with no bars. A message such as `rate limited until 3:14am` in `/usage` means Claude Code can’t fetch your plan limits again until then, not that your work with Claude is limited. If you press `r` earlier, expect the same message. Press `r` after that time for fresh data.
[](#read-the-token-count-beside-the-spinner)
Read the token count beside the spinner
While Claude works in the main conversation, the line beside the spinner can end with an elapsed time and a token count, as in `Deciphering… (10m 27s · ↓ 5.5k tokens)`. It is a live, approximate count of the output the current turn has produced so far. The arrow beside the count points down while output arrives or tools run.
- **What it covers**: output the turn generates, such as the text and tool calls Claude streams back, its thinking, and the output of subagents that run in the [foreground](../09-Agents-Patterns/sub-agents.md#run-subagents-in-foreground-or-background)
- **What it leaves out**: what Claude Code sends to the model, so your prompt, the conversation history, and the rest of your context don’t move it
- **When it resets**: at the start of each turn, and when Claude Code [compacts the conversation](../02-Claude-Code-CLI/prompt-caching.md#compacting-the-conversation)
- **When it stays hidden**: until output starts arriving, when the row is too narrow to fit it, and in [screen reader mode](../02-Claude-Code-CLI/accessibility.md)
It won’t match the `Usage by model` output figures in the `/usage` Session block, which add up the whole session rather than one turn. It also differs from the token count [verbose mode adds](../02-Claude-Code-CLI/statusline.md#notifications-share-the-status-line-row), because that count measures the size of your context rather than one turn’s output.
[](#analyze-your-usage-patterns)
Analyze your usage patterns
Run [`/insights`](../02-Claude-Code-CLI/commands.md#all-commands) for a report on how you work rather than how many tokens you’ve used. It analyzes your recent sessions on this machine and writes an HTML report covering what you work on, friction points such as misunderstood requests or buggy code, and suggestions for using Claude Code more effectively. A single run analyzes up to 200 sessions it hasn’t seen before and skips very short ones. When sessions are left out, the report header shows the analyzed count with the total in parentheses, for example `200 sessions (412 total)`. When [auto mode](../02-Claude-Code-CLI/permission-modes.md#eliminate-prompts-with-auto-mode) is available to the session and your recent sessions mostly ran without it, the report can also include an estimate of how many permission prompts auto mode could have handled across those sessions. Claude Code writes the latest report to `~/.claude/usage-data/report.html` and saves a timestamped copy of each run in the same directory, so earlier reports aren’t overwritten. Claude Code deletes reports on the same schedule as the rest of your session data: at startup, it removes files older than [`cleanupPeriodDays`](../02-Claude-Code-CLI/claude-directory.md#cleaned-up-automatically), 30 days by default. You can run `/insights` on any plan and with any provider. The analysis runs through the same provider and account as your regular sessions, and the tokens count against your plan or API usage. Sessions from other devices and claude.ai aren’t included.
[](#add-usage-credits-to-your-subscription)
Add usage credits to your subscription
[Usage credits](extra-usage-for-paid-claude-plans.md) let you keep working past your plan’s usage limit. To manage them, run `/usage-credits` after signing in with your claude.ai subscription through `/login`; the command isn’t available with API key authentication. In self-serve Enterprise organizations, Enterprise trials, and Enterprise organizations billed through AWS Marketplace, the command requires Claude Code v2.1.248 or later; earlier versions reject it with [`Unknown command: /usage-credits`](../02-Claude-Code-CLI/errors.md#unknown-command). What it opens depends on your role:
| Your role | What `/usage-credits` does |
|:-------------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Pro or Max subscriber | Opens [**Settings \> Usage**](https://claude.ai/settings/usage) on claude.ai in the browser. In its **Usage credits** section you can turn usage credits on or off and check your credit balance, this month’s spend, and your monthly spend limit |
| Team or Enterprise member with billing access | Opens your organization’s usage settings, [**Organization settings \> Usage**](https://claude.ai/admin-settings/usage), in the browser |
| Team or Enterprise member without billing access | Asks you to confirm, then sends a request to your organization’s admins. Before v2.1.211, Claude Code sent the request without a confirmation step |
For Team and Enterprise members without billing access, the confirmation appears only in interactive sessions: in non-interactive mode with the `-p` flag and from [Remote Control](../02-Claude-Code-CLI/remote-control.md), the command sends no request and tells you to run it in an interactive session instead. If you run `/usage-credits` again while your earlier request is waiting on an admin, Claude Code tells you a request has already been sent rather than sending a duplicate. After an admin dismisses your request, running the command again sends a new one. Before v2.1.222, a dismissed request also blocked new requests. On Pro and Max plans, when you reach your spend limit with usage credits still available, Claude Code prompts you to raise or remove the limit without leaving the CLI. If the server rejects the change, see [Could not update your spend limit](../02-Claude-Code-CLI/errors.md#could-not-update-your-spend-limit).
[](#manage-costs-for-your-organization)
Manage costs for your organization
Which controls you have depends on how your organization accesses Claude Code: a Claude for Teams or Enterprise plan, the Claude Console, or a cloud provider. On Teams and Enterprise plans, usage draws from each member’s seat allowance. On the Console and on cloud providers, usage is billed per token to your organization. If your organization mixes sign-in methods, each developer is metered according to the one they authenticated with. The table maps each setup to where you see spend, where you cap it, and how you pull per-user numbers. On an individual Pro or Max plan you have no organization to manage, so track your own usage-credit spend, including [fast mode](../02-Claude-Code-CLI/fast-mode.md#see-where-fast-mode-spend-appears), under [Add usage credits to your subscription](#add-usage-credits-to-your-subscription).
| Your setup | See spend | Cap spend | Per-user reporting |
|:----------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------------------------------------------------|:-------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| [Claude for Teams or Enterprise](#claude-for-teams-and-enterprise) | [Spend report in org analytics](view-usage-analytics-for-team-and-enterprise-plans.md) | Spend limits in admin settings | [Spend report CSV](view-usage-analytics-for-team-and-enterprise-plans.md); [Enterprise Analytics API](../04-API-Reference/Admin/platform-claude-com-http-beta-organization-analytics.md) on Enterprise |
| [Claude Console (API)](#claude-console) | [Console usage page](../04-API-Reference/Other/playground.md) | Workspace spend limits | [Console dashboard](../04-API-Reference/Other/playground.md), [Claude Code Analytics API](../04-API-Reference/Guides/build-with-claude-claude-code-analytics-api.md) |
| [Amazon Bedrock, Google Cloud’s Agent Platform, or Microsoft Foundry](#cloud-providers) | Your cloud billing console | Your cloud’s budget controls | [OpenTelemetry](../13-Enterprise-Admin/monitoring-usage.md) or an [LLM gateway](../13-Enterprise-Admin/llm-gateway.md) |
[OpenTelemetry export](../13-Enterprise-Admin/monitoring-usage.md) works on every setup and is the only option that streams per-user token and cost metrics into your own observability stack in near real time.
[](#report-spend-at-your-contracted-rates)
Report spend at your contracted rates
By default, Claude Code computes every cost figure it shows developers at list price, so if your organization pays contracted rates, the figures in `/usage`, the status line, and OpenTelemetry don’t match your bill. To make them match, set the [`modelPricing`](../02-Claude-Code-CLI/settings-reference.md#modelpricing) managed setting to your rates. The setting changes what Claude Code reports, not what Anthropic charges. Requires Claude Code v2.1.242 or later.
1
Take the rates from your contract
Enter the per-million-token rates from your contract. Claude Code doesn’t fetch them from the Claude Console, so update the setting when the contract changes.
2
Write the setting
Set `multiplier` below 1 for a flat discount or above 1 for a markup, list each model’s four per-token rates under `overrides`, or do both. A markup requires Claude Code v2.1.271 or later. The [`modelPricing` entry](../02-Claude-Code-CLI/settings-reference.md#modelpricing) has the shape and a paste-ready example.
3
Deploy it through managed settings
Deliver it as [managed settings](../13-Enterprise-Admin/managed-settings.md): server-managed settings, an MDM policy, `managed-settings.json`, or a [policy helper](../13-Enterprise-Admin/managed-settings.md#compute-the-policy-with-a-helper-program). Claude Code ignores the key in user, project, and local settings and in `--settings`.
To confirm the rates are in effect, run `/usage` in a session that has [received the managed settings](../13-Enterprise-Admin/managed-settings.md#read-the-source-in-%2Fstatus): the Session block’s `Total cost` line carries the note `at your organization's configured rates`. The figures are still estimates, not an invoice. The per-million-token prices in the `/model` picker stay at list price.
[](#claude-for-teams-and-enterprise)
Claude for Teams and Enterprise
On Claude for Teams and Enterprise plans, each member’s Claude Code usage draws from a per-seat allowance that resets on a rolling five-hour window and a weekly window. The allowance is shared with Claude chat and Cowork, and its size depends on the member’s [seat tier](https://support.claude.com/en/articles/11845131-use-claude-code-with-your-team-or-enterprise-plan) (Standard or Premium). Your controls live in the claude.ai admin console, not the Claude Console.
- **See spend**: the [spend report in org analytics](view-usage-analytics-for-team-and-enterprise-plans.md) shows estimated spend per user and per model, with CSV export, updated daily. The report covers usage-credit spend and appears once usage credits are turned on. Usage inside the seat allowance isn’t metered in dollars.
- **See adoption**: the [analytics dashboard](https://claude.ai/analytics/claude-code) shows daily active users, sessions, and contribution metrics, with CSV export of contribution data. See [track team usage with analytics](../13-Enterprise-Admin/analytics.md).
- **Cap spend**: the seat allowance is the default ceiling. To let members continue past it, turn on [usage credits](extra-usage-for-paid-claude-plans.md) and set spend limits at the organization, group, or individual member level.
- **Pull per-user numbers**: on the Enterprise plan, the [Enterprise Analytics API](../04-API-Reference/Admin/platform-claude-com-http-beta-organization-analytics.md) returns per-user usage and cost reports across Claude surfaces, including Claude Code. A Primary Owner creates a key with the `read:analytics` scope at [claude.ai/analytics/api-keys](https://claude.ai/analytics/api-keys). On the Teams plan, export the [spend report CSV](view-usage-analytics-for-team-and-enterprise-plans.md), which lists token usage and estimated spend per user and per model.
The [Claude Enterprise consumption guide](../13-Enterprise-Admin/claude-enterprise-consumption-guide.md) is the planning reference for admins. It explains how consumption differs across Claude chat, Claude Code, and Cowork, and gives per-user dollar starting points for budgeting. Budget more for a coding seat than a chat seat: each Claude Code turn carries file contents, tool calls, and multi-step reasoning, so one debugging session can consume more than a day of chat.
[](#claude-console)
Claude Console
API organizations manage Claude Code spend through [workspaces](../04-API-Reference/Guides/build-with-claude-workspaces.md). You can [set workspace spend limits](../04-API-Reference/Guides/build-with-claude-workspaces.md#workspace-limits) on total Claude Code spend and [view cost and usage reporting](../04-API-Reference/Guides/build-with-claude-workspaces.md#usage-and-cost-tracking) in the Console.
When you first authenticate Claude Code with your Claude Console account, a workspace called “Claude Code” is automatically created for you. This workspace provides centralized cost tracking and management for all Claude Code usage in your organization. You cannot create API keys for this workspace; it is exclusively for Claude Code authentication and usage.For organizations with custom rate limits, Claude Code traffic in this workspace counts toward your organization’s overall API rate limits. You can set a [workspace rate limit](../04-API-Reference/Endpoints/rate-limits.md#setting-lower-limits-for-workspaces) on this workspace’s Limits page in the Claude Console to cap Claude Code’s share and protect other production workloads.
For per-user reporting, the [Console dashboard](../04-API-Reference/Other/playground.md) shows spend and accepted lines per member, and the [Claude Code Analytics API](../04-API-Reference/Guides/build-with-claude-claude-code-analytics-api.md) returns the same daily per-user metrics programmatically with an [Admin API key](../04-API-Reference/Other/playground.md). See [analytics for API customers](../13-Enterprise-Admin/analytics.md#access-analytics-for-api-customers).
[](#rate-limit-recommendations)
Rate limit recommendations
When setting up Claude Code for teams, consider these Token Per Minute (TPM) and Request Per Minute (RPM) per-user recommendations based on your organization size:
| Team size | TPM per user | RPM per user |
|---------------|--------------|--------------|
| 1-5 users | 200k-300k | 5-7 |
| 5-20 users | 100k-150k | 2.5-3.5 |
| 20-50 users | 50k-75k | 1.25-1.75 |
| 50-100 users | 25k-35k | 0.62-0.87 |
| 100-500 users | 15k-20k | 0.37-0.47 |
| 500+ users | 10k-15k | 0.25-0.35 |
For example, if you have 200 users, you might request 20k TPM for each user, or 4 million total TPM (200\*20,000 = 4 million). The TPM per user decreases as team size grows because fewer users tend to use Claude Code concurrently in larger organizations. These rate limits apply at the organization level, not per individual user, which means individual users can temporarily consume more than their calculated share when others aren’t actively using the service.
If you anticipate scenarios with unusually high concurrent usage (such as live training sessions with large groups), you may need higher TPM allocations per user.
[](#cloud-providers)
Cloud providers
On Amazon Bedrock, Google Cloud’s Agent Platform, and Microsoft Foundry, Claude Code is billed per token to your cloud account, and spend controls live in your cloud provider’s billing console. Claude Code does not send metrics from your cloud back to Anthropic, so the [analytics dashboards](../13-Enterprise-Admin/analytics.md) and the Claude Code Analytics API do not cover this usage. For per-user cost attribution, you have three options:
- **OpenTelemetry**: [export metrics](../13-Enterprise-Admin/monitoring-usage.md) from each developer’s machine to your own observability stack. This gives you per-user token counts, costs, and tool activity regardless of provider.
- **A Claude apps gateway**: a self-hosted [Claude apps gateway](../13-Enterprise-Admin/claude-apps-gateway.md) provides per-user usage attribution, OTLP metrics with token counts, and [per-user spend limits](../13-Enterprise-Admin/claude-apps-gateway-spend-limits.md) on these providers.
- **An LLM gateway**: route all Claude Code traffic through a proxy that tracks spend per key. Several large enterprises reported using [LiteLLM](../13-Enterprise-Admin/llm-gateway.md), an open-source tool that [tracks spend by key](https://docs.litellm.ai/docs/proxy/virtual_keys#tracking-spend). This project is unaffiliated with Anthropic and has not been audited for security.
[](#when-a-developer-asks-about-a-limit)
When a developer asks about a limit
Developers usually bring limit questions to their admin, so it helps to know which ceiling they hit. These situations mean different things:
- **“You’ve hit your session limit” or “You’ve hit your weekly limit”**: a seat-based usage window on a subscription plan, shared across all models, so the developer can’t restore access by switching models with `/model`. The message shows when the window resets. After the model-specific “You’ve hit your Opus limit” or “You’ve hit your Sonnet limit” message, switching to a model outside that family with `/model` does keep the developer working. See [usage limit errors](../02-Claude-Code-CLI/errors.md#youve-hit-your-session-limit). What the developer can do in the meantime:
- Run `/usage-credits` to request usage beyond the allowance, if you have [usage credits](extra-usage-for-paid-claude-plans.md) turned on.
- On Claude Code v2.1.234 or later, [wait and continue the interrupted task automatically after the reset](../02-Claude-Code-CLI/interactive-mode.md#wait-for-a-usage-limit-to-reset); that section lists when Claude Code starts the wait on its own and when the developer picks it from `/rate-limit-options`. To control for your fleet whether Claude Code starts that wait on its own, set [`autoContinueAtUsageLimit`](../02-Claude-Code-CLI/settings-reference.md#autocontinueatusagelimit) in [managed settings](../02-Claude-Code-CLI/settings.md#settings-precedence).
- **“You’ve hit your individual spend limit”, “org’s monthly spend limit”, or “team’s shared budget”**: the developer’s request would be billed to usage credits, and those credits have reached a spend limit you set. To let the developer continue, go to [**Organization settings \> Usage**](https://claude.ai/admin-settings/usage) and increase the limit the message names. When the message also names a plan reset time, the developer can instead wait until then. See [the error reference](../02-Claude-Code-CLI/errors.md#youve-hit-your-monthly-spend-limit) for each variant.
- **A spend limit message from a [Claude apps gateway](../13-Enterprise-Admin/claude-apps-gateway.md)**: the developer passed a spend cap you set on your self-hosted gateway, and the gateway blocks their requests until the period resets or you raise the cap. See [gateway spend limits](../13-Enterprise-Admin/claude-apps-gateway-spend-limits.md) for caps, reset schedules, and the message the developer sees.
- **A context or auto-compact warning**: not a usage limit. The conversation has grown close to the session’s [auto-compact window](../02-Claude-Code-CLI/model-config.md#set-the-auto-compact-window), the threshold where Claude Code summarizes older history to free space. Point the developer at [reduce token usage](#reduce-token-usage).
- **Unexpectedly high spend on an API or cloud-provider plan**: usually traces back to long sessions that were never cleared or to Opus left as the default model. The highest-impact habits to share are clearing between unrelated tasks and matching the model to the job, both covered in [reduce token usage](#reduce-token-usage).
[](#agent-team-token-costs)
Agent team token costs
[Agent teams](../09-Agents-Patterns/agent-teams.md) spawn multiple Claude Code instances, each with its own context window. Token usage scales with the number of active teammates and how long each one runs. To keep agent team costs manageable:
- Use Sonnet for teammates. It balances capability and cost for coordination tasks.
- Keep teams small. Each teammate runs its own context window, so token usage is roughly proportional to team size.
- Keep spawn prompts focused. Teammates load CLAUDE.md, MCP servers, and skills automatically, but everything in the spawn prompt adds to their context from the start.
- Shut down teammates when their work is done. Each active teammate continues consuming tokens until it exits or the session ends.
- Agent teams are disabled by default. Set `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` in your [settings.json](../02-Claude-Code-CLI/settings.md) or environment to enable them. See [enable agent teams](../09-Agents-Patterns/agent-teams.md#enable-agent-teams).
[](#reduce-token-usage)
Reduce token usage
Token costs scale with context size: the more context Claude processes, the more tokens you use. Claude Code automatically optimizes costs through [prompt caching](../02-Claude-Code-CLI/prompt-caching.md), which reduces costs for repeated content like system prompts, and auto-compaction, which summarizes conversation history when approaching context limits. The following strategies help you keep context small and reduce per-message costs.
[](#manage-context-proactively)
Manage context proactively
Use `/usage` to check your current token usage, or [configure your status line](../02-Claude-Code-CLI/statusline.md#context-window-usage) to display it continuously.
- **Clear between tasks**: Use `/clear` to start fresh when switching to unrelated work. Stale context wastes tokens on every subsequent message. Use `/rename` before clearing so you can find the session later, then `/resume` to return to it.
- **Add custom compaction instructions**: `/compact Focus on code samples and API usage` tells Claude what to preserve during summarization.
You can also customize compaction behavior in your CLAUDE.md file at the root of your project:
```python
# Compact instructions
When you are using compact, please focus on test output and code changes
```
[](#choose-the-right-model)
Choose the right model
Sonnet handles most coding tasks well and costs less than Opus. Reserve Opus for complex architectural decisions or multi-step reasoning. Use `/model` to switch models mid-session, or set a default in `/config`. A switch to Opus also applies to the [subagents that inherit your session’s model](../02-Claude-Code-CLI/model-config.md#setting-your-model). For simple subagent tasks, specify `model: haiku` in your [subagent configuration](../09-Agents-Patterns/sub-agents.md#choose-a-model).
[](#reduce-mcp-server-overhead)
Reduce MCP server overhead
MCP tool definitions are [deferred by default](../06-MCP-Tools/General/mcp.md#scale-with-mcp-tool-search), so only tool names and server instructions enter context until Claude uses a specific tool. Run `/context` to see what’s consuming space.
- **Prefer CLI tools when available**: Tools like `gh`, `aws`, `gcloud`, and `sentry-cli` are still more context-efficient than MCP servers because they don’t add any per-tool listing. Claude can run CLI commands directly.
- **Disable unused servers**: Run `/mcp` to see configured servers and disable any you’re not actively using.
[](#install-code-intelligence-plugins-for-typed-languages)
Install code intelligence plugins for typed languages
[Code intelligence plugins](../08-Plugins-Skills/plugins-code-intelligence.md) give Claude precise symbol navigation instead of text-based search, reducing unnecessary file reads when exploring unfamiliar code. A single “go to definition” call replaces what might otherwise be a grep followed by reading multiple candidate files. Installed language servers also report type errors automatically after edits, so Claude catches mistakes without running a compiler.
[](#offload-processing-to-hooks-and-skills)
Offload processing to hooks and skills
Custom [hooks](../07-Hooks/hooks.md) can preprocess data before Claude sees it. Instead of Claude reading a 10,000-line log file to find errors, a hook can grep for `ERROR` and return only matching lines, reducing context from tens of thousands of tokens to hundreds. A [skill](../08-Plugins-Skills/skills.md) can give Claude domain knowledge so it doesn’t have to explore. For example, a “codebase-overview” skill could describe your project’s architecture, key directories, and naming conventions. When Claude invokes the skill, it gets this context immediately instead of spending tokens reading multiple files to understand the structure. For example, this PreToolUse hook filters test output to show only failures:
- settings.json
- filter-test-output.sh
Add this to your [settings.json](../02-Claude-Code-CLI/settings.md#where-settings-live) to run the hook before every Bash command:
```python
{
"hooks": {
"PreToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "~/.claude/hooks/filter-test-output.sh"
}
]
}
]
}
}
```
The hook calls this script. Create the folder with `mkdir -p ~/.claude/hooks`, save the script below as `~/.claude/hooks/filter-test-output.sh`, and make it executable with `chmod +x ~/.claude/hooks/filter-test-output.sh`. It checks if the command is a test runner and modifies it to show only failures:
```python
#!/bin/bash
input=$(cat)
cmd=$(echo "$input" | jq -r '.tool_input.command')
# If running tests, filter to show only failures
pattern='^(npm test|pytest|go test)( [^;&|<>`$#\\[:cntrl:]]*)?$'
if [[ "$cmd" =~ $pattern ]]; then
filtered_cmd="$cmd 2>&1 | grep -A 5 -E '(FAIL|ERROR|error:)' | head -100"
echo "$input" | jq --arg filtered "$filtered_cmd" \
'{hookSpecificOutput: {hookEventName: "PreToolUse", updatedInput: (.tool_input + {command: $filtered})}}'
else
echo "{}"
fi
```
To verify the setup, run `/hooks` and check that the hook appears under PreToolUse. You can also start Claude Code with `claude --debug-file ./claude-debug.txt` and ask Claude to run `npm test`. When the hook rewrites the command, that log file contains a `modified tool input keys` line listing `command` and the other Bash input fields.
[](#move-instructions-from-claude-md-to-skills)
Move instructions from CLAUDE.md to skills
Your [CLAUDE.md](../02-Claude-Code-CLI/memory.md) file is loaded into context at session start. If it contains detailed instructions for specific workflows (like PR reviews or database migrations), those tokens are present even when you’re doing unrelated work. [Skills](../08-Plugins-Skills/skills.md) load on-demand only when invoked, so moving specialized instructions into skills keeps your base context smaller. Aim to keep CLAUDE.md under 200 lines by including only essentials.
[](#adjust-extended-thinking)
Adjust extended thinking
Extended thinking is enabled by default because it significantly improves performance on complex planning and reasoning tasks. Thinking tokens are billed as output tokens, and the default budget can be tens of thousands of tokens per request depending on the model. For simpler tasks where deep reasoning isn’t needed, you can reduce costs by lowering the [effort level](../02-Claude-Code-CLI/model-config.md#adjust-effort-level) with `/effort` or in `/model`, or by disabling thinking in `/config`. You can’t turn off thinking on Opus 5.5, Sonnet 5.5, Haiku 5.5, or the Fable models, which always use extended thinking. On models with a [fixed thinking budget](../02-Claude-Code-CLI/model-config.md#adaptive-reasoning-and-fixed-thinking-budgets), you can also lower the budget by setting the `MAX_THINKING_TOKENS` [environment variable](../02-Claude-Code-CLI/env-vars.md), for example `MAX_THINKING_TOKENS=8000`. Adaptive-reasoning models ignore nonzero budgets, so use effort levels there instead.
[](#delegate-verbose-operations-to-subagents)
Delegate verbose operations to subagents
Running tests, fetching documentation, or processing log files can consume significant context. Delegate these to [subagents](../09-Agents-Patterns/sub-agents.md#isolate-high-volume-operations) so the verbose output stays in the subagent’s context while only a summary returns to your main conversation. The subagent’s own requests still draw on your usage. To spend less on them, [choose a smaller model for a subagent](../09-Agents-Patterns/sub-agents.md#choose-a-model) or [run every subagent on one model](../09-Agents-Patterns/sub-agents.md#run-every-subagent-on-one-model).
[](#manage-agent-team-costs)
Manage agent team costs
Agent teams use approximately 7x more tokens than standard sessions when teammates run in plan mode, because each teammate maintains its own context window and runs as a separate Claude instance. Keep team tasks small and self-contained to limit per-teammate token usage. See [agent teams](../09-Agents-Patterns/agent-teams.md) for details.
[](#write-specific-prompts)
Write specific prompts
Vague requests like “improve this codebase” trigger broad scanning. Specific requests like “add input validation to the login function in auth.ts” let Claude work efficiently with minimal file reads.
[](#work-efficiently-on-complex-tasks)
Work efficiently on complex tasks
For longer or more complex work, these habits help avoid wasted tokens from going down the wrong path:
- **Use plan mode for complex tasks**: Press Shift+Tab to cycle to [plan mode](../02-Claude-Code-CLI/permission-modes.md#analyze-before-you-edit-with-plan-mode) before implementation. Claude explores the codebase and proposes an approach for your approval, preventing expensive re-work when the initial direction is wrong.
- **Course-correct early**: If Claude starts heading the wrong direction, press Escape to stop immediately. Use `/rewind` or double-tap Escape to restore conversation and code to a previous checkpoint.
- **Give verification targets**: Include test cases, paste screenshots, or define expected output in your prompt. When Claude can verify its own work, it catches issues before you need to request fixes.
- **Test incrementally**: Write one file, test it, then continue. This catches issues early.
[](#background-token-usage)
Background token usage
Claude Code uses tokens for some background functionality even when idle:
- **Conversation summarization**: Background jobs that summarize previous conversations for the `claude --resume` feature
- **Command processing**: Some commands like `/usage` may generate requests to check status
These background processes consume a small amount of tokens (typically under \$0.04 per session) even without active interaction. When prompt suggestions are on, Claude Code also sends a short request to the model your session is using after Claude responds, to [suggest your next prompt](../02-Claude-Code-CLI/interactive-mode.md#prompt-suggestions). That request reuses the conversation’s prompt cache, so it is mostly cache reads plus a few output tokens. Claude Code [skips it while your account is close to or at its usage limit](../02-Claude-Code-CLI/interactive-mode.md#when-claude-code-skips-suggestions). To stop these requests, [turn prompt suggestions off](../02-Claude-Code-CLI/interactive-mode.md#turn-prompt-suggestions-off).
[](#why-usage-climbs-in-a-long-session)
Why usage climbs in a long session
A session that has been open for hours can use far more of your plan limits than your activity suggests, usually for one of these reasons:
- **Long context**: Claude Code sends your full conversation with every request, and each time Claude uses tools it sends another request carrying that batch of tool results. With [prompt caching](../02-Claude-Code-CLI/prompt-caching.md), Claude Code re-reads that history at the [cached token rate](about-claude-pricing.md), so a one-line question in a session that has been open all day still draws usage for the whole conversation. See [Manage context proactively](#manage-context-proactively) for ways to keep your context small
- **Cache misses**: your first message after a break longer than the [cache lifetime](../02-Claude-Code-CLI/prompt-caching.md#cache-lifetime) misses the cache and reprocesses your full context. See [which lifetime your requests get](../02-Claude-Code-CLI/prompt-caching.md#which-ttl-each-request-gets) and [the controls for setting it](../02-Claude-Code-CLI/prompt-caching.md#choose-the-ttl-yourself)
- **Scheduled tasks**: a [session-scoped scheduled task](../02-Claude-Code-CLI/scheduled-tasks.md) fires on its interval even while the session is idle, sending your full context each time
- **Cross-session messages**: Claude Code delivers a [message from another of your sessions](../02-Claude-Code-CLI/cross-session-messaging.md) as a new turn when this session sits idle, sending your full context each time. To hold inbound messages instead of delivering them, set [`crossSessionInbound`](../02-Claude-Code-CLI/settings-reference.md#crosssessioninbound) to `hold`
- **Goal check-ins**: while background work keeps an active [goal](../02-Claude-Code-CLI/goal.md) waiting, Claude Code [asks Claude to check on that work](../02-Claude-Code-CLI/goal.md#background-work-defers-evaluation) even when the session sits idle, starting a new turn that sends your full context. Claude Code starts at most three idle check-ins per goal between your prompts. Before v2.1.246, idle check-ins were uncapped. To turn check-ins off, set [`CLAUDE_CODE_GOAL_CHECKIN_MINUTES`](../02-Claude-Code-CLI/env-vars.md) to `0`. Idle check-ins require Claude Code v2.1.236 or later
- **Subagents and workflows**: every subagent, and every agent a [dynamic workflow](../02-Claude-Code-CLI/workflows.md#cost) spawns, sends its own requests on top of the main conversation’s. The [attribution breakdown](#plan-usage-breakdown) shows the subagent share
- **Agent teammates**: each active [teammate](#agent-team-token-costs) keeps consuming tokens until it exits
- **Compaction**: `/compact` reads the conversation it summarizes, so [compacting a large context](../02-Claude-Code-CLI/prompt-caching.md#compacting-the-conversation) is itself a large request. When you want a fresh start instead of continuity, `/clear` costs nothing
On a Pro, Max, Team, or Enterprise plan, the [`/usage` breakdown](#plan-usage-breakdown) recommends a change for behaviors behind 10% or more of your recent usage, such as long context or cache misses.
[](#understanding-changes-in-claude-code-behavior)
Understanding changes in Claude Code behavior
Claude Code regularly receives updates that may change how features work, including cost reporting. Run `claude --version` to check your current version. For billing questions about your specific account, contact Anthropic support through the in-product messenger:
- **Subscription plans** (Pro, Max, Team, Enterprise): sign in at [claude.ai](https://claude.ai), click your initials in the lower left, and select **Get help**
- **Console (API) billing**: sign in at [platform.claude.com](../04-API-Reference/Other/playground.md), click your initials, and select **Get help**
See [How to get support](../15-Claude-AI-Features/how-to-get-support.md) for the full flow, including who can reach a human agent on each plan.
---
## Use Claude Cowork on Team and Enterprise plans | Claude Help Center
Source: https://support.claude.com/en/articles/13455879-cowork-for-team-and-enterprise-plans
Path: 17-Billing-Plans/cowork-for-team-and-enterprise-plans.md
# Use Claude Cowork on Team and Enterprise plans
Updated today
**Note:** Claude Cowork and chat are now one Claude. Ask for what you need, and Claude decides whether that’s a quick answer or a task. This is rolling out gradually to Pro and Max plans, and it’s in beta for Enterprise plans, where an admin turns it on as **Chat and Cowork unified (beta)**. Team organizations, and Enterprise organizations that haven’t turned it on, keep chat and Claude Cowork as they are today, so everything in this article still applies. If you’re an Enterprise admin, learn more in **[Set up and manage the new unified Claude experience for your Enterprise organization](../13-Enterprise-Admin/set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization.md)**, or read our **[blog post](https://claude.com/blog/cowork-is-now-claude)**.
This article explains important limitations and considerations for Team and Enterprise organizations using Claude Cowork.
## Availability
Claude Cowork is available on paid plans (Pro, Max, Team, Enterprise). Availability varies by surface:
- **Claude Desktop for macOS** — Available on all paid plans. **[Click here](https://claude.ai/api/desktop/darwin/universal/dmg/latest/redirect)** to download.
- **Claude Desktop for Windows** — Available on all paid plans. Cowork requires the latest version of Claude for Windows. Download or update at **[claude.com/download](https://claude.com/download)**.
- **Web (beta)**, at claude.ai — Available on Pro, Max, and Team plans. On Enterprise plans, available where an admin has enabled it.
- **Claude Mobile** **(beta)** — Available on Pro, Max, and Team plans, in the latest version of Claude for iOS and Claude for Android. On Enterprise plans, available where an admin has enabled it.
- **Claude in Chrome side panel** — Available on Max and Team plans, and rolling out to Pro plans. On Enterprise plans, available where an admin has enabled it. For more information, see **[Get started with Claude in Chrome](../21-Account-Support/introduction-to-prompt-design.md)**.
On web and mobile, Claude Cowork sessions run in Anthropic's cloud.
------------------------------------------------------------------------
## Where Cowork runs
During the beta, Cowork sessions can run in two places:
- **Sessions in the cloud (beta):** Running Cowork in the cloud lets members run tasks on Anthropic's infrastructure instead of their own machines. This means work continues across desktop, web, and mobile and scheduled tasks run when the laptop closes and no device is online.
- **Local sessions:** Claude's work runs on the user’s computer, with code in an isolated virtual machine.
## Admin controls
Claude Cowork is on by default, but organization owners can manually disable it. In organizations that have enabled HIPAA, Cowork is off by default. An Owner can turn on Cowork in **Organization settings \> Cowork**.
### Enable or disable Cowork
1. Log in to your Team or Enterprise organization as an Owner or Primary Owner.
2. Navigate to **[Organization settings \> Cowork](https://claude.ai/admin-settings/cowork)**.
3. Locate the **Enable for your organization** toggle under **Cowork**.
4. Toggle off to disable Cowork for all users in your organization.
This toggle controls whether Cowork is available at all. Whether sessions can run in the cloud is a separate control.
**Note:** This is an organization-wide setting. On Enterprise plans, you can use groups and custom roles to enable Cowork for specific teams. See **[Access controls](#h_8465b1b558)** below.
### Enable or disable sessions in the cloud
For Team and Enterprise plans, there's a separate organization-wide toggle in **[Organization settings \> Cowork](https://claude.ai/admin-settings/cowork)** under "Run Cowork in the cloud."
- **Team plans:** on by default. An owner can turn it off any time from the "Run Cowork in the cloud" toggle.
- **Enterprise plans:** off by default. An owner turns on "Run Cowork in the cloud," then grants the Cowork in the cloud capability to a group with custom roles. See **[Manage custom roles on Enterprise plans](manage-custom-roles-on-enterprise-plans.md)**. With the HIPAA configuration applied to Claude Code (local mode) and Cowork (local mode), Cowork in the cloud isn't available, and no setting turns it on.
### Enable or disable the built-in browser
Claude can use the web in Cowork in two ways: a browser built into the Claude Desktop app, or your users' own Chrome browser through the Claude in Chrome extension. You can enable one, both, or neither.
- **Built-in browser:** Controlled from **[Organization settings \> Cowork](https://claude.ai/admin-settings/cowork)**. On Team plans, it's on by default as it rolls out this week. Team owners can turn it off anytime. On Enterprise plans, it's off by default at launch and turns on by default starting September 10, 2026, unless you've turned it off. In organizations that have enabled HIPAA, the built-in browser stays off until an Owner turns it on in **Organization settings \> Cowork**. With the **[HIPAA configuration applied to Claude Code (local mode) and Cowork (local mode)](https://support.claude.com/en/articles/17318731)**, the built-in browser isn't available, and no setting turns it on. When it's off, users can't open the built-in browser and Claude can't use it.
- **Claude in Chrome:** Controlled from **[Organization settings \> Claude in Chrome](https://claude.ai/admin-settings/browser-extension)**, and users' browsers still need the extension deployed or installed. See **[Claude in Chrome admin controls](https://support.claude.com/en/articles/13065128)**.
Both run the same safety layers: a blocklist for high-risk sites and safety checks on every action. The built-in browser needs the Claude Desktop app open and online; Claude in Chrome needs the extension installed in the user's browser. Browser traffic comes from the user's machine, where the desktop app runs. To site operators it looks like traffic from that device, even when the session is steered from web or mobile.
Learn more in **[Use the built-in browser in Claude Cowork](https://support.claude.com/en/articles/16607400)**.
### Auto mode availability
Two organization settings in **[Organization settings \> Capabilities](https://claude.ai/admin-settings/capabilities)** control "Automatically approve" mode in Cowork:
- **Allow "Automatically approve" mode** controls whether members can use the mode. This setting is on by default, so the mode is available to your members unless you turn it off. When it's off, "Automatically approve" doesn't appear in your members' mode selector.
- **Start new tasks in "Automatically approve" mode** controls whether new Cowork tasks start in that mode. It’s on by default on Pro, Max, and Team plans, and off by default on Enterprise plans. Turn it off to keep "Manually approve" as the default.
Members can switch modes within any session.
Learn more about how the modes differ in **[Get started with Claude Cowork](https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork#h_e1353133dd)**.
### Connector tool approvals
The organization setting **Allow "Always allow" for connector tools** in **[Organization settings \> Cowork](https://claude.ai/admin-settings/cowork)** (under **Permissions**) controls whether members can skip per-task approval for write-capable connector tools in Cowork. This setting is off by default.
When the setting is off:
- The "Allow for all tasks" option appears grayed out in Cowork's approval dialog, even when your organization-wide tool policies allow these tools.
- Previously saved always-allow preferences for write tools aren't honored. Members approve these tools per task until the setting is turned on.
Read-only tools are exempt only when the connector annotates them as read-only. Most custom connectors don't annotate their tools, so every tool on those connectors is gated.
On Enterprise plans, this setting works alongside custom role grants, and the most restrictive layer wins. Role grants can't override it. For the full layering model, see **[Manage custom roles on Enterprise plans](manage-custom-roles-on-enterprise-plans.md#h_979e558d00)**.
### Plugins
Plugins are included with Cowork and controlled by the same admin toggle—there's no separate setting to manage plugin access within Cowork.
For details on what members can do with plugins, see **[Use plugins in Claude](https://support.claude.com/en/articles/13837440-use-plugins-in-cowork)**.
------------------------------------------------------------------------
## Projects
Projects in Cowork let users organize tasks into dedicated workspaces with their own files, links, instructions, and memory. Projects are available to all Cowork users. There are no separate admin controls for projects, so owners cannot restrict project creation at the organization level at this time.
Projects are available wherever members use Cowork. Projects tied to a local folder support Cowork sessions on desktop only. For local sessions, project data is stored on the user's computer; for sessions in the cloud, projects are saved with the member's Claude account. For full details, see **[Organize your tasks with projects in Cowork](../15-Claude-AI-Features/organize-your-tasks-with-projects-in-cowork.md).**
------------------------------------------------------------------------
## Manage plugins for your organization
Owners can create plugin marketplaces to distribute curated plugins across their organization. This gives you control over which plugins users see and use in chat, Cowork, and Claude Code (for users who sign in to Claude Code with their Claude account).
- **Installed by default** — Automatically added for everyone in your organization. Members can turn it off if they choose.
- **Available to install** — Appears on the **Discover** tab for members to add on their own.
- **Required** — Automatically installed for all members. Members can’t turn it off or remove it.
- **Not available** — Hidden from members. Useful for staging or deprecating plugins.
On Enterprise plans, admins can also override these preferences for specific groups—for example, auto-installing a plugin for one team while hiding it from everyone else. For details, see **[Manage plugins for your organization](https://support.claude.com/en/articles/13837433-manage-cowork-plugins-for-your-organization)**.
------------------------------------------------------------------------
## Company branding
Cowork now surfaces your organization's branding, including a redesigned home screen tailored to your team. Team and Enterprise owners can configure branding within **Organization settings**.
------------------------------------------------------------------------
## Security, compliance, and monitoring
**Note:** For the most up-to-date and extensive guide see **[Cowork security best practices](https://trust.anthropic.com/resources?s=uukz8hyx7jmdmo80lys36s&name=claude-cowork-security-best-practices)**.
**Important:** On a HIPAA-ready Enterprise plan, after the Primary Owner applies the HIPAA configuration to Claude Code (local mode) and Cowork (local mode), your Business Associate Agreement (BAA) covers Cowork sessions in Claude Desktop. Without that configuration, Cowork is available but not covered under your BAA. With that configuration applied, Cowork in the cloud isn't available. See **[Use Claude Code (local mode) and Cowork (local mode) on a HIPAA-ready Enterprise plan](https://support.claude.com/en/articles/17318731)**.
### Monitoring
**Compliance API**
Cowork sessions via Claude, Claude Desktop, and Claude Mobile are captured in the Compliance API. Learn more about **[retrieving remote sessions in the Compliance API](../04-API-Reference/Other/manage-claude-compliance-content-data.md)**.
**Local conversation storage**
For local sessions, Cowork stores conversation history on users' computers. This data is not subject to Anthropic's standard **[data retention policies](https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data)**, and admins cannot centrally manage or delete it. Claude Enterprise admins can retrieve this content through the Compliance API. Deletion endpoints for local sessions aren't available yet. In organizations that have enabled HIPAA and turned on the Compliance API, Anthropic captures Cowork sessions that run on members' computers, so that your organization can retrieve them through the Compliance API. The Compliance API returns sessions from the most recent 30 days. If your organization's retention period is shorter than 30 days, the Compliance API returns sessions from that period.
For sessions in the cloud, sessions and files are saved to the member's Claude account.
**OpenTelemetry**
Team and Enterprise owners can stream Cowork events to your SIEM and observability tools through OpenTelemetry. This gives security teams visibility into tool calls, file access, human approval decisions, and more. It doesn't replace audit logging for compliance purposes.
For setup, supported events, and security considerations, see **[Monitor Cowork activity with OpenTelemetry](../15-Claude-AI-Features/monitor-cowork-activity-with-opentelemetry.md)**. You can also refer to **[Monitoring](https://claude.com/docs/cowork/monitoring)** in our Claude Docs.
### Prompt injection risks
Cowork has unique risks due to its agentic nature and internet access. We've implemented safety measures including model training and content classifiers, but the risk of prompt injection attacks is non-zero.
Users should:
- Avoid granting access to files with sensitive information
- Monitor Claude for suspicious actions
- Limit browser and web access to trusted sources
- Report suspicious behavior immediately
### Network access
Cowork respects your organization's current network egress permissions. Before enabling Cowork, review your network access settings in **[Organization settings \> Capabilities](https://claude.ai/admin-settings/capabilities)** under **Code execution**.
Network settings are applied when a new Cowork session is created. If you change the network access mode or add domains to the allowlist during an active conversation, those changes won't take effect in that session. Start a new conversation for the updated settings to apply.
Network egress permissions don't apply to the web fetch or **[web search](https://support.claude.com/en/articles/10684626-enabling-and-using-web-search)** tools, or to MCPs, including Claude in Chrome. Web fetch runs server-side and is limited to search results and URLs you've shared. Team and Enterprise owners can turn off web search for Cowork and Chat in **[Organization settings \> Capabilities](https://claude.ai/admin-settings/capabilities)**, and Claude in Chrome in **[Organization settings \> Claude in Chrome](https://claude.ai/admin-settings/browser-extension)**.
---
## Manage usage credits for paid Claude plans | Claude Help Center
Source: https://support.claude.com/en/articles/12429409-extra-usage-for-paid-claude-plans
Path: 17-Billing-Plans/extra-usage-for-paid-claude-plans.md
# Manage usage credits for paid Claude plans
This article explains how usage credits work on your paid Claude plan (Pro, Max 5x, or Max 20x), allowing you to continue working with Claude after reaching your plan's usage limits by switching to pay-as-you-go pricing.
## What are usage credits?
Usage credits allow individuals subscribed to paid Claude plans (Pro, Max 5x, and Max 20x) to continue using Claude after reaching their included usage limits. Paid plans have a session limit that resets every five hours and a weekly limit. Max plans also have a separate weekly limit for Fable. Instead of being blocked when you reach one of your plan's limits, you can switch to consumption-based pricing at standard API rates and continue your work without interruption.
Usage credits are separate from the monthly API credits included with Max plans. Monthly API credits don’t apply to usage credits in Claude, Claude Code, or Claude Cowork. Learn more about **[monthly API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)**.
**Note:** If you subscribed through one of the Claude mobile apps, you can only enable usage credits on the web version of Claude. You will need to add your payment method before enabling and purchasing usage credits on the web.
------------------------------------------------------------------------
## How usage credits work
When you fully use your plan’s included usage limits (your five-hour session limit, your weekly limit, or your Fable weekly limit on Max plans) with usage credits enabled:
- Your requests switch to pay-as-you-go pricing on usage credits and keep working.
- You may briefly still see the notification that you’re approaching your usage limit. Once your next request goes through on usage credits, it changes to “Now using credits.” You haven’t been cut off; your work continues.
- Your subsequent usage will be billed at standard API pricing rates.
- Your usage continues until you reach your monthly spend limit, or your balance runs out with auto-reload off.
- Your session limit resets every five hours and your weekly limits reset once a week, as usual.
**Note:** Usage credits are charged separately from your paid Claude subscription and appear as additional charges on your bill.
------------------------------------------------------------------------
## Enable usage credits
To enable usage credits on your paid Claude plan:
1. Navigate to [**Settings \> Usage**](https://claude.ai/settings/usage) in your Claude account.
2. Locate the **Usage credits** section.
3. Click "Enable" to turn on usage credits.
4. Set up your payment method if not already configured.
5. Configure your spending preferences.
6. Click “Adjust limit” to control costs with a monthly spend limit. You can also select “Set to unlimited” if you prefer no spending restrictions.
7. You’ll then need to prepay to cover usage beyond your plan limits. Click “Add funds,” enter the amount you want to purchase in the modal, then click “Purchase.”
8. You can also enable auto-reload to automatically make a purchase when your balance falls below a threshold you set:
------------------------------------------------------------------------
## Set spend limits
Control your usage credit spending with:
- **Monthly spending cap:** Set a maximum amount you're willing to spend on usage credits each month.
- **Auto-reload settings:** Automatically add funds when your balance drops below a threshold.
- **Usage alerts:** Receive notifications when approaching your spend limits.
------------------------------------------------------------------------
## Usage credit pricing
Usage credits are billed at standard API rates; see our **[pricing page](pricing.md#api)** for details.
Price and plans are subject to change at Anthropic's discretion.
------------------------------------------------------------------------
## Manage your usage credits
### Monitor usage and costs
Track your usage credits through:
- **Usage dashboard:** View real-time consumption in **[Settings \> Usage](https://claude.ai/settings/usage)**.
- **Current spending:** Monitor your month-to-date usage credit costs.
- **Usage history:** Review past consumption patterns to optimize future usage.
## Tips for cost-effective usage
To manage usage credit costs while maintaining productivity:
- **Choose efficient models:** Use our most efficient Haiku model, or the most recent Sonnet model for most tasks. These provide excellent performance at lower token costs than Opus models.
- **Use your plan’s included usage first:** Plan intensive work sessions around your five-hour usage windows.
- **Start new conversations:** Begin fresh chats for new topics to minimize the size of your context window.
- **Use projects effectively:** Store frequently referenced documents in project knowledge instead of re-uploading.
- **Set appropriate limits:** Start with conservative spending caps and adjust based on your needs.
------------------------------------------------------------------------
## How usage credits work with other features
### Claude Code
Usage credits apply to both Claude conversations and Claude Code terminal usage. Your combined usage across both interfaces counts toward your limits.
### Research mode
When using Research mode, usage credits apply once you exceed your plan's included limits. Research sessions may consume tokens more quickly due to multiple searches and comprehensive analysis.
### Projects and files
Documents stored in project files count toward your context when used in conversations. Usage credits apply to all tokens processed, including project content.
------------------------------------------------------------------------
## Frequently asked questions
### Can I disable usage credits after enabling them?
Yes, you can disable usage credits at any time through **[Settings \> Usage](https://claude.ai/settings/usage)**. Once disabled, you'll only have access to your plan's included usage.
### How quickly do my regular usage limits reset?
Paid plans include two usage limits: a session limit that resets every five hours, and a weekly limit that resets once a week. Max plans also have a separate weekly limit for Fable that resets once a week. Usage credits don’t affect the reset timing of any of these limits.
### Can I keep using Claude after I reach my weekly limit?
Yes. With usage credits enabled, once one of your included limits is fully used (your five-hour session limit or one of your weekly limits), your requests switch to pay-as-you-go pricing on usage credits and keep working. Your usage continues until you reach your monthly spend limit or your usage credit balance runs out with auto-reload off.
### I subscribed to a paid Claude plan on the App or Play store; how can I access usage credits?
If you purchased your paid plan through one of the Claude mobile apps, usage credits are only available if you enable and purchase them on the Claude web app. You will not be able to set up usage credits on the mobile app.
### Can I track usage credits separately from my included usage?
Yes, the usage dashboard clearly distinguishes between your included plan usage limits and any usage credit consumption.
### Will I get a warning before switching to usage credits?
Yes. You’ll see a notification when you’re approaching your session limit or one of your weekly limits. That notification may still be showing at the moment your usage switches to usage credits, so it can look like you’ve been cut off. If usage credits are enabled and you have funds available, your next request goes through on usage credits and the notification changes to “Now using credits.”
### Do usage credits expire?
In most cases, usage credits do not expire. However, in certain jurisdictions such as Japan, usage credits expire six months after purchase starting September 10, 2026. You'll receive an email notification seven days before your credits expire, and you can view expiration dates on the Usage page in Settings.
---
## Manage usage credits for Team and seat-based Enterprise plans | Claude Help Center
Source: https://support.claude.com/en/articles/12005970-extra-usage-for-team-and-enterprise-plans
Path: 17-Billing-Plans/extra-usage-for-team-and-enterprise-plans.md
# Manage usage credits for Team and seat-based Enterprise plans
September 4, 2026
This article explains how Team and seat-based Enterprise plan Owners and Primary Owners can purchase usage credits, allowing members to continue using Claude, Claude Cowork, and Claude Code after reaching usage limits for their assigned seat.
## What are usage credits?
Usage credits allow Team and seat-based Enterprise plan members on Standard and Premium seats to continue working with Claude, Cowork, and Claude Code after reaching their included usage limits. Instead of being blocked upon hitting limits, members can keep working without interruption.
**Important:** Usage credits don't apply to current usage-based Enterprise plans. On those plans, there's no included usage allowance to run out of—all usage is billed at API rates from the first token. For details on how usage and spend limits work on usage-based plans, see **[How am I billed for my Enterprise plan?](how-am-i-billed-for-my-enterprise-plan.md)**
------------------------------------------------------------------------
## How usage credits work
After an organization Owner or Primary Owner configures your account for usage credits, you'll start using them as soon as you reach your seat's usage limit. Your subsequent usage will be billed at standard API pricing rates as you continue working.
**For Team plans:** Owners can pre-purchase usage credits that they can control using spend limits.
**For seat-based Enterprise plans:** Usage credits are billed at the end of each month based on your actual usage during the billing period.
------------------------------------------------------------------------
## Enable usage credits
### For Team owners
1. Log in to your Team organization as an Owner or Primary Owner.
2. Navigate to **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**.
3. Click "Enable" in **Usage credits** to turn this on for your organization.
4. You'll be prompted to pay for usage credits.
5. Next, you'll see the option to enable auto-reload; choose "Reload when balance reaches" and enter the amount to reload.
6. Set a monthly spend limit to apply organization-wide.
7. Enable usage credits for specific users or the entire organization.
### For seat-based Enterprise owners
1. Log in to your seat-based Enterprise organization as an Owner or Primary Owner.
2. Navigate to **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**.
3. Click "Enable" in **Usage credits** to turn this on for your organization.
4. You'll be prompted to set monthly spend limits for the organization as a whole, by seat tier, or for individual members.
### How can members switch to usage credits once they're enabled?
Once an organization owner has enabled usage credits:
1. Continue using Claude or Claude Code normally.
2. When you reach your usage limit and choose to continue working, your usage credit consumption will be tracked and billed according to your plan type.
------------------------------------------------------------------------
## Organization-wide spend limits
Owners and Primary Owners of Team and seat-based Enterprise plans can set organization-wide spend limits to ensure predictable costs while providing flexibility for critical work.
**Note:** If you're on an Enterprise plan, you can also set spend limits at the group level. See **[Manage groups and group spend limits on Enterprise plans](manage-groups-and-group-spend-limits-on-enterprise-plans.md)**.
### Spend limits
After navigating to **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)** and enabling this feature, Owners can set a monthly spend limit on the entire organization's usage credits. Setting a limit here controls total usage credit spend across your whole organization, regardless of individual or seat limits.
The **Usage and spend limits** section will show the current limit (if any) or **Unlimited**. Clicking on "Adjust limit" opens a modal where you can either input an amount and click "Set spend limit," or click "Set to unlimited" to remove the organization-wide monthly spend limit.
Changes to your organization’s overall spend limit go into effect immediately.
### Seat spend limits for seat-based Enterprise plans
Owners and Primary Owners on **seat-based Enterprise plans only** can set spend limits that apply to all users within a specific seat tier.
Select the "By group" tab to see **Standard seats** and **Premium seats** groups. Click the "..." icon next to the current limit, then "Edit limit." This opens a modal where you can either select "Set dollar amount" and input an amount, or click "Unlimited" to remove the limit for that seat type. Click "Set limit" to save your changes.
------------------------------------------------------------------------
## User-level spend limits
Owners and Primary Owners can also set individual monthly spend limits for each member by finding **Spend limits by user** and clicking the "..." button next to the user, then "Edit limit."
Enter the amount and click "Set limit." Alternatively, selecting "Set to unlimited" will remove that member's monthly spend limit (they will still be subject to any organization or seat-level spend limits).
This allows owners fine control over usage credits, so you can set limits for different members based on their roles or individual needs. Once a user reaches their defined spend limit, this will automatically pause their usage credits until the end of the month. They will need to wait for their usage limits to reset before using Claude again.
Note that the **Spend limits by user** section has a **MTD Spend** column, so you can track members' usage patterns and optimize seat assignments.
------------------------------------------------------------------------
## Usage credit pricing
Usage credits are billed at standard API rates; see our **[pricing page](pricing.md#api)** for details.
Price and plans are subject to change at Anthropic's discretion.
------------------------------------------------------------------------
## Request usage credits for seat-based Enterprise plans
Members of seat-based Enterprise plans will see a "Request usage credits" link upon hitting their included usage limit.
Click this to send a request to organization Admins to either switch you to a Premium seat (if you're currently assigned to a Standard seat) or enable usage credits for your user account. This will change to **Request sent to admin** after clicking it, indicating that you submitted a request for a seat tier increase or usage credits to an organization Admin.
Owners, Primary Owners, and custom roles with the Billing permission set to "Can manage" can review these requests in **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**. Clicking into "Review requests" will open a modal where each requester is listed, along with their current seat, and the time they asked for more usage. Click "Increase limit" next to each request you want to approve. Admins and above will also receive a daily email including all your organization's outstanding requests.
### Disable usage credit requests
If you want to prevent users from submitting requests for usage credits, an organization owner can follow these steps:
1. Navigate to **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**.
2. Scroll to the bottom of the page and find **Usage credit requests**.
3. Toggle it off.
------------------------------------------------------------------------
## Frequently asked questions
### What happens when I reach my spend limit?
If your account is configured for usage credits and you exceed your set spend limit, you won't be able to use Claude, Cowork, or Claude Code again until the next billing period, or until your limits are adjusted.
### Why was I able to exceed my spend limit?
It's possible to slightly exceed your defined spend limit. Our system checks if you're within your limit before you're allowed to make a single request or send a message. Once the request is processed, we calculate your token consumption, which means you may bypass your limit with that request. Once this happens, any subsequent requests will be blocked.
### Can usage credits be disabled completely?
Yes, Owners and Primary Owners can choose to disable usage credits entirely, which means that members of the organization will be unable to continue working once they reach their usage limits and will need to wait for them to reset.
---
## Get started with the Team plan | Claude Help Center
Source: https://support.claude.com/en/articles/9267247-get-started-with-the-team-plan
Path: 17-Billing-Plans/get-started-with-the-team-plan.md
# Get started with the Team plan
## Requirements to sign up for a Team plan
- The account creator must use a business email address. Public domains like @gmail.com, @yahoo.com, and @hotmail.com aren't allowed—but you can **[add them as permitted domains](../21-Account-Support/account-management-faqs.md#h_b54c41c86c)** for other members of your organization.
- All team members must have an email address with one of your organization's allowed email domains to be invited to the account.
- During sign-up, you can choose between monthly or annual billing options.
- Refer to this article for more information: **[How is my Team plan bill calculated?](how-is-my-team-plan-bill-calculated.md)**
- Team plans require a minimum of two members and are not intended for individual use.
## Create a new Team organization
To get started with the Team plan, navigate to **[claude.ai/login](https://claude.ai/login)** and enter your work email address. Follow the onboarding prompts and select the Team plan.
## Upgrade from an individual plan to the Team plan
If you already have a Free, Pro, or Max account on your work email and want to upgrade to Team, sign in to your account and visit **[claude.ai/upgrade](https://claude.ai/upgrade)**. Follow the steps to create your Team.
If you see the **Keep your personal account separate** checkbox, then upgrading to Team upgrades your existing organization in place by default. Your organization ID stays the same and some of your content carries over to your new Team plan. For a full list of what does and doesn’t migrate, see **[Move your personal Claude account to a Team or Enterprise organization](../21-Account-Support/can-individuals-with-pro-or-max-plan-accounts-migrate-them-to-team-or-enterprise-plan.md#h_4e63ef6e87)**.
**Note:** Once content has been moved into an organization, it can't be moved back to a personal account.
If you don’t see the **Keep your personal account separate** checkbox, then this upgrade process will create a separate Team plan with a new organization ID instead. This applies to subscriptions purchased via the Apple App Store, paused plans, and plans using unsupported currencies.
What else happens during an in-place upgrade:
- Your individual Pro or Max subscription is cancelled automatically and you receive a prorated refund for the unused portion of your billing period. The refund is issued about 24 hours after your Team payment goes through, and depending on your bank, it can take several more business days to appear on your statement.
- Any prepaid usage credits on your individual account are refunded.
- Public projects in your account become private once the upgrade is complete. Project owners can give others in their organization access to the project from its **Share** menu. For details, see **[Manage project visibility and sharing](https://support.claude.com/en/articles/9519189-manage-project-visibility-and-sharing)**.
- If you’ve claimed monthly API credits on your Max plan, your Max link ends. A Team Owner or Primary Owner can claim the team’s credits once the Team plan has been active for seven days.
**Note:** If you'd rather keep your personal Claude account active alongside your new Team plan, check this box in the team-creation flow before completing your upgrade: **Keep your personal account separate**. We’ll set up a new workspace for this team and your existing chats and projects stay in your personal account. If you check this, your individual subscription stays active and your personal data stays in your individual account instead of moving into the Team org.
### Apple App Store subscribers
Because Apple doesn't allow third-party cancellation of App Store subscriptions, in-place upgrades work differently if you signed up for Pro or Max through the Apple App Store. By default, you will upgrade to a new, separate Team organization. If you'd prefer to upgrade in place, you’ll need to **[cancel your iOS subscription](https://support.claude.com/en/articles/8325617-cancel-your-pro-or-max-subscription#h_54384c9962)** first and wait for the billing period to end.
### Google Play Store subscribers
Subscriptions purchased through the Google Play Store are eligible for in-place upgrade. Your refund doesn't have the 24-hour wait, but it can take a few days to appear.
### If you decline the in-place upgrade
If you choose to keep your personal account, your Team plan creates a separate Claude organization. You can switch between your personal account and the Team org by clicking your initials or name in the lower left corner and selecting the account you want to access. Data isn't shared between separate accounts.
To use only your Team plan after upgrading separately, you'll need to **[cancel your paid subscription](how-do-i-cancel-my-paid-claude-subscription.md)** and **[delete your individual Claude account](https://support.claude.com/en/articles/9028421-how-can-i-delete-my-claude-account)**.
## Claim your team’s API credits
Claude Max and Team plans include monthly credits for the Claude API. One owner links a Claude Console organization and claims the pooled credit, up to \$500 a month. New subscribers can claim once they’ve been on an eligible plan for seven days.
To claim, you need to be a Primary Owner or Owner on your Team plan and have the Owner, Admin, or Billing role in the Console organization.
1. Go to **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**.
2. In the **API credits** section, select "Link organization."
3. Choose the Console organization you want to receive the credits, or create a new one.
4. Review the **[Supplemental Credit Terms](https://www.anthropic.com/legal/credit-terms)**, then select "Link organization."
Learn more about **[monthly API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)**.
---
## HIPAA-ready Enterprise plans | Claude Help Center
Source: https://support.claude.com/en/articles/13296973-hipaa-ready-enterprise-plans
Path: 17-Billing-Plans/hipaa-ready-enterprise-plans.md
# HIPAA-ready Enterprise plans
This feature is available for Enterprise plans only (both self-serve and sales-assisted).
We offer a HIPAA-ready version of Claude that is available for organizations on Enterprise plans that choose to process protected health information (PHI) through Claude. This article explains what the offering includes, which features are available, and how to get started.
## Overview
The HIPAA-ready Enterprise offering is designed for healthcare providers, health plans, healthcare data processors, and their business associates who are subject to HIPAA requirements. This offering includes a Business Associate Agreement (BAA), functionality, and safeguards designed to support an organization's HIPAA compliance requirements.
## Who is this for?
This offering is designed for HIPAA-covered entities and their business associates, including:
- Healthcare providers (e.g., hospitals, clinics, physicians)
- Health plans and insurers
- Healthcare data processors
- Business associates that handle PHI on behalf of covered entities
- Other HIPAA regulated entities
If you're unsure whether your organization benefits from a HIPAA-ready product, ask yourself: will you be processing protected health information through Claude? If yes, you need the HIPAA-ready offering with a BAA.
## Feature availability
The HIPAA-ready Enterprise offering includes many of the features available on **[standard Enterprise plans](what-is-the-enterprise-plan.md)**—but enabling HIPAA doesn't bring every feature under your BAA. Features fall into three categories: covered by your BAA, available but not covered, and disabled. PHI should only be processed through covered features, so it's important for administrators to know which features fall in which category and to configure their workspace accordingly. The **[Implementation Guide for HIPAA Entities](https://trust.anthropic.com/resources?s=rgirr4qe8u7ek8c2igx3&name=claude-for-enterprise-hipaa-ready-offering-implementation-guide)** on the Anthropic Trust Center lists every feature's status and is the authoritative source.
**Important:** Enabling HIPAA alone doesn't bring Claude Code or Cowork under your BAA. The Primary Owner must also apply the HIPAA configuration to Claude Code (local mode) and Cowork (local mode). This configuration is currently only available to organizations with an Anthropic account team. Claude Code (local mode) is Claude Code in the terminal and in the Code tab of Claude Desktop. Cowork (local mode) is Cowork in Claude Desktop.
- **Before the Primary Owner applies the configuration:** Cowork is available but not covered under your BAA. Claude Code is covered only with zero data retention (ZDR) enabled, which is available on qualified accounts only. Without ZDR, Claude Code is also available but not covered. Don't use PHI with a product that isn't covered.
- **After the Primary Owner applies the configuration:** Your BAA covers Claude Code (local mode) and Cowork (local mode). Cloud features such as Claude Code cloud sessions, Claude Code Remote Control, and Cowork in the cloud aren't available. The Primary Owner can't remove the configuration.
Learn how to get the configuration and how to prepare in **[Use Claude Code (local mode) and Cowork (local mode) on a HIPAA-ready Enterprise plan](https://support.claude.com/en/articles/17318731)**.
## Additional resources
For detailed implementation requirements and technical specifications, review the **[Implementation Guide for HIPAA Entities](https://trust.anthropic.com/resources?s=rgirr4qe8u7ek8c2igx3&name=claude-for-enterprise-hipaa-ready-offering-implementation-guide)** on the Anthropic Trust Center. You can download the Implementation Guide directly during the setup flow.
**Note:** You'll need to request access to view the Implementation Guide. Requests from domains matching existing customer accounts are approved automatically.
------------------------------------------------------------------------
## Get started
Eligible Enterprise organizations can enable HIPAA directly from organization settings—no sales or legal cycle required. The Business Associate Agreement (BAA) is included in the flow as click-to-accept, so there's no separate document to sign and return. Clicking “Accept and Enable HIPAA” constitutes acceptance of the BAA.
### Eligibility
You can enable HIPAA from organization settings if your organization is on an Enterprise plan. Team plans and individual plans (Free, Pro, and Max) can't enable HIPAA.
Only the **Primary Owner** of the organization can accept the BAA and enable HIPAA. Other Owners or Admins can't complete this flow on the org's behalf. If you're an admin but not the Primary Owner of the Enterprise organization, ask your Primary Owner to sign in and complete enablement.
### Before you begin
Two things to know up front:
- **Enabling HIPAA resets certain settings across your organization.** Some configurations return to defaults as part of the transition to a HIPAA-ready state. The onboarding modal and the Implementation Guide (downloadable during the flow) detail what changes.
- **This is a one-way decision.** Once HIPAA is enabled and the BAA is accepted, the change can't be reversed from organization settings.
You must review the BAA and the Implementation Guide before accepting, as this is an irreversible organization transition.
**Note:** The BAA offered through the self-serve flow is a standard agreement and can't be modified.
### Enable HIPAA
1. Sign in to Claude as the Primary Owner and go to **[Organization settings \> Data and privacy](https://claude.ai/admin-settings/data-privacy-controls)**.
2. Go to **HIPAA Compliance.**
3. Click “Enable” to open the consent flow.
4. Download the Business Associate Agreement, review it, then click “Next.”
5. Download the Implementation Guide, review it, then click “Next.”
6. Click “Accept and enable HIPAA.”
### Confirmation
Once enabled, you'll see a checkmark in the **HIPAA Compliance** section of organization settings, confirming your organization has been configured to process PHI through Claude in accordance with HIPAA. If you don't see this checkmark, your organization isn't enabled. Enabling HIPAA alone doesn't bring Claude Code or Cowork under your BAA. The Primary Owner must also apply the HIPAA configuration to Claude Code (local mode) and Cowork (local mode). See **[Use Claude Code (local mode) and Cowork (local mode) on a HIPAA-ready Enterprise plan](https://support.claude.com/en/articles/17318731)**.
The onboarding modal will guide you through next steps for your team.
For help with the BAA, the Implementation Guide, or post-enablement questions, reach out to your Anthropic account team or **[our support team](../15-Claude-AI-Features/how-to-get-support.md)**.
------------------------------------------------------------------------
## If you have an existing API BAA
If your organization signed a BAA for Claude API usage before December 2, 2025, that agreement only covers API usage—it does not extend to the HIPAA-ready Enterprise plan. To add this Enterprise plan access, you'll need to sign a new BAA with your account team.
BAAs signed after December 2, 2025 can cover both API usage and the Enterprise plan under a single agreement.
If you use the Claude API, learn more about **[HIPAA-ready Claude API access and how to set it up](../04-API-Reference/Other/manage-claude-api-and-data-retention.md#hipaa-readiness)**.
---
## How am I billed for my Enterprise plan? | Claude Help Center
Source: https://support.claude.com/en/articles/11526368-how-am-i-billed-for-my-enterprise-plan
Path: 17-Billing-Plans/how-am-i-billed-for-my-enterprise-plan.md
# How am I billed for my Enterprise plan?
Enterprise plan billing has two parts: a fixed seat fee and separate usage charges. The seat fee covers platform access. Usage is billed on top of that, based on what your team actually consumes.
How billing works depends on whether your organization is on a self-serve or sales-assisted Enterprise plan, and whether you're using the current single Enterprise seat or a legacy seat type. The sections below are organized by plan type—make sure you're reading the section that matches your setup. If you're unsure which plan type you're on, check with the person who set up your Enterprise account or contact your Anthropic account manager. Price and plans are subject to change at Anthropic's discretion.
**Important:** The main sections of this article describe the current Enterprise seat billing model, which applies to all new Enterprise plans.
- If your organization was provisioned before the transition to the single Enterprise seat and you see **Chat** and **Chat + Claude Code** seat types in **[Organization settings \> Organization](https://claude.ai/admin-settings/organization)**, skip to the **[Chat and Chat + Claude Code seats section](#h_f6aa4f4dd2)**.
- If your organization is on a seat-based plan with **Standard** and **Premium** seats, skip to the **[seat-based plans section](#h_3b87de90bd)**.
- Chat-only seats and Standard/Premium seats are no longer available for new contracts—both legacy plan types are transitioning to the single Enterprise seat at their next renewal.
------------------------------------------------------------------------
## Seat fees
All usage-based Enterprise plans (self-serve and sales-assisted) use the same seat pricing: **priced per user per month and billed annually**.
The seat fee gives each person access to Claude on web, desktop, and mobile, plus Claude Code and Cowork, but doesn't include any usage. Every token your team consumes is billed separately at standard API rates.
You're charged for the number of seats on your plan at the start of your annual billing cycle. If you add seats during your term, you're charged the prorated amount immediately for the remainder of the year.
**Example:** Your annual plan starts January 1 with 50 seats. You are charged upfront for the seats. On April 1, you add 10 seats. You'll be charged immediately for the remaining months.
**Note:** Seats cannot be removed mid-term on self-serve Enterprise plans. For step-by-step instructions on purchasing, adding, and managing seats, see **[Purchase and manage seats on Enterprise plans](purchasing-and-managing-seats-on-enterprise-plans.md)**.
------------------------------------------------------------------------
## Usage billing and payment methods
On usage-based Enterprise plans, usage is charged separately from your seat fee and is based on actual token consumption at standard API rates. For current per-model pricing, see our **[API pricing page](https://www.anthropic.com/pricing#api)**.
**Important:** If your organization has the US-only inference setting turned on, usage is billed at 1.1x standard API rates for Claude Opus 4.6, Claude Sonnet 4.6, and later models. This applies to both self-serve and sales-assisted plans. Learn more about **[enabling US-only inference for your organization](https://support.claude.com/en/articles/15422948)**.
How and when you're billed for usage depends on your plan type:
### Self-serve Enterprise
**Usage billing**
Usage is purchased **upfront in credits**. Your credits draw down as your team uses Claude and Claude Code. When your credits run out, usage stops until an Owner, Primary Owner, or custom role with the **Billing** permission set to "Can manage" purchases more. Self-serve Enterprise plans are billed in USD only. If your organization needs to pay in another currency, **[contact our Sales team](https://claude.com/contact-sales)** to set up a sales-assisted plan.
- After setup, Owners, Primary Owners, and custom roles with the **Billing** permission set to "Can manage" can purchase additional credits at any time from **[Organization](https://claude.ai/admin-settings/organization) [settings \> Usage](https://claude.ai/admin-settings/usage)**.
- All credits are shared across your organization—any team member can draw from the same pool.
**Note:** If you purchased your Enterprise plan through AWS Marketplace, billing works like sales-assisted plans, except that you pay through AWS. You're billed monthly in arrears based on your organization's consumption rather than purchasing credits upfront.
**Payment methods**
Self-serve Enterprise organizations can pay by credit card, debit card, or ACH bank transfer. Owners, Primary Owners, and custom roles with the **Billing** permission set to "Can manage" can switch between payment methods at any time in **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**.
For details on ACH, including activation timing and auto-reload, see **[What is the Enterprise plan?](what-is-the-enterprise-plan.md)**
### Sales-assisted Enterprise
**Usage billing**
Usage is **billed monthly in arrears** based on your organization's actual consumption during each billing period. You'll receive a monthly invoice reflecting usage for that period. Speak with your account manager for questions about your usage invoices.
**Payment methods**
On sales-assisted Enterprise plans, invoices aren’t charged automatically to a saved card. Each invoice, including your seat invoice and each monthly usage invoice, is emailed to your organization’s billing contact with a secure payment link. The payment terms are shown on the invoice.
You can pay by bank transfer (ACH or wire) or by credit card. Invoices of \$50,000 or more can only be paid by bank transfer. The credit card option won’t appear on the payment page for invoices at or above this amount.
To have future invoices charged automatically to a card, contact your Anthropic account manager, who will arrange it with our billing team. With automatic payment, your card is charged on the invoice date instead of at the end of your payment term. You can’t set this up in **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)** because those payment method settings only apply to self-serve Enterprise plans.
------------------------------------------------------------------------
## How usage works across your team
Enterprise seats don't come with an individual token allowance. All usage across your organization is billed together at API rates, regardless of who consumed it.
What this looks like in practice depends on your plan type:
### Self-serve Enterprise
Everyone's usage draws from the same credit balance. One person's heavy usage depletes credits faster for everyone, so monitoring and spend limits matter here. When the balance hits zero, usage stops for the whole organization until an Owner purchases more.
### Sales-assisted Enterprise
There's no balance to deplete. Everyone's usage is metered and added to the same monthly invoice. One person's heavy usage doesn't block anyone else — it just increases what shows up on the bill. If you want a ceiling, set spend limits.
------------------------------------------------------------------------
## Spend limits
Owners, Primary Owners, and custom roles with the **Billing** permission set to "Can manage" can set spend limits to manage your organization's consumption. This applies to both self-serve and sales-assisted plans.
To configure spend limits, navigate to **[Organization](https://claude.ai/admin-settings/organization) [settings \> Usage](https://claude.ai/admin-settings/usage)**.
You can set limits at two levels:
- **Organization level:** Maximum spend for all usage across your organization.
- **Individual level:** Maximum spend for a specific user.
These limits work hierarchically, so a user cannot exceed their individual limit or the organization limit, whichever is lower.
On **self-serve plans**, spend limits work alongside your credit balance. If a user hits their individual limit or the organization limit, their usage will stop even if credits remain. Owners can adjust limits at any time.
On **sales-assisted plans**, spend limits prevent usage from continuing past the limit threshold. If a limit is reached, usage stops until the next billing period begins or an owner raises the limit.
**Owners can set limits to "unlimited,"** but consumption will still be billed. You cannot disable billing for usage—usage-based pricing is a core part of the Enterprise plan.
------------------------------------------------------------------------
## Monitoring usage and spend
You can track your organization's usage and spending in a few places:
### Organization settings \> Usage
View month-to-date spending for each member, current spend limit status, and credit balance (self-serve plans).
At the top of this page is a section called **Blocked by a spend limit** with a view of how often members reach their spend limits. **Blocked by a spend limit** is built for usage-based Enterprise plans. Orgs without usage-based seats only see how many members are blocked or near their limit right now.
You'll see three metrics at the top:
- **Blocked right now:** the number of users currently locked out because they've reached a spend limit. Click this to see who they are.
- **Near their limit:** the number of users approaching their spend limit.
- **Member-days lost this month:** total days of blocked usage across your organization this month, compared to the same day last month.
Below this, a chart shows the time at limit per active seat this month, for all members and your power users (top 10% by spend), plotted against prior months with a forecast of where this month is headed. It also calls out which group or limit type accounts for the most time at limit, so you can quickly see where limits are working as intended and where your most engaged users may need more headroom.
You can adjust limits from the same page, including raising a seat type's default or increasing the limits of the members who reached it.
**Note:** If a user’s extra-usage spend limit is set to \$0, extra usage is turned off for them entirely. They can appear in the "Blocked right now" count, but their time isn't counted as time lost to a spend limit. The member-days figure and the chart include only members whose limit is above \$0 and who reached their limit.
### Monthly invoices
See detailed usage per user for the billing period (sales-assisted plans).
### Spend limit notifications
Get alerts when users or your organization approach configured spending thresholds.
------------------------------------------------------------------------
## What happens when usage stops
If usage stops on your Enterprise plan, here's how Owners, Primary Owners, and custom roles with the **Billing** permission set to "Can manage" can resume:
- **Self-serve plans:** If credits run out or a spend limit is reached, purchase additional credits or raise the spend limit from **[Organization](https://claude.ai/admin-settings/organization) [settings \> Usage](https://claude.ai/admin-settings/usage)**.
- **Sales-assisted plans:** If a spend limit is reached, you can raise the limit, or usage will resume at the start of the next billing period. Contact your account manager with questions.
------------------------------------------------------------------------
## Chat and Chat + Claude Code seats
**Important:** Chat and Chat + Claude Code are legacy seat types that are no longer available for new Enterprise contracts. This section only applies to organizations that were provisioned with these seat types before the transition to the single Enterprise seat. If you recently signed a new Enterprise contract, the main sections of this article apply to you—your plan uses the single Enterprise seat.
Some existing usage-based Enterprise organizations currently have two seat types with different pricing. If you see **Chat** and **Chat + Claude Code** seats in **[Organization settings \> Organization](https://claude.ai/admin-settings/organization)**, this section applies to you.
Seat fees are billed annually. Usage billing works the same way as described in the **[Usage billing section](#h_540cbc3861)** above: separately from seat fees, at API rates, and in arrears on sales-assisted plans.
### Transition to the single Enterprise seat
At your next contract renewal, your plan will automatically transition to the single Enterprise seat model. When that happens, all users—regardless of their current seat type—will move to the **Enterprise seat**. This seat includes Claude Code, Cowork, Chat and more.
If you have questions about your upcoming renewal, reach out to your Anthropic Contact or **[our Sales team](https://claude.com/contact-sales)**.
------------------------------------------------------------------------
## Seat-based plans
**Important:** Standard and Premium are legacy seat types that are no longer available for new Enterprise contracts. This section only applies to organizations that were provisioned with these seat types before the transition to usage-based billing. If you recently signed a new Enterprise contract, the main sections of this article apply to you.
Some Enterprise organizations are on older seat-based plans with **Standard** and **Premium** seats. These plans charge a flat monthly fee per seat that includes a usage allowance, which is a different model than the usage-based billing described above.
If you see "Standard" and "Premium" seats in **[Organization settings \> Organization](https://claude.ai/admin-settings/organization)**, this section applies to you.
On seat-based plans, usage credits are available to allow team members to continue working after reaching their seat's included limits. For details on how usage credits work and how they're billed on your plan, see **[Manage usage credits for Team and seat-based Enterprise plans](https://support.claude.com/en/articles/12005970-)**.
### Transitioning to usage-based Enterprise
At your next contract renewal, your plan will transition to the usage-based single Enterprise seat model described in this article. If you'd like to migrate before your renewal, reach out to your Anthropic Contact or **[our Sales team](https://claude.com/contact-sales)**.
---
## How can I cancel my Claude Pro subscription on the Claude app for iOS? | Claude Help Center
Source: https://support.claude.com/en/articles/9264804-how-can-i-cancel-my-claude-pro-subscription-on-the-claude-app-for-ios
Path: 17-Billing-Plans/how-can-i-cancel-my-claude-pro-subscription-on-the-claude-app-for-ios.md
4. How can I cancel my Claude Pro subscription on the Claude app for iOS?
# How can I cancel my Claude Pro subscription on the Claude app for iOS?
If you signed up for Claude Pro via the iOS app, your subscription and payment will be handled directly on your iOS device.
To cancel your subscription, click on your initials in the top right corner of the Claude app for iOS, and then click “Billing” from the menu options. Select “manage subscription” and follow the prompts for cancellation. If you’ve already removed the app from your device, you can also follow the instructions located in the App Store resource [here](https://support.apple.com/en-us/118428) to unsubscribe.
You may cancel your Claude Pro subscription at any time from the platform you signed up on. To avoid being charged for your next billing period, cancel your subscription at least 24 hours before your next billing date.
---
## How can I learn more about Claude API pricing? | Claude Help Center
Source: https://support.claude.com/en/articles/8114523-how-can-i-learn-more-about-claude-api-pricing
Path: 17-Billing-Plans/how-can-i-learn-more-about-claude-api-pricing.md
# How can I learn more about Claude API pricing?
March 16, 2026
For our most up-to-date prices, please consult our [pricing page](pricing.md#api).
---
## Cancel your Pro or Max subscription | Claude Help Center
Source: https://support.claude.com/en/articles/8325617-how-do-i-cancel-my-paid-claude-subscription
Path: 17-Billing-Plans/how-do-i-cancel-my-paid-claude-subscription.md
# Cancel your Pro or Max subscription
You may cancel your Pro or Max plan subscription at any time by following the cancellation instructions for the platform you signed up on. Your cancellation will take effect at the end of your current billing period and you can continue using your paid plan until then.
**Note:**
- To avoid being charged for your next billing period, cancel your subscription at least 24 hours before your next billing date.
- Monthly API credits included with Max and Team plans aren’t purchased, so they can’t be refunded. They expire at the end of each billing cycle. If you cancel or get a refund for your plan, new monthly credits stop, and credits you already have stay usable until they expire.
## Cancel your Pro or Max subscription on Claude and Claude Desktop
If you signed up for a paid plan on the web version of Claude (**[claude.ai](https://claude.ai)**) or Claude Desktop (Mac, Windows, or Linux), start by logging into your account on a web browser or opening the desktop app. Click on your initials or name in the lower left corner and select “Settings” from the menu. Navigate to **[Settings \> Billing](https://claude.ai/settings/billing)** and click the “Cancel” button.
## Cancel your Pro or Max subscription on Claude for iOS
If you subscribed to a Pro or Max plan via Claude for iOS, your subscription and payment will be handled directly on your iOS device.
To cancel your subscription, click on your initials in the top right corner of Claude for iOS, and then click “Billing” from the menu options. Select “Manage subscription” and follow the prompts for cancellation. If you’ve already removed the app from your device, you can also follow the instructions located in this App Store resource to unsubscribe: **[If you want to cancel a subscription from Apple](https://support.apple.com/en-us/118428)**.
You may cancel your Pro or Max subscription at any time from the platform you signed up on. To avoid being charged for your next billing period, cancel your subscription at least 24 hours before your next billing date.
## Cancel your Pro or Max subscription on Claude for Android
If you subscribed to a Pro or Max plan via Claude for Android, your subscription and payment will be handled directly on your Android device.
To cancel your subscription, click on your initials in the top right corner of Claude for Android, and then click “Billing” from the menu options. Select “Manage subscription” and follow the prompts for cancellation. If you’ve already removed the app from your device, you can also follow the instructions located in this Play Store resource to unsubscribe: **[Cancel, pause, or change a subscription on Google Play](https://support.google.com/googleplay/answer/7018481?hl=en&co=GENIE.Platform%3DAndroid)**.
You may cancel your Pro or Max subscription at any time from the platform you signed up on. To avoid being charged for your next billing period, cancel your subscription at least 24 hours before your next billing date.
---
## How do I sign up for the Max plan? | Claude Help Center
Source: https://support.claude.com/en/articles/11049752-how-do-i-sign-up-for-the-max-plan
Path: 17-Billing-Plans/how-do-i-sign-up-for-the-max-plan.md
# How do I sign up for the Max plan?
This article applies to individual consumers signing up for paid Max plans. If you're part of an organization looking to use Claude with your team, refer to **[Team and Enterprise plans](https://support.claude.com/en/collections/9387370-team-and-enterprise-plans)**.
## Instructions for new users
1. Visit **[claude.ai](https://claude.ai/)**.
2. Create a new account.
3. During the onboarding process, select the Max plan option.
4. Choose your preferred usage tier (5x or 20x).
5. Enter your payment information.
6. Confirm your subscription.
## Instructions for existing free users
1. Log in to your Claude account.
2. Go to **[Settings \> Billing](https://claude.ai/settings/billing)**.
3. Select "Upgrade to Max."
4. Choose your preferred usage tier (5x or 20x).
5. Enter your payment information.
6. Confirm your subscription.
## Instructions for existing Pro users
1. Log in to your Claude account.
2. Go to **[Settings \> Billing](https://claude.ai/settings/billing)**.
3. Select "Upgrade to Max."
4. Choose your preferred usage tier (5x or 20x).
5. Confirm your upgrade.
Your Pro plan is upgraded to Max immediately. Your billing cycle restarts on the day you upgrade: you're charged for a full billing cycle of Max, minus a prorated credit for the unused time left on your Pro plan. Your usage also starts fresh on the Max limits right away, so if you've reached your Pro limit, you can keep using Claude without waiting for your session to reset.
If you're moving from an annual Pro plan to a Max plan and the remaining balance on your annual Pro plan is greater than your Max plan price, you will receive a credit to your account for the remaining balance. This credit will be applied to future subscription costs.
**Note:** If you subscribed through Google Play, upgrades work differently. You're charged the full price of your new plan when you upgrade, and the unused value of your previous plan is converted into extra days on your new plan. Your renewal date will land a few days later than a full month—you keep the value of your remaining time, but you won't see a discounted charge.
## How does subscription renewal work for Max plans?
After subscribing for a Max plan, your subscription will be set to automatically renew at the end of each billing period by default. This ensures uninterrupted access to Max features. However, you have the flexibility to **[cancel your paid plan](https://support.claude.com/en/articles/8325617)** at any time if you choose not to continue.
---
## How is my Team plan bill calculated? | Claude Help Center
Source: https://support.claude.com/en/articles/9267289-how-is-my-team-plan-bill-calculated
Path: 17-Billing-Plans/how-is-my-team-plan-bill-calculated.md
# How is my Team plan bill calculated?
Prices shown are for US customers and exclude applicable taxes. Pricing, currency, and tax handling vary by region. Visit **[claude.ai/upgrade](https://claude.ai/upgrade)** to see current pricing for your location.
For current pricing by seat type and billing interval, see **[What is the Team plan?](what-is-the-team-plan.md)**
For information on seat types and what's included, see **[Purchasing and managing seats on Team plans](https://support.claude.com/en/articles/12004354-purchasing-and-managing-seats)**.
------------------------------------------------------------------------
## How does adding or removing members affect my bill?
**Adding members or upgrading seats:** You will be charged the prorated amount immediately.
**Removing members:** You will not receive an immediate credit or refund. The seat becomes available to assign to another member.
For instructions to add and remove members, see **[Manage members on Team and Enterprise plans](https://support.claude.com/en/articles/13133750)**.
------------------------------------------------------------------------
## Usage credits
If usage credits are enabled, your bill may include charges for usage beyond seat limits. For details on how usage credits work and how they're billed on your plan, see **[Manage usage credits for Team and seat-based Enterprise plans](https://support.claude.com/en/articles/12005970)**.
### Monthly API credits
Claude Max and Team plans include monthly credits for the Claude API. On Team plans, credits for all seats are pooled into one monthly balance, capped at \$500. Usage is never charged to your Claude plan.
The pool follows your seat count. It’s calculated from the seats on your plan each time credits are deposited. For example, a team with three Standard seats and two Premium seats receives \$260 a month. Adding another Premium seat would increase the next cycle’s credits to \$360. Learn more about **[monthly API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)**.
------------------------------------------------------------------------
## Billing examples
### Annual plan example
On January 1 (the start date of your annual subscription), your annual plan has 10 standard seats. The amount charged would be \$2,400 (\$20 × 10 seats × 12 months) due on January 1st.
On April 1st, you decide to upgrade five of the existing standard seats to premium seats. Since there are 275 days remaining in your subscription year, the prorated cost for the seat upgrades would be: (\$80 × 5 seats × 12 months) × (275 days ÷ 365 days in the year) = \$3,616.44. Your payment method will be charged \$3,616.44 on April 1st for the seat upgrades for the remainder of the subscription year.
If you remove members during your subscription year, their seats will become available to assign to other team members.
Taxes are not included in this example.
### Monthly plan example
On January 1 (the first day of your billing cycle), your Team plan has 10 standard seats. The amount charged would be \$250 (\$25 × 10 seats) due on January 1st.
On January 15th, you decide to upgrade five standard seats to premium seats. Since there are 16 days remaining in January, the prorated cost for the seat upgrades would be: (\$100 × 5 seats × 16 days) ÷ 31 days in January = \$258.06. Your payment method will be charged \$258.06 on January 15th for the seat upgrades in January.
You will be charged for the number of members on your team at the beginning of each billing cycle. If you remove members in the middle of a billing cycle, their seats will become available to assign to other team members.
Taxes are not included in this example.
**Note:** The "Projected total" displayed on **[your organization’s Billing page](https://claude.ai/admin-settings/billing)** is not inclusive of taxes.
Price and plans are subject to change at Anthropic's discretion.
---
## How large is the context window on paid Claude plans? | Claude Help Center
Source: https://support.claude.com/en/articles/8606394-how-large-is-the-context-window-on-paid-claude-plans
Path: 17-Billing-Plans/how-large-is-the-context-window-on-paid-claude-plans.md
# How large is the context window on paid Claude plans?
This article explains how large the context window is on paid Claude plans (Pro, Max, Team, Enterprise) when you chat with Claude, or use Claude Code or Claude Cowork.
## Chatting with Claude
[TABLE]
Outside of these models, Claude’s context window size is 200K, meaning it can ingest 200K+ tokens (about 500 pages of text or more) when using a paid Claude plan to chat with Claude.
## Claude Code
[TABLE]
## Claude Cowork
[TABLE]
## Automatic context management
For users on paid plans with code execution enabled, Claude automatically manages your conversation context. When your conversation approaches the context window limit, Claude summarizes earlier messages to make room for new content. This allows conversations to continue indefinitely in most cases. Longer conversations that trigger automatic context management use more of your usage limit.
Your full chat history is preserved so Claude can reference it, even after earlier portions have been summarized. You may occasionally notice Claude "organizing its thoughts" during long conversations—this is the automatic context management at work.
**Note:** Code execution must be enabled for automatic context management to work. In rare edge cases (such as very large first messages or system errors), you may still encounter context window limits.
## Maximizing your context window
While context is managed automatically for most conversations, you can still optimize how you use your available context space:
- **Utilize projects effectively:** Projects use retrieval-augmented generation (RAG), which allows Claude to work with larger amounts of information by only loading relevant content into the context window.
- **Keep project instructions concise:** Claude performs best when you use project instructions for general context around your project, key guidelines, and Claude's role.
- **Manage tools and connectors:** These features are token-intensive, so being mindful of how many you have active helps maximize your available context.
---
## How to change your Pro plan from monthly to annual billing | Claude Help Center
Source: https://support.claude.com/en/articles/10185996-how-to-change-your-pro-plan-from-monthly-to-annual-billing
Path: 17-Billing-Plans/how-to-change-your-pro-plan-from-monthly-to-annual-billing.md
# How to change your Pro plan from monthly to annual billing
March 16, 2026
Save on your Pro plan subscription by switching from monthly to annual billing. When you upgrade, any remaining time on your current monthly subscription will be credited to your new annual plan invoice.
## To switch from monthly to annual billing
1. Navigate to [Settings \> Billing](https://claude.ai/settings/billing).
2. Click "Adjust plan" next to your Pro subscription details.
3. From [the upgrade page](https://claude.ai/upgrade), select "Get Pro annual plan"
4. Review the annual price on the next screen.
5. Click "Confirm subscription."
## What happens next?
- Your subscription billing period switches from monthly to annual immediately.
- Any unused time from your monthly subscription will be automatically credited to your first annual invoice. You’ll see this credit as a separate line item on your invoice.
- Your next billing date will be set to one year from the date you switch.
- You can cancel your subscription at any time from your billing settings. See [How do I cancel my paid Claude subscription?](how-do-i-cancel-my-paid-claude-subscription.md) for more information.
---
## How to gift a Claude subscription | Claude Help Center
Source: https://support.claude.com/en/articles/12938627-how-to-gift-a-claude-subscription
Path: 17-Billing-Plans/how-to-gift-a-claude-subscription.md
# How to gift a Claude subscription
**Important:** Gift subscriptions are currently unavailable to purchase. This applies to all accounts, so there’s nothing you need to fix on your end. We don’t have a date to share yet for when purchasing will be available again.
## What's included?
Gift subscriptions purchased when they were available include full access to all features of the selected plan. Refer to the below articles for full details for each plan:
- **[What is the Pro plan?](what-is-the-pro-plan.md)**
- **[What is the Max plan?](what-is-the-max-plan.md)**
## How to purchase a gift
It's not possible to purchase a gift at this time.
**Important:** Previously purchased gifts will expire 365 days after the purchase date. Recipients cannot redeem multiple gifts at one time or stack redemptions.
## Delivery options
These apply to gift subscriptions purchased while they were still available:
- **Email delivery:** The recipient received the gift directly in their inbox. The email include your personalized message and a redemption button.
- **Shareable link:** You received a link that you could share however you liked—in a card, text message, or in person.
## Good to know
- Recipients redeem gifts on the web at **[claude.ai/gift/redeem](https://claude.ai/gift/redeem)**. For more information, see **[How to redeem a Claude gift subscription](how-to-redeem-a-claude-gift-subscription.md)**.
- Recipients with active mobile (iOS or Android) subscriptions will need to wait until their mobile subscription ends before redeeming.
- No credit card is required for the recipient to redeem.
---
## How to redeem a Claude gift subscription | Claude Help Center
Source: https://support.claude.com/en/articles/12938695-how-to-redeem-a-claude-gift-subscription
Path: 17-Billing-Plans/how-to-redeem-a-claude-gift-subscription.md
# How to redeem a Claude gift subscription
March 16, 2026
Someone sent you a Claude gift subscription—here's how to redeem it and start using Claude.
## How to redeem your gift
1. Open the gift email or link you received.
2. Click “Redeem your gift.”
3. Sign in to your Claude account, or create a new account if you don't have one.
4. Confirm redemption.
5. You can also redeem directly at [claude.ai/gift/redeem](https://claude.ai/gift/redeem) and enter your gift code.
**Important:** Your gift will expire 365 days after the purchase date. It’s not possible to redeem multiple gifts at one time or stack redemptions.
## What happens when you redeem
Your experience depends on your current subscription status:
**If you're a new or free user:** Your account is upgraded to the gifted plan immediately. You'll have full access for the duration of the gift.
**If you're a Pro subscriber (web) and receive a Pro gift:** Your Pro subscription is extended by the gift duration.
**If you're a Pro subscriber (web) and receive a Max gift:** You're upgraded to the Max plan for the gift duration. When the gift ends, your Pro subscription resumes. Any unused time from your Pro billing cycle is added as account credit.
**If you're a Max subscriber (web) and receive a lower-tier gift:** The gift value is converted to account credit, which is automatically applied to your future invoices.
**If you're a Max subscriber (web) and receive the same or higher Max tier:** Your Max subscription is extended or upgraded accordingly.
## Mobile Subscribers
If you have an active subscription through the iOS App Store or Google Play Store, you'll need to wait until that subscription ends before you can redeem a gift subscription. Gift subscriptions can only be redeemed on the web.
Your gift won't expire while you wait—you can redeem it once your mobile subscription ends.
## Troubleshooting
### I don't see the redemption email
Check your spam or junk folder. If you still can't find it, ask the person who sent the gift to confirm your email address or resend the gift link.
### I'm getting an error when trying to redeem
Make sure you're signed in to Claude on the web (not the mobile app).
### Can I use the gift on a different email address?
The gift can be redeemed by any Claude account, regardless of which email received the gift.
---
## I have a paid Claude subscription (Pro, Max, Team, or Enterprise plans). Why is Claude API usage billed separately from my paid Claude plan? | Claude Help Center
Source: https://support.claude.com/en/articles/9876003-i-have-a-paid-claude-subscription-pro-max-team-or-enterprise-plans-why-is-claude-api-usage-billed-separately-from-my-paid-claude-plan
Path: 17-Billing-Plans/i-have-a-paid-claude-subscription-pro-max-team-or-enterprise-plans-why-is-claude-api.md
# I have a paid Claude subscription (Pro, Max, Team, or Enterprise plans). Why is Claude API usage billed separately from my paid Claude plan?
Claude paid plans and the Claude Console are separate products designed for different purposes:
- Claude paid plans give subscribers access to Claude on the web, desktop, and mobile, and offer enhanced features like more usage and priority access during high-traffic periods.
- The Claude Console is our developer platform providing API keys and access to Claude models for building applications and integrations.
A paid Claude subscription enhances your chat experience, and the Claude API is billed separately. Claude Max and Team plans include monthly credits for the Claude API. Learn more about **[monthly API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)**.
If you're interested in both enhanced chat features and API access, you'll need to sign up for a paid Claude plan and separately [set up Console access](https://support.claude.com/en/articles/8114521-how-can-i-access-the-anthropic-api) for API usage. This allows you to benefit from both offerings based on your specific needs.
Refer to this article to learn more about Claude Console billing: [How do I pay for my API usage?](https://support.claude.com/en/articles/8977456-how-do-i-pay-for-my-api-usage)
---
## I’m planning to launch a product using the Claude API. What steps should I take to ensure I’m not violating Anthropic’s Usage Policy? | Claude Help Center
Source: https://support.claude.com/en/articles/8241216-i-m-planning-to-launch-a-product-using-the-claude-api-what-steps-should-i-take-to-ensure-i-m-not-violating-anthropic-s-usage-policy
Path: 17-Billing-Plans/i-m-planning-to-launch-a-product-using-the-claude-api-what-steps-should-i-take-to-ensure.md
# I’m planning to launch a product using the Claude API. What steps should I take to ensure I’m not violating Anthropic’s Usage Policy?
March 16, 2026
We founded Anthropic to put safety at the frontier of AI research and AI products. Our research informs our commercial products, and our models are some of the most reliably safe and resistant to abuse available today. We are working to improve our safety filters based on user feedback - and we expect our commercial customers will hold us accountable when our safety features are failing.
But we believe safety is a shared responsibility. Our features are not failsafe, and committed partners are a second line of defense. Depending on your use case, moderation steps will look different, but here are some additional safety recommendations:
- [Use Claude as a content moderation filter](https://docs.claude.com/en/docs/about-claude/use-case-guides/content-moderation) to identify and prevent violations.
- For external-facing products, disclose to your users that they are interacting with an AI system.
- For sensitive information and decision making, have a qualified professional review content prior to dissemination to consumers.
We encourage you to send us feedback or specific proposals to [\[email protected\]](https://support.claude.com/cdn-cgi/l/email-protection#087d7b6d7a7b696e6d7c714869667c607a6778616b266b6765). For existing commercial partners, we’d recommend [joining our Discord server](https://discord.com/invite/6PPFFzqPDZ) and exchanging ideas with fellow developers as well.
---
## Add or update your paid Claude account’s tax or VAT ID | Claude Help Center
Source: https://support.claude.com/en/articles/9889408-i-need-to-add-or-update-my-paid-claude-account-s-tax-or-vat-id
Path: 17-Billing-Plans/i-need-to-add-or-update-my-paid-claude-account-s-tax-or-vat-id.md
# Add or update your paid Claude account’s tax or VAT ID
August 6, 2026
## Add your tax or VAT ID during signup
When you sign up for a Pro or Max subscription, you may have the option to enter your Tax or VAT ID depending on your location:
1. During the sign-up process, enter your address information.
2. If your address is eligible for tax purposes, an optional field for your Tax or VAT ID will appear.
3. Enter your Tax or VAT ID in the provided field.
4. If the ID is entered correctly, you'll be able to proceed with your signup.
**Important:** If you're signing up for an individual paid account as a business, and want to use a name other than the one tied to your payment method, check the "Use a different name on invoices" box when adding or updating your payment method in **[Settings \> Billing](https://claude.ai/settings/billing)**. Then, enter your company name in the "Bill to" field to ensure it is reflected correctly on your invoice.
## Update your tax or VAT ID after signup
**Note:** Updates to your billing details will only apply to future billing cycles. Previously completed invoices cannot be updated retroactively.
If you need to add or update your Tax or VAT ID after you've already signed up, follow these steps:
1. Log in to your Claude account.
2. Click on your initials or name in the lower left corner and select “Settings” from the menu.
3. Navigate to **[Settings \> Billing](https://claude.ai/settings/billing)**.
4. Click the "Update" button next to your payment method.
5. In the payment update form, you should see a field to enter or update your Tax or VAT ID.
6. Enter or modify your Tax or VAT ID as needed.
7. Save your changes.
**Note:** Your billing address determines your tax jurisdiction. See **[Understanding your billing address and tax calculation](understanding-your-billing-address-and-tax-calculation.md)** for details on how to view or update your billing address.
---
## Add or update your Team plan's tax or VAT ID | Claude Help Center
Source: https://support.claude.com/en/articles/9927624-i-need-to-add-or-update-my-team-plan-s-tax-or-vat-id
Path: 17-Billing-Plans/i-need-to-add-or-update-my-team-plan-s-tax-or-vat-id.md
# Add or update your Team plan's tax or VAT ID
March 16, 2026
## Add your tax or VAT ID during signup
When you sign up for a Team plan, you may have the option to enter your Tax or VAT ID depending on your location:
1. During the signup process, enter your address information.
2. If your address is eligible for tax purposes, an optional field for your Tax or VAT ID will appear.
3. Enter your Tax or VAT ID in the provided field.
4. If the ID is entered correctly, you'll be able to proceed with your signup.
**Important**: If you're signing up as a business and want to use a name other than the one tied to your payment method, an organization Owner should check the "Use a different name on invoices" box when adding or updating your payment method in **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**. Then, enter your company name in the "Bill to" field to ensure it is reflected correctly on your invoice.
## Update your tax or VAT ID after signup
**Note**: Updates to your billing details will only apply to future billing cycles. Previously completed invoices cannot be updated retroactively.
If you need to add or update your Tax or VAT ID after you've already signed up, follow these steps:
1. Navigate to your **[Billing Settings](https://claude.ai/settings/billing)**.
2. Click on the "Update" button next to your payment method.
3. In the payment update form, you should see a field to enter or update your Tax or VAT ID.
4. Enter or modify your Tax or VAT ID as needed.
5. Save your changes.
**Note:** Your billing address determines your tax jurisdiction. See **[Understanding your billing address and tax calculation](understanding-your-billing-address-and-tax-calculation.md)** for details on how to view or update your billing address.
---
## Manage custom roles on Enterprise plans | Claude Help Center
Source: https://support.claude.com/en/articles/13930452-manage-custom-roles-on-enterprise-plans
Path: 17-Billing-Plans/manage-custom-roles-on-enterprise-plans.md
# Manage custom roles on Enterprise plans
Custom roles are available for Enterprise plan organizations. Owners, Primary Owners, and custom roles with the **Identity & Access** permission set to "Can manage" can go to **[Organization settings \> Roles](https://claude.ai/admin-settings/roles)** to manage custom roles.
## What are custom roles?
Custom roles let you define which features your members can access. Each custom role contains a set of permissions that grant or restrict access to specific capabilities like chat, Claude Cowork, Claude Code, and web search, plus the connectors your organization has added, such as Slack or Google Drive.
Custom roles can also grant admin permissions, which give members access to specific administrative areas like billing, identity, or privacy without making them Owners. A custom role can also grant all of an Owner's admin permissions with the **Owner access** permission.
Custom roles work alongside groups. The typical workflow is: create custom roles, assign them to groups, and then set members' roles to “Custom” so their access is governed entirely by the custom roles assigned to their groups.
**Note:** Custom roles only affect members whose role is set to “Custom.” Members with the User, Admin, or Owner roles get their permissions from those roles directly, not from custom roles.
**Note:** With SCIM directory sync and group mappings enabled, each member’s role is owned by the sync. A member whose role was set to “Custom” before group mappings were enabled reverts to their mapped role on the next full sync unless they’re in an IdP group mapped to “Custom.” See **[Manage groups and group spend limits on Enterprise plans](manage-groups-and-group-spend-limits-on-enterprise-plans.md#h_05cb172230)**.
------------------------------------------------------------------------
## How feature access works
Feature access is determined by a four-level precedence chain, where the most restrictive level wins:
1. **Platform-level overrides**: Some features may be force-enabled or force-disabled for your organization by Anthropic as part of your contract. These can't be changed in organization settings.
2. **Organization-level setting**: An Owner or Primary Owner can toggle a feature on or off for the entire organization. If a feature is disabled at the organization level, no custom role can grant access to it.
3. **Custom role permissions**: If the feature is enabled at the organization level, the member's custom roles determine whether they can access it. If any of the member's custom roles grant the feature, they have it.
4. **User-level setting**: If the feature is granted at the role level, it's available unless the member has disabled it in their own settings.
The key takeaway: the organization-level toggle is a main switch. Custom roles are the per-member switches underneath it. A feature must be enabled at the organization level before custom roles can control who gets access.
**Note:** This precedence chain applies to capabilities. Admin permissions aren't gated by an organization-level toggle or a member's own settings. If a member's custom role grants an admin permission, they have that access.
------------------------------------------------------------------------
## Available capabilities
Each custom role can grant or restrict access to the following capabilities:
[TABLE]
\*Claude Code dynamic workflows are on for your whole organization by default. Because a single run can last for hours and use more tokens than a typical session, decide which roles should have access. For members on custom roles, this capability follows the additive model like any other—a role must grant it for those members to use it. To restrict a specific group, leave this capability off in their role.
This can be disabled organization-wide via `managed-settings.json` by adding `"disableWorkflows": true` to your managed settings.
An owner can turn it off across your entire organization by going to **[Organization settings \> Claude Code](https://claude.ai/admin-settings/claude-code)** and toggling **Workflows** off.
Custom roles also govern admin permissions, connectors, and model access, which are configured on separate **Permissions**, **Connectors**, and **Models** tabs in the role editor. See **[Admin permissions](manage-custom-roles-on-enterprise-plans.md#h_fde60b08bd)**, **[Connector permissions](manage-custom-roles-on-enterprise-plans.md#h_979e558d00)**, and **[Model access](manage-custom-roles-on-enterprise-plans.md#h_fca0f9a6b5)** below.
**Note:** Chat is enabled by default for all custom roles, including ones created before this capability was added. If you want to restrict chat for a specific role, toggle it off when editing the role.
Custom roles that already granted Claude Code have Cloud sessions and Claude Code remote control turned on, so users' access doesn't change. To restrict either one, turn it off under **Claude Code** on the role's **Capabilities** tab.
### Grant all capabilities at once
Instead of toggling capabilities individually, you can grant a role every capability. When creating or editing a role, choose an option on the **Capabilities** tab for **Capability access**:
- **All capabilities:** Grants the role every capability, including capabilities in beta and research preview.
- **All generally available:** Grants the role every generally available capability.
Roles set to either option pick up new capabilities automatically as they launch. Roles set to “Only selected” only include the capabilities you select.
------------------------------------------------------------------------
## Create a custom role
1. Navigate to **[Organization settings \> Roles](https://claude.ai/admin-settings/roles)**.
2. Click “Add role.”
3. Enter a name for the role (for example, “Developer,” “Standard Access,” or “Restricted”).
4. Select the groups you want to assign to the role.
5. Toggle each capability on or off to define what this role grants, or choose "All capabilities" or "All generally available" to grant every capability at once.
6. Configure permissions. You can choose No access, Can view, and Can manage for each admin setting.
7. Configure connectors. You can choose Always allow, Needs approval, or Blocked for all connectors, or customize per connector or connector tool.
8. Configure models. Select which models this role can use, optionally set a maximum effort level per model, and optionally choose a default model and default effort level for the role.
9. Click “Save role.”
## Edit a custom role
1. Navigate to **[Organization settings \> Roles](https://claude.ai/admin-settings/roles)**.
2. Click the role you want to edit.
3. Update the name and groups, or toggle capabilities, permissions, connectors, and models as needed.
4. Click “Save role” to save your changes.
Role changes may take up to 15 minutes to take effect, and members may need to refresh their browser. All members in groups assigned to this role are affected.
## Delete a custom role
Click the menu button on any custom role and select “Delete role.” Deleting a role removes its permissions from all groups it was assigned to. Members in those groups lose the permissions the role granted, unless another role in their chain also grants them.
------------------------------------------------------------------------
## Assign groups to custom roles
Custom roles are assigned to groups, not directly to individual members. To assign a group to a role:
1. Navigate to **[Organization settings \> Roles](https://claude.ai/admin-settings/roles)**.
2. Click the role you want to assign.
3. In the groups selector, select one or more groups.
4. Click "Save role."
You can also assign custom roles when creating or editing a group in **[Organization settings \> Groups](https://claude.ai/admin-settings/groups)**. See **[Manage groups and group spend limits on Enterprise plans](manage-groups-and-group-spend-limits-on-enterprise-plans.md)**.
------------------------------------------------------------------------
## How permissions combine across multiple roles
If a member belongs to multiple groups with different custom roles, their permissions are **additive**—they get the union of all permissions from all roles in their chain. If any role grants a feature, the member has access to it.
This means you can't use one role to remove a permission granted by another role. This is by design — it enables a layered approach where a base role covers common features and additional roles layer on specific capabilities and admin permissions.
**Example:** A member is in two groups. The "All Users" group is assigned a "Standard Access" role with web search and memory. The "Engineering" group is assigned a "Developer" role with Cowork and Claude Code. The member gets all four: web search, memory, Cowork, and Claude Code.
------------------------------------------------------------------------
## See a member or group's effective role
When a member belongs to several groups whose roles grant different capabilities, it can be hard to tell what they can actually do. The "View effective role" option shows the combined result: every capability, admin permission, and connector the member has, with the role that grants each one.
1. Navigate to **[Organization settings \> Members](https://claude.ai/admin-settings/members)** (or **[Organization settings \> Groups](https://claude.ai/admin-settings/groups)**).
2. Find the member or group and open the "⋮" menu on the right side of their row.
3. Select "View effective role."
The modal lists the member's assigned roles and three tabs:
- **Capabilities:** each capability with a "Granted by *\[role name\]*" label showing which role turned it on.
- **Permissions:** each admin permission area with its effective level (No access, Can view, or Can manage) and which role grants it.
- **Connectors:** each connector's effective permission level and which role grants it.
This view is read-only. To change what a member can do, edit the roles assigned to their groups.
**Note:** "View effective role" appears only for members whose role is set to "Custom" and who have at least one custom role assigned through a group. Members with a built-in role (User, Admin, Owner, or Primary Owner) get their permissions from that role directly, so there's nothing to compute.
------------------------------------------------------------------------
## Admin permissions
Custom roles can grant admin permissions in addition to capabilities and connector permissions. Admin permissions give members access to specific administrative areas, like billing or privacy, without making them Owners. You can configure admin permissions in the **Permissions** tab of the role editor.
**Note:** Admin permissions only apply to members whose role is set to "Custom." Members with the User, Admin, Owner, or Primary Owner roles keep the access those roles grant.
### Admin permission levels
On the **Permissions** tab, you set each permission area to one of three levels:
- **No access:** The member doesn't see this area in their organization settings.
- **Can view:** View grants read-only access. The member sees the same pages and settings as someone who can manage that area, but every control is disabled or shown as read-only. Use this permission level for compliance reviewers, finance auditors, security teams, or anyone who needs to see the configuration without changing it.
- **Can manage:** Manage grants full read and write access to the area and includes view access.
Within an area, you grant all of View or all of Manage. You can't grant or restrict individual pages or settings.
### Available admin permissions
There are eight admin permission areas:
[TABLE]
**Note:** A role with **Identity & Access** set to "Can manage" can create and edit groups and roles, including its own role definition, and can turn on Owner access. Members with this permission can expand their own access, so reserve it for trusted security and IT administrators.
### Owner access (beta)
The **Owner access** permission gives a custom role all the admin permissions of an Owner. Owners get their permissions from the Owner role directly and skip custom roles, so until now you had to choose between making someone an Owner and managing their access with custom roles. With Owner access, a user can have full admin access while their capabilities, connectors, and models are still governed by the custom roles assigned to their groups.
Owners, Primary Owners, and custom roles with **Identity & Access** set to "Can manage" can turn on Owner access. It matches the Owner role, not the Primary Owner role.
To give a role Owner access:
1. Navigate to **[Organization settings \> Roles](https://claude.ai/admin-settings/roles)**.
2. Open the role you want to edit, or click "Add role" to create one.
3. On the **Permissions** tab, turn on **Owner access**.
4. Click "Save role."
Owner access applies only to users whose role is set to "Custom" and who are in a group assigned to the role. Changing an Owner's role to "Custom" removes their built-in Owner access, so add them to the group before you change their role. If roles come from directory sync with group mappings, map the user's identity provider group to "Custom" rather than Owner.
### Available organization settings pages for each permission
[TABLE]
### What admin permissions don't cover
The following remain available only to Owners and Primary Owners, even for members with admin permissions:
- **Managing Owners and Admins.** Admin permissions can't grant or revoke the Owner, Admin, or Primary Owner built-in roles. Only Owners can manage other Owners.
- **API keys and workspaces.** API key management, workspace settings, and Claude Console administration aren't covered by admin permissions.
- **Compliance and security keys.** Compliance API settings and security-key administration remain Owner-only.
- **Organization-level capability settings.** Which capabilities are enabled at the organization level is governed separately and isn't part of admin permissions.
### What members see when admin permissions are restricted
If a member doesn’t have access to a specific admin permission, the section doesn't appear in their organization settings. Only sections their permissions cover are shown.
------------------------------------------------------------------------
## Connector permissions
Custom roles also control which connectors, and which tools on those connectors, a role can use. Where capabilities cover Claude’s built-in features, connector permissions cover the apps and services you’ve connected to your organization, such as Slack, Google Drive, or Jira. You set them on the **Connectors** tab of the role editor, next to the **Capabilities** and **Permissions** tabs.
**Note:** Connector permissions apply only to members whose role is set to “Custom.” Members with the User, Admin, or Owner roles see every connector enabled for your organization, subject to your organization-wide tool policies per connector. Owners and Admins always see every connector so they can configure it, regardless of any role’s connector permissions.
### Permission levels
On the **Connectors** tab, you set all connectors, each connector, or each tool on a connector, to one of three levels:
- **Always allow:** Every tool on the connector is available, and members can set their own approval to “Always allow” to skip the per-call confirmation.
- **Needs approval:** Every tool is available, but members confirm each call. The “Always allow” option is removed from their personal approval menu for these tools.
- **Blocked:** The connector or tool is hidden. Claude can’t see it or call it.
A connector can also be set to **Custom**, which lets you set each of its tools individually. For the full setup, see **[Set up role-based permissions on Enterprise plans](https://support.claude.com/en/articles/13930458-)**.
### How connector access is determined
A connector or tool passes through several layers before a member can use it, evaluated in this order:
1. **Role grant.** Each connector or tool on a role is set to “Always allow,” “Needs approval,” or “Blocked.”
2. **Across the member’s roles.** If a member’s groups give them more than one role, the most permissive grant for each tool applies. Connector permissions are additive across roles, the same as capabilities.
3. **Organization-wide tool policy.** The per-tool policy you set under **[Organization settings \> Connectors](https://claude.ai/admin-settings/connectors)** per connector is the ceiling. For each tool, Claude compares the member’s role grant to this policy and applies the stricter of the two. Role grants narrow access within the policy; they can’t widen past it. Learn more about setting tool access in **[Use connectors to extend Claude’s capabilities](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities)**.
4. **The member’s own setting.** The result of the steps above is the member’s effective ceiling. It limits the options in their personal per-tool approval menu (“Always allow,” “Ask,” or “Never”). A ceiling of “Needs approval” removes “Always allow.” A ceiling of “Blocked” grays the tool out.
For members using Claude Code, one more layer applies: Managed Settings policies and connector permissions compose by most-restrictive. A tool is callable without a prompt only when both allow it. For more information, see **[Claude Code settings](../02-Claude-Code-CLI/settings.md#settings-files)**.
For members using Claude Cowork, write-capable connector tools pass through one more gate. See **[Cowork approval setting for write tools](manage-custom-roles-on-enterprise-plans.md#h_85bd7c30e9)** below.
This table shows how the organization-wide tool policy and a member’s role grant combine:
[TABLE]
### Cowork approval setting for write tools
Claude Cowork has a separate organization setting, **Allow "Always allow" for connector tools**, that gates write-capable connector tools. It's off by default, and custom role grants can't override it: even when the organization-wide tool policy and every role grant are set to "Always allow," members approve these tools per task in Cowork until the setting is turned on. Learn more about **[connector tool approvals in Cowork](https://support.claude.com/en/articles/13455879-use-claude-cowork-on-team-and-enterprise-plans#h_1bd1fa754d)**.
### Where connector permissions apply
Connector permissions are enforced on Anthropic’s servers, so they apply across every Claude surface that routes connector traffic through Anthropic:
[TABLE]
Connector permissions govern connectors your organization has added under **[Organization settings \> Connectors](https://claude.ai/admin-settings/connectors)**. They don’t govern connectors a member runs locally on their own machine, and they don’t govern Claude Cowork when it’s deployed on a third-party platform. For third-party Cowork deployments, use MDM instead. See **[Cowork on 3P: MCP, plugins, skills, and hooks](https://claude.com/docs/cowork/3p/extensions).**
### What members see when a connector is restricted
[TABLE]
Members can’t tell which layer restricted a tool. The message is the same whether the limit comes from the organization-wide tool policy, a role grant, or both. To find the source, compare the organization-wide policy with the member’s role grants.
------------------------------------------------------------------------
## Model access
Custom roles also control which Claude models a role can use and the maximum effort level members can select on each one. You set these on the **Models** tab of the role editor, alongside the role's default model and default effort level.
The organization-level model setting is the ceiling. A role can't grant a model that's disabled at the organization level. Across a member's roles, model access is additive and effort limits take the highest cap any role allows. Haiku models are always available and can't be disabled.
For setup steps and what members see, see **[Manage model access for your organization](https://support.claude.com/en/articles/15694740)**. For default model behavior, see **[Set a default model for your organization](https://support.claude.com/en/articles/15330088)**.
------------------------------------------------------------------------
## What members see when capability access is restricted
When a capability is restricted, here’s what members see. For connector and tool restrictions, see **[Connector permissions](manage-custom-roles-on-enterprise-plans.md#h_979e558d00)** above.
[TABLE]
---
## Manage groups and group spend limits on Enterprise plans | Claude Help Center
Source: https://support.claude.com/en/articles/13799932-manage-groups-and-group-spend-limits-on-enterprise-plans
Path: 17-Billing-Plans/manage-groups-and-group-spend-limits-on-enterprise-plans.md
# Manage groups and group spend limits on Enterprise plans
Groups and group spend limits are available for Enterprise plan organizations. Owners, Primary Owners, and custom roles with the **Identity & Access** permission set to "Can manage" can go to **[Organization settings \> Groups](https://claude.ai/admin-settings/groups)** to manage groups. Owners, Primary Owners, and custom roles with the **Billing** permission set to "Can manage" can go to **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)** to manage group spend limits.
## What are groups?
Groups let you organize members into logical collections—by team, department, or any other grouping that fits your organization. Once groups are set up, you can:
- **Set spend limits for groups**, so all members of a group share a per-user spend limit, and optionally give the group one shared monthly budget (beta).
- **Control member access through group memberships and custom roles**, so their capabilities and permissions are determined entirely by the groups they belong to. For additional details, see **[Manage custom roles on Enterprise plans](manage-custom-roles-on-enterprise-plans.md)**.
- **Let members share resources with a group**, so a project, skill, or plugin shared with the group is available to everyone in it, and access follows membership as it changes. For details, see **[Manage project visibility and sharing](https://support.claude.com/en/articles/9519189-manage-project-visibility-and-sharing)** and **[Provision and manage skills for your organization](https://support.claude.com/en/articles/13119606-provision-and-manage-skills-for-your-organization)**.
Groups can be created manually or synced automatically from your identity provider via SCIM. Each organization can have up to 1000 groups. There's no limit on how many groups a member can belong to, though belonging to more than 250 can slow performance.
In addition to spend limits, Enterprise admins can use groups to control plugin access in chat, Cowork, and Claude Code. Each plugin in your organization's marketplace can have group-level overrides that set it to "Available to install," "Installed by default," "Required," or "Not available" for members of a specific group. For details, see **[Manage plugins for your organization](https://support.claude.com/en/articles/13837433-manage-cowork-plugins-for-your-organization)**.
------------------------------------------------------------------------
## Create a group
1. Navigate to **[Organization settings \> Groups](https://claude.ai/admin-settings/groups)**.
2. Click "Add group."
3. Enter a **Group name**.
4. Optionally enter a **Display name**. The display name replaces the group name on in-product surfaces, like the project sharing picker. Leave it blank to use the group name.
5. Select which custom roles to assign to this group (optional).
6. Under **Visibility settings**, choose who can discover the group, share resources like projects with it, and see its members (optional).
7. Search for and add members, or click "Add all members" to add everyone in your organization.
8. Click "Add group."
**Note:** If SCIM directory sync is enabled, you’ll see a “SCIM Sync” button next to "Add group." Clicking this will manually refresh groups from your identity provider.
## Edit a group
Click any group in the list to open its edit form. You can change the group name and display name, update custom role assignments, change visibility settings, and add or remove members.
To change settings for several groups at once, select them with the checkboxes in the groups list, then click the "Edit settings" button that appears.
**Note:** Groups synced from your identity provider via SCIM can't be renamed or deleted in Claude, and their members are managed in your identity provider.
## Delete a group
Click the menu button to the right of any group and select "Delete." Deleting a group doesn't affect the custom roles that were assigned to it and doesn't remove any members from your organization. Deleting a group also removes its access to any projects shared with it. Members lose access to those projects unless they have access another way.
------------------------------------------------------------------------
## SCIM group sync
If your organization uses SCIM directory sync, groups from your identity provider are automatically synced to Claude. SCIM groups appear with a sync indicator in the groups list.
SCIM groups support custom role assignments and spend limits the same way as manually created groups.
To manually trigger a sync, click “SCIM Sync."
**Note:** Claude supports direct group memberships only. If your identity provider nests groups inside other groups, those relationships are ignored when memberships are pushed via SCIM, and only direct members appear in Claude. Some providers flatten nested memberships before pushing them, which makes members of child groups appear as direct members. Check your provider's SCIM behavior to confirm.
------------------------------------------------------------------------
## Group visibility
By default, groups appear only on admin surfaces. Visibility settings let you make a group discoverable to members so they can share resources (like projects, skills, or plugins) with it. You set them in the **Visibility settings** section when creating or editing a group.
There are three settings:
- **Discover this group:** Members can find the group by name. This doesn't expose group members, spend limits, or role assignments.
- **Share resources with this group:** Members can share resources, such as projects, skills, and plugins, with the group.
- **See group members:** Members can see who belongs to the group, by name and email address.
For each setting, select **Group members** to grant it to members of that group, or **Everyone** to grant it to everyone in your organization. Leave both unchecked to keep the setting off.
Visibility settings don't affect admin access. Owners, Primary Owners, and custom roles with **Identity & Access** access always see every group.
The **Visibility** column in the groups list shows each group's current state. New visibility settings can take a few minutes to appear in-app.
**Important:** Visibility settings are configured per organization. Groups, group membership, and SCIM sync are managed at the parent organization level and shared across child organizations, but visibility settings aren't. An admin changing visibility settings in one organization doesn't affect any other organization.
### Remove a group's access to shared projects, skills, and plugins
Turning off **Share resources with this group** blocks new shares. It doesn't revoke projects already shared with the group. To revoke those:
1. Open the group's edit form.
2. Under **Visibility settings**, select "Remove this group's access to all \[number\] projects."
3. Save the group.
This revokes existing shares only. It doesn't block future sharing, so turn off **Share resources with this group** as well if you want both.
**Note:** Removing a group's access runs in the background. For groups with more than 1000 shared projects, it can take several minutes or longer.
------------------------------------------------------------------------
## Control member access with custom roles
You can control individual members' feature access entirely through groups and custom roles. When a member's role is set to **Custom**, they have no default capabilities or permissions—their access is determined entirely by the custom roles assigned to their groups. This is different from the User, Admin, or Owner roles, which include built-in permissions.
### Set a member's role to Custom
1. Navigate to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
2. Find the member and click their role dropdown.
3. Select "Custom."
Owners, Primary Owners, and custom roles with the **User Management** permission set to "Can manage" can change member roles. You can also assign “Custom” at scale by mapping an IdP group using **[group mappings](https://support.claude.com/en/articles/13133195-set-up-jit-or-scim-provisioning)**.
**Important:** If your provisioning mode is SCIM directory sync and group mappings are enabled, each member’s role is set by your IdP group-to-role mapping and managed by the sync, not by the **Members** page. A role that was set to “Custom” before you enabled group mappings (or set another way) is recalculated on the next full sync and reverts to the mapped role. It works until that sync runs, and the reversion isn’t recorded in the audit log, so it can look like custom role permissions stopped applying for no reason.
To keep a member on “Custom,” add them to an IdP group that’s mapped to the “Custom” role in **[Organization settings \> Organization and access](https://claude.ai/admin-settings/organization)**, then run a sync. See **[Set up JIT or SCIM provisioning](https://support.claude.com/en/articles/13133195-set-up-jit-or-scim-provisioning)** and **[How SCIM sync works for Enterprise organizations](../13-Enterprise-Admin/how-scim-sync-works-for-enterprise-organizations.md)**.
### Recommended setup
1. Create custom roles with the desired permissions in **[Organization settings \> Roles](https://claude.ai/admin-settings/roles)**. For details, see **[Manage custom roles on Enterprise plans](https://support.claude.com/en/articles/13930452)**.
2. Create groups in **[Organization settings \> Groups](https://claude.ai/admin-settings/groups)** (or sync them from your identity provider).
3. Assign custom roles to groups.
4. Add members to the appropriate groups.
1. **Note:** If a member set to a Custom role isn't in any groups, or their groups have no custom roles assigned, they have no permissions and can't access any products. They'll land on their settings page when they sign in.
5. Set each member's organization role to **Custom**.
6. Enable any features at the organization level that you want to control per-group.
The member's effective permissions are now determined by their group memberships and the custom roles assigned to those groups.
**Important:** Always complete steps 1–5 before enabling features at the organization level (step 6). If you enable a feature before changing members' roles to Custom and assigning appropriate custom roles, there's a brief window where some members could access the feature through their previous role. For a detailed walkthrough, see **[Set up role-based permissions on Enterprise plans](set-up-role-based-entitlements-on-enterprise-plans.md)**.
### Invite new members
When inviting a new member, Owners, Primary Owners, and custom roles with the **User Management** permission set to "Can manage" can select "Custom” as the role.The new member's access is determined by their group memberships after they join.
------------------------------------------------------------------------
## Group spend limits
Group spend limits let you control spending across your organization by assigning per-user monthly spend limits to groups. Instead of setting spend limits for each member individually, you can set a limit on a group and have it apply to every member of that group.
Group spend limits work alongside individual spend limits. If a member has an individual spend limit set, their individual limit takes precedence over any group limit.
A pooled budget only starts counting spend after it is created and resets each month.
### Set a group spend limit
1. Navigate to **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**.
2. Select the "By group/tier" tab.
3. Find the group and click the menu button to the right, then "Edit limits."
4. Select "No member limit" or "Member limit" and enter an amount.
5. Click "Save."
The spend limit applies to all members of the group. Members who also have an individual spend limit set are governed by their individual limit instead.
### Choose how multi-group spend limits resolve
If a member belongs to more than one group with a spend limit, the **Multi-group spend limit** setting controls which limit applies.
1. Navigate to **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**.
2. Find **Member limit** from groups in the **Spending defaults** section.
3. Select "Higher group limit" or "Lower group limit" from the dropdown.
Select "Lower group limit" to set a broad limit on a large group and create subgroups with tighter budgets. Select "Higher group limit" to set a conservative baseline on a large group and grant more headroom to specific teams.
### How spend limits are resolved
When determining a member's effective spend limit, the system evaluates in this order:
1. **Individual limit**—if the member has an individual spend limit set, that limit applies regardless of group membership.
2. **Group limit**—if the member has no individual limit, the system checks their group memberships. If the member belongs to multiple groups with spend limits, your **Multi-group spend limit** setting determines whether the higher or lower limit applies.
3. **No limit**—if the member has no individual limit and belongs to no groups with spend limits, no spend limit is applied.
For a view of how spend limits are affecting your organization, see the **Blocked by a spend limit** section at the top of **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**. **Blocked by a spend limit** is built for usage-based Enterprise plans. Orgs without usage-based seats only see how many members are blocked or near their limit right now. Learn more about **[monitoring usage and spend on Enterprise plans](how-am-i-billed-for-my-enterprise-plan.md#h_ae17ec8236)**.
---
## Manage pooled group budgets on Enterprise plans | Claude Help Center
Source: https://support.claude.com/en/articles/17005973-manage-pooled-group-budgets-on-enterprise-plans
Path: 17-Billing-Plans/manage-pooled-group-budgets-on-enterprise-plans.md
# Manage pooled group budgets on Enterprise plans
A pooled group budget gives a group one shared monthly amount that all its members draw from, on top of each user's own monthly spend limit. This article explains how pooled budgets work and how to set, prioritize, and monitor them.
Pooled group budgets are in beta for Enterprise plan organizations. Primary Owners, Owners, and custom roles with the **Billing** permission set to "Can manage" can set pooled budgets in **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**. To share feedback on the beta, contact your Anthropic account team.
## How pooled budgets work
A group spend limit applies to each group member separately, so every member gets the same monthly limit. A pooled budget adds one shared amount for the whole group.
Every request counts against both the user's own monthly spend limit and the group's pooled budget. The user stops when their own limit runs out, or when every pooled budget they can use is used up. When the pooled budget is used up, usage pauses for every member of the group until you raise the budget or it resets for the new month. After you raise it, group members can send messages again right away.
**Note:** A pooled budget isn't an equal share for each person. If you set the member monthly limit to the pooled budget divided by the number of group members, you're back to one-person limits and lose the benefit of a shared budget. Set the member monthly limit as a guard rail against unusually high use by one person.
## Before you start
Check the following before you set a pooled budget:
- The group exists in **[Organization settings \> Groups](https://claude.ai/admin-settings/groups)**. Learn more about **[managing groups and group spend limits on Enterprise plans](https://support.claude.com/en/articles/13799932)**.
- The group has a monthly spend limit. A pooled budget sits on top of this limit.
- You've picked a group to start with. A single team with a clear owner is a good first choice.
## Choose starting amounts
Base your first amounts on last month's actual spend, not an estimate. You need two numbers for the group. Editing limits for a group suggests these automatically. You can also verify them in **Analytics**:
- **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:** The first row when you sort that table by spend.
A good starting point is a pooled budget of about three times last month's group spend, and a member monthly limit of about three times the top spender's spend.
For example, if a group spent \$1450 last month and its top spender used \$310, set the pooled budget to \$2900 and the member monthly limit to about \$950. With these amounts, requests for more should be rare and the pooled budget should last the month.
## Set a pooled budget
Set the pooled budget and the member monthly limit together from the group's row in the spend limits table.
1. Navigate to **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**.
2. Scroll to **Spend limits** and select the "By group/tier" tab.
3. Find the group, click the menu button to the right, and select "Edit limits."
4. Under **Pooled monthly budget**, select "Set amount." A suggested amount based on the group's recent usage is filled in, and you can change it.
5. Under **Member monthly limit**, click "Use" to apply the suggested limit, or enter your own.
6. Click "Save."
If the member monthly limit is too low for the pooled budget, you'll see a warning with an option to raise it.
## Change, freeze, or turn off a pooled budget
- **Change the amount:** Select "Edit limits" in the group's row menu and enter a new amount.
- **Freeze the group:** Set the pooled budget to \$0. Group members can no longer spend from this pooled budget.
- **Pause the pooled budget:** Select "Paused." The amount is kept but not enforced until you select "Set amount" again. To remove the pool, select "No pooled budget."
- **Remove the group's spend limit:** This also removes the group's pooled budget.
## Set the budget priority for users in several groups
If a user belongs to more than one group with a pooled budget, the largest pooled budget pays first by default. When it is used up, the next largest with usage remaining pays. To choose the order yourself:
1. Navigate to **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**.
2. In the **Pooled budget priority** card, select "Custom order."
3. Use the arrows to put the groups in order, with the most specific team first.
4. Click "Save order."
With a custom order, the first pooled budget in your list with budget remaining pays.
**Note:** Budget priority only decides the order in which pooled budgets pay. To choose which group's member monthly limit applies to a user in more than one group, use the **Member limit from groups** setting under **Spending defaults**.
## Monitor pooled budgets
Check pooled budget usage at any time in the **Pooled budget** column on the "By group/tier" tab in **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**. The column shows each group's pooled budget and how much of it has been used this month. The bar turns amber at 75% and red at 90%. A dash means the group has no pooled budget.
When a pooled budget reaches 50%, 75%, 95%, and 100% of its monthly amount, everyone with the Billing permission gets an email, and a notice for the group appears on the admin home page. Click "View group" in the notice to go to the group's row, then dismiss the notice once you've acted on it.
To tell whether your amounts are right, also check the number of requests under **Review requests**. If a pooled budget is 75% used before the 20th of the month, consider raising it by 50%. If users keep requesting more, raise the member monthly limit.
## What users see
Nothing changes for users until they reach their own monthly spend limit or until every pooled budget they can use is used up. At that point, a message appears in the message box with a "Request more" button. If the pooled budget is used up, the message says their team's shared budget has run out.
Requests from users appear under **Review requests**. Users never see the group's name or the pooled budget amount.
## Beta limitations
- The **Billing** permission applies across your whole organization, so anyone who can edit one group's pooled budget can edit every group's pooled budget.
- Pooled budgets can only be managed in **Organization settings**. They aren't available through the Admin API.
---
## Manage members on Team and Enterprise plans | Claude Help Center
Source: https://support.claude.com/en/articles/13133750-managing-members-on-team-and-enterprise-plans
Path: 17-Billing-Plans/managing-members-on-team-and-enterprise-plans.md
# Manage members on Team and Enterprise plans
This guide covers how to add, remove, and manage the people on your Team or Enterprise plan.
**Permissions note:** Organization Admins can manage members in **[Organization settings \> Members](https://claude.ai/admin-settings/members)**, but only Owners and Primary Owners can access **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**. For more information, see our article about **[roles and permissions](../13-Enterprise-Admin/roles-and-permissions.md)**.
For information on purchasing seats or adjusting your plan's seat allocation, see our guides for **[Team plans](https://support.claude.com/en/articles/12004354-purchasing-and-managing-seats)** and **[Enterprise plans](purchasing-and-managing-seats-on-enterprise-plans.md)**.
------------------------------------------------------------------------
## Add members
### Add members by invitation
**Note:** Pending invitations occupy your available seats immediately; a new member does not need to accept the invite to take up a seat.
Admins and above can add members by following these steps:
1. Navigate to **[Organization settings \> Members](https://claude.ai/admin-settings/members)** and click “Add member.”
2. Enter the person's email address (it must use one of your organization's **[allowed email domains](../21-Account-Support/account-management-faqs.md#h_b54c41c86c)**).
3. Select the appropriate seat type.
4. Set the role and permissions for the member.
1. **Note:** On Enterprise plans, you can also select “Custom” as a member’s role. Members set to this role have their access controlled through group memberships and custom roles. To see exactly what a custom role member can access, open the “**⋮**” menu on the right side of their row and select "View effective role." For details, see **[Manage custom roles on Enterprise plans](manage-custom-roles-on-enterprise-plans.md)**.
5. Click “Add members.”
This sends an email invitation to the person. The invitation expires after 21 days, so you'll need to re-invite them if they don't accept within that time period.
**Add multiple members at once:** You can invite multiple members by clicking "Bulk add" and typing or pasting email addresses separated by commas or new lines.
**Note:** The seat type selector only shows seat types your plan already owns. If all seats of the selected type are assigned, you'll be prompted to purchase one. See our guides for **[Team plans](https://support.claude.com/en/articles/12004354)** and **[Enterprise plans](https://support.claude.com/en/articles/13393991)** for more information.
### Add members via organization discovery
Members can also join your organization on their own through organization discovery. When you enable discoverability, colleagues with a matching email domain can find your organization during signup and request to join—no invitation needed. You can configure whether they're added automatically or require your approval. See **[Find and join a Team or Enterprise organization](https://support.claude.com/en/articles/13566435-organization-discovery)** for details.
### Share an invite link
Admins and above can generate a shareable invite link and distribute it to teammates—for example, by posting it in a Slack channel, email thread, or team wiki—without needing to enter individual email addresses.
**Availability:**
- **Team plans:** Invite links are enabled by default for new organizations.
- **Enterprise plans (non-SSO):** Invite links are disabled by default. Admins can enable them in **[Organization settings \> Organization and access](https://claude.ai/admin-settings/organization)**.
- **SSO organizations:** Invite links are not available. Member provisioning is managed through your Identity Provider.
To find and copy your invite link, navigate to **[Organization settings \> Organization and access](https://claude.ai/admin-settings/organization)**. New members who join via link are assigned to the lowest available seat tier, defaulting to a standard seat if none are available.
Admins can disable the link at any time—this immediately invalidates all existing links. Regenerating the link also invalidates the previous one.
For more details on how the joining flow works, see **[Join an organization via invite link](../13-Enterprise-Admin/join-an-organization-via-invite-link.md)**.
### Automated provisioning with SSO
Organizations with single sign-on (SSO) configured can automate member provisioning. Learn more about **[setting up SSO](https://support.claude.com/en/articles/13132885-setting-up-single-sign-on-sso-for-claude-and-claude-console)**.
- **Just-in-time (JIT) provisioning:** Members assigned to the Anthropic app in your Identity Provider will have accounts created automatically the first time they log in. On plans with multiple seat types, users are assigned to the highest-available seat type upon first login. On single-seat Enterprise plans, users are automatically assigned the Enterprise seat. Admins and above can manually reassign seat types afterward in **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
- **SCIM provisioning (Enterprise plan only):** With SCIM directory sync enabled, members assigned to the Anthropic app in your Identity Provider are provisioned automatically, up to the number of total seats on your plan. On plans with multiple seat types, seat types are distributed from highest to lowest available. On single-seat Enterprise plans, all users are automatically assigned the Enterprise seat. Admins and above can manually reassign seat types afterward in **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
**Important:** An Owner or Primary Owner must ensure seats are available before new users can be provisioned. We recommend monitoring your seat usage and adding seats proactively to ensure uninterrupted access for your team. You can **[enable group mappings with JIT or SCIM](https://support.claude.com/en/articles/13133195-setting-up-jit-or-scim-provisioning#h_adee31eeba) to provision users directly to a specific role and seat tier**.
------------------------------------------------------------------------
## Member-to-member invites
Organization members can invite teammates by email, even if they aren't admins. This makes it easier for your team to grow organically without requiring admin involvement for every new member.
### How it works
Any member can access the invite flow from the account selector in Claude. They enter a teammate's email address and submit the invite. What happens next depends on your organization's new member approval setting:
- **Approve one-by-one (default):** The invite request goes to an admin for review. The invite is only sent to the teammate after an admin approves it.
- **Approve automatically:** The invite is sent right away and the invitee can join immediately.
Invites sent by members follow the same domain restrictions as other join methods — the invitee's email must match one of your organization's allowed domains.
### Availability
- **Team plans:** Member-to-member invites are enabled by default for new organizations.
- **Enterprise plans:** Member-to-member invites are disabled by default. Admins can enable them from Admin settings.
### Admin controls
Admins can enable or disable member-to-member invites from the admin settings. When disabled, only admins can send invitations. Invitees added through member invites are assigned the default member role and placed in the lowest available seat tier.
------------------------------------------------------------------------
## Remove members
You can remove a member by navigating to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**, clicking the menu button to the right of the member, then selecting "Remove from team." However, if you are an Owner or Primary Owner, you can't remove yourself from your organization. Another Primary Owner or Owner must remove you from the team.
For Enterprise organizations using SCIM provisioning, members are automatically removed from Claude when they are removed from your Identity Provider.
When a member is removed:
- They lose access to the organization immediately.
- The seat they occupied becomes available to assign to another user.
- If you re-add the member later using the same email address, their account history will be maintained.
Removing a member frees up their seat for reassignment, but does not automatically reduce your plan's total seat count. See our guides for **[Team plans](https://support.claude.com/en/articles/12004354-purchasing-and-managing-seats)** and **[Enterprise plans](purchasing-and-managing-seats-on-enterprise-plans.md)** for information on reducing seats.
**Note:** If you're on a Team plan, the option to remove members from **[Organization settings \> Members](https://claude.ai/admin-settings/members)** will no longer be available after you cancel your plan. For more information, see **[Cancel your organization's Team plan subscription](https://support.claude.com/en/articles/9267323)**.
------------------------------------------------------------------------
## Export member data
Admins and above can export a CSV of your organization's current member list from your organization settings.
The export includes member details such as name, email address, role, and seat type. This is useful for auditing membership, reconciling seat usage, or maintaining an external record of your team.
To export:
1. Navigate to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
2. Click the "Export CSV" button at the top of the **Members** section.
3. A CSV file will download to your device.
------------------------------------------------------------------------
## Manage invitations
### Resend an expired invitation
You can resend an invite from **[Organization settings \> Members](https://claude.ai/admin-settings/members)**. Click the “Pending” tab, find the member, and select to resend the invite.
### Revoke a pending invitation
You can revoke a pending invite from **[Organization settings \> Members](https://claude.ai/admin-settings/members)**. Click the “Pending” tab, find the member, and select "Remove from team."
------------------------------------------------------------------------
## Frequently asked questions
### Can I invite someone who already uses Claude personally with their work email?
Yes. Once they join your team, they'll have both a personal account and a Team or Enterprise plan account. They can toggle between accounts through the menu by clicking their initials or name in the lower left corner.
### How do I add a member that I previously removed?
To add a member that you previously removed, follow the same steps as adding a new member. Their account history will be maintained.
### How do I change the Primary Owner?
The current Primary Owner can transfer ownership by:
1. Navigate to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
2. Click the Role dropdown next to the new user and select "Primary Owner."
3. Type the new Primary Owner's email address in the modal to confirm and transfer ownership.
**Important:** There can only be one Primary Owner per organization. Following these steps transfers the role to a different user.
### What happens to the initial invitation for a new Enterprise organization?
When Anthropic provides a new Enterprise organization and invites the Primary Owner, the same 21-day expiration period applies to that initial invitation. If your invitation has expired, please reach out to your account manager.
### How can I check whether my seat is Standard or Premium?
Only Admins and above can see seat types, in the **Tier** column in **[Organization settings \> Members](https://claude.ai/admin-settings/members)**. If you don’t have an Admin, Owner, or Primary Owner role, you can’t see your own seat type in Claude. To confirm your seat type, ask an Owner or Admin in your organization.
---
## Manage user feedback settings on Team and Enterprise plans | Claude Help Center
Source: https://support.claude.com/en/articles/10504844-managing-user-feedback-settings-on-team-and-enterprise-plans
Path: 17-Billing-Plans/managing-user-feedback-settings-on-team-and-enterprise-plans.md
# Manage user feedback settings on Team and Enterprise plans
March 16, 2026
As a Primary Owner or Owner of a Team or Enterprise plan, you can manage the ability for members of your organization to submit feedback to Anthropic via thumbs up / thumbs down.
1. Navigate to **[Organization settings \> Data and Privacy](https://claude.ai/admin-settings/data-privacy-controls).**
2. Use the toggle to change the **Rate chats** setting for your organization:
More information on how Anthropic collects, uses, and stores feedback data can be found in our Privacy Center: **[How long do you store my organization’s data?](https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data)**
---
## Monthly API credits for Max and Team plans | Claude Help Center
Source: https://support.claude.com/en/articles/17154008-monthly-api-credits-for-max-and-team-plans
Path: 17-Billing-Plans/monthly-api-credits-for-max-and-team-plans.md
# Monthly API credits for Max and Team plans
Max and Team plans include monthly credits for the Claude Platform. Use them to build Claude into your own apps and agents with the Claude API. This article explains who's eligible, how to claim your credit, what it covers, and what happens when it runs out.
Available on Max and Team plans, including discounted Team plans. Free, Pro, and Enterprise plans aren't eligible.
## Monthly credits by plan
[TABLE]
\*On Team plans, credits for all seats are pooled into one monthly balance, capped at \$500. For example, a team with three Standard seats and two Premium seats receives \$260 a month. The pool is calculated from the seats on the plan when the credits are granted.
## Eligibility
- **Active plan.** Your Max or Team subscription must be active and in good standing.
- **Seven days on the plan.** New subscribers can claim once they've been on an eligible plan for seven days.
- **Mobile subscriptions.** You can subscribe on the web, iOS, or Android. Claim your credits on claude.ai in a web browser.
- **No payment method needed.** You don't need to add a card on Claude Platform to claim or use the credit.
## How to claim your credit
To claim your credit, you link a Claude Console organization to your plan. Credits go to that organization each month.
Before you begin, you need:
- **On your Claude plan:** Max: be the subscriber. Team: be a Primary Owner or Owner
- **In the Console organization:** the Owner, Admin, or Billing role. If you don't have a Console organization yet, you can create one during the claim flow or at **[platform.claude.com](../04-API-Reference/Other/playground.md)**.
To claim your credit:
1. On claude.ai, go to **[Settings \> Billing](https://claude.ai/settings/billing)** as a Max subscriber or **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)** as a Team Owner or Primary Owner.
2. In the **API credits** section, select "Link organization."
3. Choose the Console organization you want to receive the credits, or create a new one.
4. Review the **[Supplemental Credit Terms](https://www.anthropic.com/legal/credit-terms)**, then Link organization.
Your credits appear in that organization's balance, ready to use.
**Important:** You can link only one Console organization, and each Console organization can receive credits from only one plan. You can't change the linked organization yourself, so choose the one you plan to build in. To change it later, **[contact support](../15-Claude-AI-Features/how-to-get-support.md)**.
**Tip:** Sign in to the Claude Console with the same email you use on claude.ai. If you’re seeing errors during the linking flow, please try again in a few hours.
## What the credits cover
The credits work with any available Claude model on the Claude Platform, including:
- The Claude API (Messages API and Message Batches API)
- The Playground in the Claude Console
- Claude Managed Agents
- The Claude Agent SDK
The credits don’t apply to:
- Interactive Claude Code in the terminal, IDE, desktop, or web
- Extra usage in Claude, Claude Code, or Claude Cowork
- Claude on Amazon Bedrock, Google Cloud Vertex AI, or Microsoft Foundry
## How the credits work
- **Refreshes each billing cycle.** New credits arrive shortly after your plan payment goes through. On annual plans, credits arrive monthly.
- **Doesn't roll over.** Unused credits expire at the end of each billing cycle.
- **Used first.** Your monthly credits are spent before any credits you've purchased.
- **Shared across the organization.** Everyone with an API key in the linked organization draws from the same balance.
- **Separate from your plan limits.** The credits don’t change your usage limits in Claude, Claude Code, or Claude Cowork.
- **Visible in the Console.** All credits appear on the **Billing** page (platform.claude.com/settings/billing) in the Claude Console with their amount and expiry date.
## What happens when your credits run out
- **If the organization has purchased credits or auto-reload,** usage continues and draws from those.
- **If the organization has no other credits,** API requests stop until your next monthly credits arrive. Usage is never charged to your Claude plan. To keep going, buy credits or turn on auto-reload in the Console.
- **If your organization is invoiced through Anthropic sales,** usage beyond the credits is billed as usual.
## If your plan changes
- **Cancel, downgrade to an ineligible plan, or refund.** New credits stop. Credits you already have stay usable until they expire.
- **Upgrade from Max 5x to Max 20x.** You receive prorated credits right away, then \$200 each billing cycle after that.
- **Move from Max to Team.** Your Max link ends. A Team Owner or Primary Owner can claim the team's credits once the Team plan has been active for seven days.
## For Team Owners and Primary Owners
**One claim for the whole team.** One owner links a Console organization and claims the pooled credit, up to \$500 a month.
**The pool follows your seat count.** It's calculated from the seats on your plan each time credits are deposited. For example, a team with three Standard seats and two Premium seats receives \$260 a month. Adding another Premium seat would increase the next cycle’s credits to \$360.
**Control who spends it.** Everyone with an API key in the linked organization can use the balance. To limit usage by project or teammate, set **[workspace spend limits](../04-API-Reference/Endpoints/rate-limits.md#setting-lower-limits-for-workspaces)** in the Console.
------------------------------------------------------------------------
## Frequently asked questions
### Why can't I use the credits for Claude Code?
The credits are for building your own apps and agents on the Claude Platform. They don't cover interactive Claude Code sessions or extra usage after you hit your plan's limits.
### Why don't I see the offer yet?
We’re rolling out API credits over a few days so we might not have gotten to you yet. The offer appears after you've been on an eligible plan for seven days. If you're past seven days and still don't see it, check that you're on a Max or Team plan and that you have one of the required roles. If you think you should be eligible but don’t see the API credits, **[contact support](../15-Claude-AI-Features/how-to-get-support.md)**.
### Is this the same as the Agent SDK credits announced in June?
No. That credit isn't available. API credits cover the Claude API, Claude Managed Agents, and the Claude Agent SDK, and you claim it into a Console organization.
### Can I split my credits across multiple organizations?
No. Credits go to a single Console organization.
### I'm on a Pro plan. Can I get this credit?
No. The credits are available on Max and Team plans only.
### Does this cover `claude -p` ?
API credits cover `claude -p` and the Claude Agent SDK when you run them yourself with an API key from your linked Claude Console organization, because that usage is billed as Agent SDK usage. When you're signed in with your Claude plan instead, `claude -p` and Agent SDK usage still draw from your plan's usage limits and don't use your API credits. Runs started by the Claude Code GitHub Action, an IDE extension or the Claude desktop app count as Claude Code usage, so API credits don't cover them, even with `-p`.
---
## Notice regarding consumption tax (JCT) for Japanese customers | Claude Help Center
Source: https://support.claude.com/en/articles/14051822-notice-regarding-consumption-tax-jct-for-japanese-customers
Path: 17-Billing-Plans/notice-regarding-consumption-tax-jct-for-japanese-customers.md
# Notice regarding consumption tax (JCT) for Japanese customers
March 16, 2026
## Consumption tax
Effective April 1, 2026, Anthropic will be levying a separate consumption tax (JCT) of 10% on services provided to Japanese customers in accordance with Japanese consumption tax law. Anthropic has completed registration as a qualified invoice issuing business.
## Price impact
Starting April 1, 2026, 10% consumption tax will be added to all plan prices.
## Frequently asked questions
### Why is sales tax added?
Under Japan's Consumption Tax Act, digital service providers from overseas are required to tax Japanese customers. Anthropic has complied with this legal obligation and has completed registration as a qualified invoice issuing business. This allows corporate customers to claim input tax credits.
### I am a corporation. Can I collect consumption tax?
Yes. Corporate customers who are subject to consumption tax can receive input tax credits by using qualified invoices issued by Anthropic. Please contact your tax representative for details.
### What is Anthropic's Qualified Billing Business Registration Number?
The registration number is T7700150134388. You can check it on the National Tax Agency's "Qualified Invoice Issuer Publication Site."
### Will the billing currency change?
No. Your billing currency remains unchanged. The JCT amount will be shown in Japanese Yen (JPY) on your Tax Qualified Invoice.
### What if it is for personal use?
Individual customers cannot receive input tax credits. They will be responsible for the consumption tax. This is the same as other services in Japan.
### When will this be applied?
Starting April 1, 2026. Consumption tax will be applied to all invoices from that date onwards.
### Who should I contact for inquiries?
Please contact us using the details below depending on the nature of your inquiry.
[TABLE]
---
## Paid plan billing FAQs | Claude Help Center
Source: https://support.claude.com/en/articles/8325618-paid-plan-billing-faqs
Path: 17-Billing-Plans/paid-plan-billing-faqs.md
# Paid plan billing FAQs
This article covers Pro and Max subscriptions purchased on the web. If you subscribed through Claude for iOS or Claude for Android, your payment is handled by the Apple App Store or Google Play, and you'll manage your payment method and receipts through your app store account. To cancel or manage an app store subscription, see **[Cancel your Pro or Max subscription](https://support.claude.com/en/articles/8325617)**.
## Where can I find the invoice or receipt for my Pro or Max plan payment?
If you are subscribed to a paid plan (Pro or Max), follow these steps to access your invoices:
1. Click on your initials or name in the lower left corner and select “Settings” from the menu.
2. Navigate to **[Settings \> Billing](https://claude.ai/settings/billing)**.
3. Find the **Invoices** section.
4. Click the "View" button next to the invoice you want to open.
Additionally, all invoices are automatically emailed to your billing email address. To find previously emailed invoices in your inbox, search by the subject line "Your receipt from Anthropic."
## How can I edit the billing details for my existing paid Claude subscription?
1. Click on your initials or name in the lower left corner and select “Settings” from the menu.
2. Navigate to **[Settings \> Billing](https://claude.ai/settings/billing)**.
3. Click the "Update" button next to your payment method.
4. Enter your new billing details in the payment update form.
5. Click "Update" to save your changes.
6. Your updated payment method will be charged the next time your subscription renews.
## How can I change or remove the card on my Pro or Max subscription?
To change the card on your Pro or Max subscription:
1. Navigate to **[Settings \> Billing](https://claude.ai/settings/billing)**.
2. Click the “Update” button next to your payment method.
3. Enter your new card details.
4. Click “Update” to save your changes.
The new card becomes your default payment method, and all future subscription renewals are charged to it. Your previous card is no longer billed.
There's no separate option to remove a card, and updating to a new card replaces the old one for billing purposes. The billing page only shows your current default card. Previously used cards are no longer charged, but they may remain stored with our payment processor. If you need a previous card fully removed from your account, please contact **[our support team](../15-Claude-AI-Features/how-to-get-support.md)**.
## How can I use a different name on my invoices?
If you want to use a name other than the one tied to your payment method, check the "Use a different name on invoices" box when adding or updating your payment method in **[Settings \> Billing](https://claude.ai/settings/billing)**.
## How can I edit a paid invoice?
Once an invoice is paid, there isn't a way to edit the information on the finalized invoice. Additionally, our internal teams cannot reissue paid invoices or modify information on previous invoices.
## Can I change the date I'm charged for my Pro or Max subscription?
No, there isn't a direct way to change your subscription billing date. However, you can unsubscribe from your current plan, then resubscribe on your preferred billing date to establish your new monthly billing cycle on a different date.
## What alternate payment methods are available?
For subscriptions purchased on the web, we only accept credit or debit cards. If you subscribed through Claude for iOS or Claude for Android, available payment options are determined by the Apple App Store or Google Play.
## I have a paid plan, but my account is showing as free; how can I access my paid account?
If you've paid for a Pro or Max plan but are not seeing this reflected in your account, there are two things you should check:
1. You've logged in with a different email. We recommend trying to sign in with any alternative emails you may have used to create your paid account.
2. Your payment method failed and your account was downgraded. To check this, navigate to **[Settings \> Billing](https://claude.ai/settings/billing)** to confirm your recent payment status and update your payment method or billing details if needed.
## Where can I see my monthly API credits?
In the Claude Console. All credits appear under **[Settings \> Billing](../04-API-Reference/Other/playground.md)** in your linked Console organization, with their amount and expiry date. Usage is never charged to your Claude plan. Learn more about **[monthly API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)**.
---
## Claude Enterprise plan | Claude by Anthropic
Source: https://www.claude.com/pricing/enterprise
Path: 17-Billing-Plans/pricing-enterprise.md
# Claude enterprise solutions
The frontier, on every desk
Put Claude to work across your organization. Help everyone think deeper, do more, and build securely.
[Get Enterprise plan](http://claude.ai/create/enterprise)[Build on Claude Platform](https://www.claude.com/platform/api)
## Trusted by the world’s leading organizations
> “We saw 12 hours of prototyping work collapse into about 20 minutes. Then your whole team can jump in and refine it together.”
30+concurrent agent tasks from a single task board
97%reduction in prototyping time
Industry:
Software
Company size:
Large
Product:
Claude Managed Agents
Location:
North America
> “In a highly regulated industry, we can't just throw our data and information into a large language model and hope for the best. Our conversations with Anthropic really guided in the ways we can securely use Claude for planning, for strategic tasks, for code generation.”
1000xclinical study documentation down from 10 weeks to 10 minutes
Industry:
Life sciences
Company size:
Large
Product:
Claude Code
Location:
Europe
> “Slack’s close collaboration with Anthropic has helped our Engineering and Product teams accelerate prototyping and model testing.”
97minutes per week saved by the average user through summarization and recap features
Industry:
Software
Company size:
Large
Product:
Claude Platform
Location:
North America
> “With this partnership, Allianz is taking a decisive step to address critical AI challenges in insurance. Anthropic's focus on safety and transparency complements our strong dedication to customer excellence and stakeholder trust.”
90%week-over-week growth company-wide deployment, with rapid global adoption
Industry:
Insurance
Company size:
Large
Product:
Claude Platform
Location:
EMEA
> “Through using Claude, we’ve saved millions, which we have reinvested in upskilling our customer support agents. We’ve empowered our agents to focus on those more complex issues that really require human care.”
87%reduction in customer support time
30%more accurate teams making sharper calls
Industry:
Transportation
Company size:
Large
Product:
Claude Platform
Location:
North America
> “As AI becomes the interface for decisions, trust becomes the standard. Moody’s decision-grade connected intelligence is key to unlocking AI for high‑stakes credit and compliance decision‑making.”
1,200× fastercredit memo prep time cut from 40 hours to 2 minutes with Claude-built agents
Industry:
Financial services
Company size:
Large
Product:
Claude Platform
Location:
North America
> “We saw 12 hours of prototyping work collapse into about 20 minutes. Then your whole team can jump in and refine it together.”
30+concurrent agent tasks from a single task board
97%reduction in prototyping time
Industry:
Software
Company size:
Large
Product:
Claude Managed Agents
Location:
North America
> “In a highly regulated industry, we can't just throw our data and information into a large language model and hope for the best. Our conversations with Anthropic really guided in the ways we can securely use Claude for planning, for strategic tasks, for code generation.”
1000xclinical study documentation down from 10 weeks to 10 minutes
Industry:
Life sciences
Company size:
Large
Product:
Claude Code
Location:
Europe
> “Slack’s close collaboration with Anthropic has helped our Engineering and Product teams accelerate prototyping and model testing.”
97minutes per week saved by the average user through summarization and recap features
Industry:
Software
Company size:
Large
Product:
Claude Platform
Location:
North America
> “With this partnership, Allianz is taking a decisive step to address critical AI challenges in insurance. Anthropic's focus on safety and transparency complements our strong dedication to customer excellence and stakeholder trust.”
90%week-over-week growth company-wide deployment, with rapid global adoption
Industry:
Insurance
Company size:
Large
Product:
Claude Platform
Location:
EMEA
1 of 6
-
-
-
-
-
-
-
-
-
-
-
## Built for enterprise
### Built on leading models
Claude is a leader on reasoning, coding, and analysis benchmarks. The same frontier models power every surface, from business apps to developer tools.
### No model training by default
Your prompts, data, and results are not used to train our models by default. Review our data practices at the Trust Center.
### Flexible by design
Pick the products and platform that are right for your teams, whether you’re collaborating with Claude at work or building your own products and offerings.
### Made to pass security review
The security, compliance, and admin controls your organization needs.
[Learn more (opens in new tab)](https://trust.anthropic.com/)
\*Data retention controls and OTEL monitoring are currently available on Claude Enterprise only.
-
Single sign-on (SSO/SAML) and domain capture
-
SOC 2, ISO 27001, GDPR, and CCPA compliance
-
Usage analytics and reporting
-
SCIM provisioning
-
Spend controls
-
Data retention controls\*
-
Compliance API
-
HIPAA-ready offering
-
Audit logs and OpenTelemetry monitoring\*
-
Role-based access control (RBAC)
## Bring Claude to your enterprise two ways
Deploy Claude to your workforce or build it into your products.
### Claude Enterprise
Give every employee secure access to Chat, Claude Cowork, Claude Code, and your company's connectors. Get the admin controls, management, and visibility your IT and security teams need.
[See plans](#pricing)
### Claude Platform
Access the Claude API to power new experiences, ship production-grade agents, and integrate Claude into the workflows and applications you're building.
[Explore the platform](https://www.claude.com/platform/api)
Results with Claude Code
90%
less time spent on complex code migrations
## Secure products for employees, everywhere your teams work
Claude Code
Claude Cowork
Claude Chat
Claude Security
### Code faster across your enterprise stack
Build, debug, and ship using natural language from your terminal, IDE, Slack, or the web. Claude Code works wherever your team does.
[Learn more](../15-Claude-AI-Features/product-claude-code-enterprise.md)
### Delegate tasks to Claude with Cowork
Connect your files and tools, then hand off research, documents, and repetitive work. Get polished deliverables back while you focus on the work that needs your judgment.
[Learn more](../15-Claude-AI-Features/product-cowork.md)
### Chat: A thinking partner for everyday work
Chat with Claude to develop ideas, draft content, tighten reports, work through hard problems, and more.
[Learn more](../15-Claude-AI-Features/product-overview.md)
### Find and fix vulnerabilities with Claude Security
Claude helps security teams and developers by reviewing code for security issues, drafts patches, and explains the risk in language your whole team can act on.
[Learn more](../15-Claude-AI-Features/product-claude-security.md)
Tailor Claude to your business
Connect to Gmail, Google Drive, Slack and more to give Claude context from across your stack. Use Claude directly inside Microsoft 365 or with Google Chrome.
[Learn more](../04-API-Reference/Other/partners-mcp.md)
## Real work, across every function
Engineering
Marketing
Sales
Product Management
Human Resources
Security
Prompt
Audit our use of the deprecated legacy-auth library across the monorepo. Generate a migration plan to move all 47 services to auth-v2, prioritized by risk and ordered by dependencies.
``` CodePanel-module-scss-module__SPquYW__terminalBody
✻ Migration plan: legacy-auth → auth-v2
Audited 47 services, 312 call sites, 8 distinct usage patterns.
Recommended order
Phase 1 — Low risk (weeks 1–2, 12 services)
Internal admin tools with no external dependencies. Safe to validate the auth-v2 codemod and surface unknown patterns.
Phase 2 — Leaf services (weeks 3–5, 18 services)
No downstream consumers in the dependency graph. Failures stay contained; single staged rollout per service.
Phase 3 — Core services (weeks 6–9, 17 services)
Auth-critical paths with downstream impact. Requires feature flags, shadow traffic comparison, and per-team rollback plans.
Risk callouts
payments-api — blocker
Uses undocumented legacy-auth.signWithRotation() not present in auth-v2. Needs design discussion before migration.
mobile-bff — needs review
Integration tests pinned to legacy-auth response format. Token envelope changed (token.claims → token.payload); 23 fixtures to update.
identity-gateway — coordinated cutover
Sits in front of 31 of 47 services. Recommend cutover at the Phase 2 → 3 boundary with a 48-hour dual-write window.
Suggested next steps
1. Open an RFC for the signWithRotation equivalent in auth-v2.
2. Run the codemod against Phase 1 services, one PR per service.
3. Add a CI check that fails on new legacy-auth imports in week 2.
4. Schedule identity-gateway cutover with platform for week 5.
```
### Engineering
- Convert project requirements into technical specifications
- Design system architecture and component interactions
- Troubleshoot errors and runtime issues
- Identify code optimizations and performance improvements
[Claude Code for Enterprise](../15-Claude-AI-Features/product-claude-code-enterprise.md)
### Marketing
- Interpret market trends and consumer behavior patterns
- Brainstorm multi-platform content items
- Develop marketing campaign strategies
- Create post campaign performance reports
### Sales
- Analyze sales calls to craft tailored account plans
- Develop objection handling strategies
- Build compelling and tailored pitches
- Interpret sales metrics and KPIs
### Product Management
- Define product vision and objectives
- Analyze user feedback and usage data
- Create product specifications and requirements documents
- Interpret product usage metrics and KPIs
### Human Resources
- Summarize candidate feedback into hiring recommendations
- Create performance review templates and calibration summaries
- Develop learning and development programs
- Interpret headcount and workforce planning metrics
### Security
- Triage alerts and prioritize real threats
- Investigate incidents and trace attack paths
- Correlate signals across logs and tools
- Draft incident reports and post-mortems
- Build detection rules and tune existing ones
## Get the Enterprise plan
[Explore features](pricing.md#team-enterprise-features)
### Enterprise
Get started today. Includes Enterprise security and compliance, chat, Claude Code, Cowork, connectors, SSO, SCIM, audit logs, and more.
\$20
Per seat / month, billed annually.
Usage is billed as you go at API rates, based on what your team uses. Annual commitment required. Minimum 20 seats.
[Get the Enterprise plan](http://claude.ai/create/enterprise)[Chat with buying specialist](https://claude.ai/buying-specialist)
[Usage limits (opens in new tab)](usage-limit-best-practices.md) apply. Prices shown don’t include applicable tax. Price and plans are subject to change at Anthropic's discretion.
[Usage limits (opens in new tab)](usage-limit-best-practices.md) apply. Price and plans are subject to change at Anthropic's discretion.
## Build on the Claude Platform
Give developers access to the API to build AI-enabled products, services, and agents.
[View documentation](../04-API-Reference/Other/home.md)
### Primitives
Building blocks to integrate Claude, including the Messages API and tools, with full control over every layer.
[Learn more](../04-API-Reference/Other/home.md)
### Harnesses and infrastructure
Everything you need to ship production-grade agents, including Claude Managed Agents.
[Learn more](https://www.claude.com/resources/articles/claude-managed-agents)
### Operating system
Controls to deploy and manage agents across your organization, including authorization, governance, and observability.
[Learn more](../04-API-Reference/Other/playground.md)
Customer story
Canva empowers employees across teams with Claude
[Read story](../18-Industry-UseCases/canva.md)
Customer story
GitLab enhances productivity with Claude
[Read story](../18-Industry-UseCases/gitlab-enterprise.md)
1 of 2
Code modernization
Modernize legacy code without starting over. Claude Code handles large-scale refactoring while keeping your existing business logic intact.
[Learn more](../18-Industry-UseCases/code-modernization.md)
### Build on your own
Launch your own generative AI-enabled products with:
------------------------------------------------------------------------
-
Access to all Claude models
-
Usage-based tiers
-
Automatically increasing rate limits
-
Pay-as-you-go pricing
-
Self-serve deployment on workbench
-
[Prompting guides and developer docs](https://docs.anthropic.com/claude/reference/getting-started-with-the-api)
[Start building](https://www.claude.com/platform/api)
### Get extra support
Need custom rate limits or hands-on help? Contact our sales team for:
------------------------------------------------------------------------
-
Anthropic-supported onboarding
-
Custom rate limits
-
Billing via monthly invoices
-
Prompting support
-
Deployment support
[Contact sales](https://www.claude.com/contact-sales)
## FAQ
Security and compliance
Products and capabilities
Getting started
### Security and compliance
### Does Anthropic train on our data?
No. Your inputs and outputs are not used to train our models by default. Review our data practices at the [Trust Center (opens in new tab)](https://trust.anthropic.com/).
### What security and compliance controls does Claude Enterprise include?
Enterprise is built for organizations with real compliance obligations:
- **Identity and access** — SSO and domain capture, SCIM and JIT provisioning, and role-based access control. Admins define groups, roles, and capabilities to govern exactly which people can use which products and connectors.
- **Visibility and logging** — audit logs, a Compliance API for programmatic access to activity logs, chats, files, and projects, OpenTelemetry, and an Analytics API for aggregated adoption and engagement data. Both feed the DLP, SIEM, and monitoring tools your security team already runs.
- **Data controls** — custom data retention, customer-managed encryption keys, and US-only inference.
- **Network controls** — IP allowlisting and network-level access control, which prevents access to personal or non-corporate Claude instances from enterprise networks.
- **Connector governance** — admins approve which connectors are available org-wide and set per-tool permissions. Connectors respect the permissions users already have in the underlying systems.
### Do you support HIPAA? Can we get a BAA?
Yes, for both the Claude Platform and Claude Enterprise. Claude Platform: Healthcare customers can sign a BAA with no Zero Data Retention requirement. The HIPAA-ready feature set in the Messages API includes prompt caching, web search, and structured outputs, with coverage expanding over time. Claude Enterprise: HIPAA-ready configuration is available with a BAA from Anthropic. Once enabled, your organization can process Protected Health Information (PHI) through Claude in accordance with HIPAA.
### Products and capabilities
### What is the Claude Enterprise plan?
Claude Enterprise is Anthropic's complete offering for organizations deploying Claude at scale. One seat gives every employee the full suite: Chat for everyday thinking work, Claude Code for engineering, Claude Cowork for delegating multi-step knowledge work, Claude Design for turning a prompt into polished visuals, and Claude in the tools your teams already use including Microsoft 365, Chrome, and Slack.
Underneath all of it sits one identity, one policy, and one set of admin controls. Connectors bring in your organization's data, skills encode how your teams actually work, and enterprise-grade security, governance, and analytics give IT and security teams the visibility they need. Please reference [pricing](pricing.md#team-&-enterprise) for a full feature breakdown.
### What’s included in the Enterprise plan?
The Claude Enterprise plan supports deep, cross-functional workflows and provides one seat for every surface:
**One seat, every surface**
- **Chat** — a thinking partner for everyday work, on web, desktop, and mobile
- **Claude Code** — agentic coding in the terminal, IDE, Slack, and on the web
- **Claude Cowork** — delegate your tasks such as research, analysis, and documents; get finished deliverables back
- **Claude Design** — go from prompt to polished visuals, prototypes, and slides
- **Claude for Microsoft 365** — Work with Claude in Excel, PowerPoint, Word, and Outlook
- **Claude in Chrome** — Claude navigates, clicks, and fills out forms across your tabs
**Context from your organization**
- Pre-built connectors, plus custom connectors via MCP for internal systems
- Skills that capture your templates, standards, and workflows so every team runs them the same way
- Memory across conversations, so Claude carries context forward
**Security, governance, and administration**
- Single sign-on (SSO), domain capture, SCIM and JIT provisioning
- Role-based access control for fine-grained user, feature, and spend management
- Audit logs, Compliance API, and Analytics API
- Custom data retention, customer-managed encryption keys, IP allowlisting, network-level access control
### What's the difference between Chat, Claude Code, and Claude Cowork?
Chat is meant for research, brainstorming, writing, and analysis. Claude Code is for software development from your terminal, desktop app, or the web. Claude Cowork is for delegating complex tasks that run in the background. All three are included in every Enterprise plan and entitlements are managed with role-based access controls from organization settings.
### Can we connect Claude to the tools we already use?
Yes. Connectors bring context from Google Drive, Gmail, Slack, Microsoft 365 and many more into Claude. You can also use Claude directly inside Excel, PowerPoint, Outlook, Slack, and Chrome. See the [Enterprise administrator guide (opens in new tab)](https://academy.claude.com/tutorials/claude-enterprise-administrator-guide) for setup.
### What is Claude for Work?
Claude for Work was the earlier name for our business plans — what are now the Team and Enterprise plans. The name has been retired, but the plans still exist: Team for collaboration across smaller organizations, and Enterprise for organizations operating at scale that need advanced security, compliance, and administrative controls.
### Getting started
### Can we buy Claude through AWS Marketplace, Google Cloud, or Azure?
Claude Enterprise is available directly from Anthropic and through AWS Marketplace, where it can draw down from your existing AWS commit. Claude Platform (the API) is also available on Amazon Bedrock, Gemini Enterprise Agent Platform, and Microsoft Foundry.
### Do you support invoice billing on Claude Enterprise?
Yes. Sales-assisted Claude Enterprise plans include invoice billing. Self-serve Enterprise plans accept credit card or ACH bank transfer.
### How can I integrate Claude into my own products or services?
If you're a developer building user-facing experiences or new products with Claude, the Claude Platform is the right starting point. It gives you direct access to our models, the Claude Agent SDK, and the building blocks for production agents.
[Explore the developer docs](https://docs.claude.com/en/home) to get started, or [contact our Sales team](https://claude.com/contact-sales) to talk through platform plans and volume commitments.
### Where do I get an API key for Claude Platform and how does billing work?
Create an API key in the [Claude Console (opens in new tab)](../04-API-Reference/Other/playground.md). For production workloads, you can use [Workload Identity Federation (opens in new tab)](../04-API-Reference/Other/manage-claude-workload-identity-federation.md) to exchange your cloud provider's identity for short-lived tokens instead of managing static keys. Self-serve accounts are prepaid: add a payment method, purchase credits, and optionally enable auto-reload. Credits cover API usage, the Workbench, and Claude Code (when authenticated with an API key). Enterprise customers can use monthly invoicing instead, [contact sales (opens in new tab)](https://claude.com/contact-sales) to set this up.
## Enterprise resources
Everything you need to integrate AI thoughtfully
into your organization.
Claude Enterprise administrator guide
Tutorial
Claude Academy
Resource
Zero trust AI agents
Guide
Deploying Claude across your organization
Guide
The Enterprise AI transformation guide
Guide
The 2026 state of AI agents report
Report
## Ready to bring Claude
to your organization?
[Get Enterprise plan](http://claude.ai/create/enterprise)[Build on Claude Platform](https://www.claude.com/platform/api)
-
-
-
-
-
-
-
-
-
-
-
[](https://www.claude.com/)
© 2026 Anthropic PBC
## Products
- [Claude](../15-Claude-AI-Features/product-overview.md)
- [Claude Code](../15-Claude-AI-Features/product-claude-code-fad1ab4b.md)
- [Claude Cowork](../15-Claude-AI-Features/product-cowork.md)
- [Claude Duet](../15-Claude-AI-Features/product-claude-duet.md)
- [Claude Tag](../15-Claude-AI-Features/product-tag.md)
- [Claude Science](../15-Claude-AI-Features/product-claude-science.md)
- [Claude Security](../15-Claude-AI-Features/product-claude-security.md)
- [Download app](https://www.claude.com/download)
- [Pricing](pricing.md)
- [Log in](https://claude.ai/login)
## Capabilities
- [Artifacts](https://www.claude.com/features/artifacts)
- [Design](../15-Claude-AI-Features/product-design.md)
- [Connectors](https://www.claude.com/marketplace/connectors-plugins)
- [Plugins](https://www.claude.com/marketplace/plugins)
- [Skills](https://www.claude.com/skills)
## Extensions
- [Claude in Chrome](https://www.claude.com/claude-in-chrome)
- [Claude for Google Workspace](https://www.claude.com/claude-for-google-workspace)
- [Claude for Microsoft 365](https://www.claude.com/claude-for-microsoft-365)
## Models
- [Mythos (including Fable)](../15-Claude-AI-Features/claude-mythos.md)
- [Opus](../15-Claude-AI-Features/claude-opus.md)
- [Sonnet](../15-Claude-AI-Features/claude-sonnet.md)
- [Haiku](../15-Claude-AI-Features/claude-haiku.md)
## Enterprise
- [Overview](pricing-enterprise.md)
- [Claude Code for Enterprise](../15-Claude-AI-Features/product-claude-code-enterprise.md)
## Departments
- [Customer support](../18-Industry-UseCases/customer-support.md)
- [Cybersecurity](../18-Industry-UseCases/cybersecurity.md)
- [Legal](../18-Industry-UseCases/legal.md)
- [Sales](../18-Industry-UseCases/sales.md)
## Industries
- [Financial advisors](../18-Industry-UseCases/financial-advisors.md)
- [Financial services](../18-Industry-UseCases/finance.md)
- [Government](../18-Industry-UseCases/government.md)
- [Healthcare](../18-Industry-UseCases/healthcare.md)
- [Higher education](../18-Industry-UseCases/education.md)
- [K-12 teachers](../18-Industry-UseCases/teachers.md)
- [Life sciences](../18-Industry-UseCases/life-sciences.md)
- [Nonprofits](../18-Industry-UseCases/nonprofits.md)
- [Small business](../18-Industry-UseCases/small-business.md)
## Programs
- [Campus](../15-Claude-AI-Features/programs-campus.md)
- [Frontier Academy](../15-Claude-AI-Features/programs-frontier-academy.md)
- [Scientists](../15-Claude-AI-Features/programs-team-plan-for-scientists.md)
- [Startups](../15-Claude-AI-Features/programs-startups.md)
## Developers
- [Developer docs](../02-Claude-Code-CLI/code-home.md)
- [Developer blog](https://claude.dev)
- [Community](https://www.claude.com/community)
- [Console](../04-API-Reference/Other/home.md)
- [Engineering at Anthropic](https://www.anthropic.com/engineering)
## Platform
- [Overview](https://www.claude.com/platform/api)
- [Marketplace](https://www.claude.com/marketplace)
- [Claude on AWS](../04-API-Reference/Other/partners-claude-on-aws.md)
- [Google Cloud](../04-API-Reference/Other/partners-google-cloud.md)
- [Microsoft Foundry](../04-API-Reference/Other/partners-microsoft-foundry.md)
- [Managed Agents](https://www.claude.com/platform/claude-managed-agents)
## Resources
- [Overview](https://www.claude.com/resources)
- [Articles](https://www.claude.com/resources/articles)
- [Webinars](https://www.claude.com/resources/webinars)
- [Claude partner network](../04-API-Reference/Other/partners.md)
- [Claude Academy](https://academy.claude.com/)
- [Customer stories](../18-Industry-UseCases/customers.md)
- [Events](https://www.anthropic.com/events)
- [Powered by Claude](../04-API-Reference/Other/partners-powered-by-claude.md)
- [Service partners](https://www.claude.com/marketplace/service-partners)
## Help and security
- [Availability](https://www.anthropic.com/legal/supported-regions)
- [Check files](https://www.claude.com/check-files)
- [Regional compliance](https://www.claude.com/regional-compliance)
- [Report abuse](https://www.claude.com/form/anthropic-content-reporting)
- [Security and compliance](https://trust.anthropic.com/)
- [Status](https://status.anthropic.com/)
- [Support center](https://support.claude.com/en/)
## Company
- [Anthropic](https://www.anthropic.com/)
- [Careers](https://www.anthropic.com/careers)
- [Policy](https://www.anthropic.com/policy)
- [Research](../19-Reference/anthropic-com-research.md)
- [Anthropic news](../19-Reference/news.md)
- [Policy on the AI Exponential](https://www.anthropic.com/policy-on-the-ai-exponential)
- [Responsible Scaling Policy](../19-Reference/announcing-our-updated-responsible-scaling-policy.md)
- [Transparency](https://anthropic.com/transparency)
## Terms and policies
- Privacy choices
- [Privacy policy](https://www.anthropic.com/legal/privacy)
- [Responsible disclosure policy](https://www.anthropic.com/responsible-disclosure-policy)
- [Terms of service: Commercial](https://www.anthropic.com/legal/commercial-terms)
- [Terms of service: Consumer](https://www.anthropic.com/legal/consumer-terms)
- [Terms of Service: US K-12](https://anthropic.com/legal/k12-terms)
- [Data Processing Agreement: US K-12](https://anthropic.com/legal/k12-dpa)
- [Usage Policy](https://www.anthropic.com/legal/aup)
## Products
- [Claude](../15-Claude-AI-Features/product-overview.md)
- [Claude Code](../15-Claude-AI-Features/product-claude-code-fad1ab4b.md)
- [Claude Cowork](../15-Claude-AI-Features/product-cowork.md)
- [Claude Duet](../15-Claude-AI-Features/product-claude-duet.md)
- [Claude Tag](../15-Claude-AI-Features/product-tag.md)
- [Claude Science](../15-Claude-AI-Features/product-claude-science.md)
- [Claude Security](../15-Claude-AI-Features/product-claude-security.md)
- [Download app](https://www.claude.com/download)
- [Pricing](pricing.md)
- [Log in](https://claude.ai/login)
## Capabilities
- [Artifacts](https://www.claude.com/features/artifacts)
- [Design](../15-Claude-AI-Features/product-design.md)
- [Connectors](https://www.claude.com/marketplace/connectors-plugins)
- [Plugins](https://www.claude.com/marketplace/plugins)
- [Skills](https://www.claude.com/skills)
## Extensions
- [Claude in Chrome](https://www.claude.com/claude-in-chrome)
- [Claude for Google Workspace](https://www.claude.com/claude-for-google-workspace)
- [Claude for Microsoft 365](https://www.claude.com/claude-for-microsoft-365)
## Models
- [Mythos (including Fable)](../15-Claude-AI-Features/claude-mythos.md)
- [Opus](../15-Claude-AI-Features/claude-opus.md)
- [Sonnet](../15-Claude-AI-Features/claude-sonnet.md)
- [Haiku](../15-Claude-AI-Features/claude-haiku.md)
## Enterprise
- [Overview](pricing-enterprise.md)
- [Claude Code for Enterprise](../15-Claude-AI-Features/product-claude-code-enterprise.md)
## Departments
- [Customer support](../18-Industry-UseCases/customer-support.md)
- [Cybersecurity](../18-Industry-UseCases/cybersecurity.md)
- [Legal](../18-Industry-UseCases/legal.md)
- [Sales](../18-Industry-UseCases/sales.md)
## Industries
- [Financial advisors](../18-Industry-UseCases/financial-advisors.md)
- [Financial services](../18-Industry-UseCases/finance.md)
- [Government](../18-Industry-UseCases/government.md)
- [Healthcare](../18-Industry-UseCases/healthcare.md)
- [Higher education](../18-Industry-UseCases/education.md)
- [K-12 teachers](../18-Industry-UseCases/teachers.md)
- [Life sciences](../18-Industry-UseCases/life-sciences.md)
- [Nonprofits](../18-Industry-UseCases/nonprofits.md)
- [Small business](../18-Industry-UseCases/small-business.md)
## Programs
- [Campus](../15-Claude-AI-Features/programs-campus.md)
- [Frontier Academy](../15-Claude-AI-Features/programs-frontier-academy.md)
- [Scientists](../15-Claude-AI-Features/programs-team-plan-for-scientists.md)
- [Startups](../15-Claude-AI-Features/programs-startups.md)
## Developers
- [Developer docs](../02-Claude-Code-CLI/code-home.md)
- [Developer blog](https://claude.dev)
- [Community](https://www.claude.com/community)
- [Console](../04-API-Reference/Other/home.md)
- [Engineering at Anthropic](https://www.anthropic.com/engineering)
## Platform
- [Overview](https://www.claude.com/platform/api)
- [Marketplace](https://www.claude.com/marketplace)
- [Claude on AWS](../04-API-Reference/Other/partners-claude-on-aws.md)
- [Google Cloud](../04-API-Reference/Other/partners-google-cloud.md)
- [Microsoft Foundry](../04-API-Reference/Other/partners-microsoft-foundry.md)
- [Managed Agents](https://www.claude.com/platform/claude-managed-agents)
## Resources
- [Overview](https://www.claude.com/resources)
- [Articles](https://www.claude.com/resources/articles)
- [Webinars](https://www.claude.com/resources/webinars)
- [Claude partner network](../04-API-Reference/Other/partners.md)
- [Claude Academy](https://academy.claude.com/)
- [Customer stories](../18-Industry-UseCases/customers.md)
- [Events](https://www.anthropic.com/events)
- [Powered by Claude](../04-API-Reference/Other/partners-powered-by-claude.md)
- [Service partners](https://www.claude.com/marketplace/service-partners)
## Help and security
- [Availability](https://www.anthropic.com/legal/supported-regions)
- [Check files](https://www.claude.com/check-files)
- [Regional compliance](https://www.claude.com/regional-compliance)
- [Report abuse](https://www.claude.com/form/anthropic-content-reporting)
---
## Plans & pricing | Claude by Anthropic
Source: https://www.claude.com/pricing/max
Path: 17-Billing-Plans/pricing-max.md
# Pricing
Individual
Team & Enterprise
API
### Free
\$0
Free for everyone
[Try Claude](https://claude.ai/login?plan=free)
- Chat on web, desktop, and mobile
- Search the web, create files, and run code
- Memory across conversations
- Connect your apps and tools
- Create Artifacts
- Claude Design, Slides, Docs
### Pro
For everyday work
\$17
Per month with annual subscription discount (\$200 billed up front). \$20 if billed monthly.
[Try Claude](https://claude.ai/login?plan=pro)
Everything in Free, plus:
- More usage\*
- Hand off and schedule tasks
- Claude Dashboards (beta)
- Claude Code
- Claude Science
- Projects
- More Claude models
- Claude in Chrome and Microsoft 365
### Max
For people who work with Claude all day
From \$100
Per month
[Try Claude](https://claude.ai/login?plan=max)
Everything in Pro, plus:
- Choose 5x or 20x more usage than Pro\*
- Higher output limits for all tasks
- Early access to advanced Claude features
- Priority access at high traffic times
- \$100 to \$200/month in API credits to build on the Claude Platform^(†)
[Usage limits](usage-limit-best-practices.md) apply. Prices shown don’t include applicable tax. Price and plans are subject to change at Anthropic's discretion.
[Usage limits](usage-limit-best-practices.md) apply. Price and plans are subject to change at Anthropic's discretion.
## Compare features across plans
Search
Free
[Try Claude](https://claude.ai/)
Pro
[Try Claude](https://claude.ai/)
Max 5x
[Try Claude](https://claude.ai/)
Max 20x
[Try Claude](https://claude.ai/)
### Features and capabilities
[TABLE]
### Security and administration
[TABLE]
### Payment options
[TABLE]
### Models and usage
[TABLE]
### Team
For teams of 2 to 150
[Get Team plan](https://claude.ai/upgrade?initialPlanType=team)
Standard seat
All Claude features, plus more usage than Pro\*
\$20
Per seat / month if billed annually. \$25 if billed monthly.
Premium seat
5x more usage than standard seats\*
\$100
Per seat / month if billed annually. \$125 if billed monthly.
- Claude Code and Claude Cowork
- Claude Design, Slides, and Docs
- Claude Motion and Dashboards (beta)
- Claude Science
- Microsoft 365, @Claude, and more
- Enterprise search across your organization
- Central billing and administration
- Single sign-on (SSO)
- Admin controls for remote and local connectors
- Enterprise deployment for the Claude desktop app
- No model training on your content by default
- Mix and match seat types
- Up to \$500 per month in pooled API credits^(†)
### Enterprise
For large businesses operating at scale
[Get Enterprise plan](https://claude.ai/create/enterprise)[Chat with buying specialist](https://claude.ai/buying-specialist)
Seat price + usage at API rates
US\$20/seat/month, billed annually, 20 seat minimum. Usage cost scales with model and task.
All Team plan features, plus:
- Admins set user and org spend limits
- Role-based access with fine grained permissioning
- System for Cross-domain Identity Management (SCIM)
- Audit logs
- Compliance API for observability and monitoring
- Custom data retention controls
- Network-level access control
- IP allowlisting
- HIPAA-ready offering available
- Claude Security (beta)
[Usage limits](usage-limit-best-practices.md) apply. Prices shown don’t include applicable tax. Price and plans are subject to change at Anthropic's discretion.
[Usage limits](usage-limit-best-practices.md) apply. Price and plans are subject to change at Anthropic's discretion.
### Education plan
Get a comprehensive university‐wide plan for an institution, including its students, faculty, and staff.
[Learn more](../18-Industry-UseCases/education.md)
-
Student and faculty access
Comprehensive access for all university members at discounted rates
-
Academic research and learning mode
Dedicated API credits and educational features for student learning
-
Training and enablement
Resources for successful adoption across your institution
## Compare features across plans
Search
Team
[Create plan](https://claude.ai/upgrade?initialPlanType=team)
Enterprise (self-serve)
[Create plan](https://claude.ai/create/enterprise)
Enterprise (sales-assisted)
[Contact sales](https://claude.com/contact-sales)
### Features and capabilities
[TABLE]
### Security and administration
[TABLE]
### Payment options
[TABLE]
### Partnership
[TABLE]
### Models and usage
[TABLE]
## Latest models
[Contact sales](https://claude.com/contact-sales)[Start building (opens in new tab)](../04-API-Reference/Other/playground.md)
Save 50% with batch processing. [Learn more](../04-API-Reference/Guides/build-with-claude-batch-processing.md)
Batch processing
### Fable 5.1
Next generation intelligence for long-running agents
Prompt caching
Read
\$0.25 / MTok
Write
\$12.50 / MTok
Input
\$10 / MTok
Output
\$50 / MTok
### Opus 5.5
Daily driver for agentic coding and enterprise work
Prompt caching
Read
\$0.20 / MTok
Write
\$5 / MTok
Input
\$4 / MTok
Output
\$20 / MTok
### Sonnet 5.5
High-performance model for coding and agents
Prompt caching
Read
\$0.10 / MTok
Write
\$2.50 / MTok
Input
\$2 / MTok
Output
\$10 / MTok
### Haiku 5.5
Fastest, most cost-efficient model
Prompt caching
Prompts ≤ 100K tokens
Read
\$0.01 / MTok
Write
\$0.125 / MTok
Prompts \> 100K tokens
Read
\$0.05 / MTok
Write
\$0.625 / MTok
Input
Prompts ≤ 100K tokens
\$0.10 / MTok
Prompts \> 100K tokens
\$0.50 / MTok
Output
Prompts ≤ 100K tokens
\$0.50 / MTok
Prompts \> 100K tokens
\$2.50 / MTok
For workloads that need to run in the US, US-only inference is available at 1.1x pricing for input and output tokens. [Learn more](../04-API-Reference/Other/manage-claude-data-residency.md).
Get up to 2.5x faster speeds with fast mode for Opus 5.5 at 2x standard pricing. [Learn more](about-claude-pricing.md#fast-mode-pricing).
Prompt caching pricing reflects 5-minute TTL. Learn about [extended prompt caching](../04-API-Reference/Guides/build-with-claude-prompt-caching.md#1-hour-cache-duration).
[Explore detailed pricing (opens in new tab)](about-claude-pricing.md)
## Pricing for Claude Platform features
Get more out of Claude with advanced features and capabilities.
[Learn more (opens in new tab)](about-claude-pricing.md#specific-tool-pricing)
### Managed Agents
Build and deploy agents at scale with a suite of composable APIs. Standard token rates apply.
Cost
\$0.08 per session-hour for active runtime
### Web search
Give Claude access to the latest information from the web. Doesn’t include input and output tokens required to process requests.
Cost
\$10 / 1K searches
### Code execution
Run Python code in a sandboxed environment for advanced data analysis. 50 free hours of usage daily per organization.
Additional hours
\$0.05 per hour per container
### Service tiers
Balance availability, performance, and predictable costs based on your needs.
[Learn more (opens in new tab)](../04-API-Reference/Endpoints/service-tiers.md)[Contact sales](https://claude.com/contact-sales)
- Standard
Default tier for both piloting and scaling everyday use cases
- Batch
For asynchronous workloads that can be processed together for better efficiency
## Legacy models
[Learn more (opens in new tab)](../20-Models/about-claude-models-overview.md)[Explore detailed pricing (opens in new tab)](about-claude-pricing.md)
### Haiku 4.5
Prompt caching
Read
\$0.10 / MTok
Write
\$1.25 / MTok
Input
\$1 / MTok
Output
\$5 / MTok
### Sonnet 5
Prompt caching
Read
\$0.20 / MTok
Write
\$2.50 / MTok
Input
\$2 / MTok
Output
\$10 / MTok
Save 50% with batch processing. [Learn more](../04-API-Reference/Guides/build-with-claude-batch-processing.md)
Batch processing
### Opus 5
Prompt caching
Read
\$0.50 / MTok
Write
\$6.25 / MTok
Input
\$5 / MTok
Output
\$25 / MTok
### Fable 5
Prompt caching
Read
\$1 / MTok
Write
\$12.50 / MTok
Input
\$10 / MTok
Output
\$50 / MTok
### Opus 4.8
Prompt caching
Read
\$0.50 / MTok
Write
\$6.25 / MTok
Input
\$5 / MTok
Output
\$25 / MTok
### Sonnet 4.6
Prompt caching
Read
\$0.30 / MTok
Write
\$3.75 / MTok
Input
\$3 / MTok
Output
\$15 / MTok
### Opus 4.7
Prompt caching
Read
\$0.50 / MTok
Write
\$6.25 / MTok
Input
\$5 / MTok
Output
\$25 / MTok
### Opus 4.6
Prompt caching
Read
\$0.50 / MTok
Write
\$6.25 / MTok
Input
\$5 / MTok
Output
\$25 / MTok
### Sonnet 4.5
Prompt caching
Read
\$0.30 / MTok
Write
\$3.75 / MTok
Input
\$3 / MTok
Output
\$15 / MTok
### Opus 4.5
Prompt caching
Read
\$0.50 / MTok
Write
\$6.25 / MTok
Input
\$5 / MTok
Output
\$25 / MTok
Prompt caching pricing reflects 5-minute TTL. Learn about [extended prompt caching](../04-API-Reference/Guides/build-with-claude-prompt-caching.md#pricing).
## FAQ
Plans and usage
Billing and payments
Managing your plan
### Plans and usage
#### What do I get with Claude Pro?
The [Pro plan](what-is-the-pro-plan.md) gives you everything in a Free plan with more usage and more of Claude's capabilities. That includes Claude Code, along with projects to organize your chats and documents, access to more Claude models, and Claude for Microsoft 365. You can choose a monthly or annual subscription.
#### How is Claude Max different from Pro?
The [Max plan](what-is-the-max-plan.md) is built for people who work with Claude throughout the day and want longer, uninterrupted sessions. You get everything in Pro, plus more usage: choose from 5x or 20x the usage of Pro per 5-hour session. Max also gives you higher output limits. Both options are billed monthly. See the cards above for current pricing.
#### What are the usage limits on each plan, and what happens when I hit them?
Every plan has [usage limits](usage-limit-best-practices.md) that reset on a rolling five-hour session window, and paid plans add weekly limits on top. Your activity across Claude on web, desktop, mobile, and Claude Code all draws from the same pool. How much you can do depends on the length and complexity of your conversations, the model you choose, and the features you use, so there's no fixed message count. Free covers everyday questions. Pro gives you at least 5x more usage per 5-hour session than Free. Max gives you 5x or 20x more usage per 5-hour session than Pro. On Team plans, Standard seats give more than Pro and Premium seats give 5x more than Standard. To manage capacity and make sure all users have fair access, we may limit your usage in other ways, such as weekly and monthly caps or model and feature usage, at our discretion. When you reach a limit, you can wait for it to reset, move to a higher plan, or, on paid plans, turn on [usage credits](https://support.claude.com/en/articles/12429409-manage-usage-credits-for-paid-claude-plans) to keep working at standard API rates. You can see where you stand anytime in [Settings \> Usage](https://claude.ai/settings/usage).
#### Is Claude Code included in my plan?
[Claude Code](../15-Claude-AI-Features/product-claude-code-fad1ab4b.md) is included in all paid plans. It shares the same usage limits as the rest of your plan, so your work in the terminal and your chats draw from one pool. For heavy coding sessions, you can also switch to pay-as-you-go API credits through a [Console account](../04-API-Reference/Other/playground.md).
#### How much does the Claude Enterprise plan cost?
The [Claude Enterprise plan](pricing-enterprise.md) is built for large businesses operating at scale. Pricing is \$20 per seat per month plus usage billed at API rates, so cost scales with the models and tasks your team runs. Enterprise is billed annually and includes everything in Team plus advanced security and admin controls, including SCIM, audit logs, custom data retention, and role-based access. You can get started self-serve or [contact sales](https://claude.com/contact-sales) for a tailored quote.
### Billing and payments
#### Can I pay annually? Does it cost less than if I pay monthly?
Yes, annual plans are designed to cost less than monthly subscriptions. Annual subscriptions are available for Pro and Team plans. Enterprise plans are only available as annual subscriptions.
When you choose to pay annually, you're billed once up front for the year. If you're already on a monthly plan, you can switch to annual in [Settings \> Billing](https://claude.ai/settings/billing), and any unused time is credited toward your first annual invoice. See the steps for [Pro](how-to-change-your-pro-plan-from-monthly-to-annual-billing.md) and [Team](change-your-team-plan-from-monthly-to-annual-billing.md).
#### Does Claude offer refunds?
Payments are generally non-refundable, except where our [Consumer Terms of Service](https://www.anthropic.com/legal/consumer-terms) say otherwise or where local law requires it.
Customers outside of Europe can follow this process to [request a refund](requesting-a-refund-for-a-paid-claude-plan.md):
- Log in, open Get help from the menu, start a message, and choose Claude Refund Request to check your eligibility.
- If you subscribed through the App Store, [Apple](https://support.apple.com/billing) handles the refund, so you'll request it from Apple.
- If you subscribed through Google Play, [contact our Support team](../15-Claude-AI-Features/how-to-get-support.md) to check eligibility for an active subscription.
If you're in the European Economic Area and the United Kingdom, and within your 14-day withdrawal period, you can request a refund directly in the app.
### Managing your plan
#### How do I upgrade, downgrade, or switch between plans?
You can change your plan any time in Settings.
- For individual plans, go to [Settings \> Billing](https://claude.ai/settings/billing) and choose Manage subscription.
- On Team plans, an Owner or Primary Owner manages this under Organization settings \> Billing. [See more details here](https://support.claude.com/en/articles/12004354-purchase-and-manage-seats-on-team-plans).
Upgrades take effect right away, and any unused time on your current plan is credited toward the new one, so you won't pay twice for the same days.
Moving from monthly to annual works the same way, with your remaining time credited to the first annual invoice.
In some upgrades (for example Pro Annual to Max 5x Monthly), your remaining value on your old plan is larger than the cost of one billing period of the new plan. In this case, the excess will be stored as credit, which will automatically get used for future purchases.
Downgrades take effect at the end of your current billing period, and your chats, projects, and files stay with your account whichever plan you're on.
#### How do I cancel my Claude subscription?
You can cancel anytime, and your plan stays active until the end of your current billing period. To avoid the next charge, cancel at least 24 hours before your renewal date.
- If you signed up on the web or the desktop app, go to [Settings \> Billing](https://claude.ai/settings/billing) and click Cancel.
- If you subscribed through the App Store or Google Play, cancel from that app under Billing \> Manage subscription, or directly in your [Apple](https://support.apple.com/en-us/118428) or [Google Play](https://support.google.com/googleplay/answer/7018481) account.
- Team and self-serve Enterprise: an Owner or Primary Owner cancels under [Organization settings \> Billing](https://claude.ai/admin-settings/billing).
- Sales-assisted Enterprise: Reach out to your Anthropic Contact or our Sales team to discuss cancellation.
Canceling doesn't delete your data. Your chats, projects, and files stay with your account, though some features aren't available on the Free plan. For Pro and Max, your account moves to the Free plan once the period ends. For step-by-step help, see [how to cancel a Pro or Max plan](how-do-i-cancel-my-paid-claude-subscription.md) or [cancel a Team plan](cancel-your-organization-s-team-plan-subscription.md).
[](https://www.claude.com/)
© 2026 Anthropic PBC
## Products
- [Claude](../15-Claude-AI-Features/product-overview.md)
- [Claude Code](../15-Claude-AI-Features/product-claude-code-fad1ab4b.md)
- [Claude Cowork](../15-Claude-AI-Features/product-cowork.md)
- [Claude Duet](../15-Claude-AI-Features/product-claude-duet.md)
- [Claude Tag](../15-Claude-AI-Features/product-tag.md)
- [Claude Science](../15-Claude-AI-Features/product-claude-science.md)
- [Claude Security](../15-Claude-AI-Features/product-claude-security.md)
- [Download app](https://www.claude.com/download)
- [Pricing](pricing.md)
- [Log in](https://claude.ai/login)
## Capabilities
- [Artifacts](https://www.claude.com/features/artifacts)
- [Design](../15-Claude-AI-Features/product-design.md)
- [Connectors](https://www.claude.com/marketplace/connectors-plugins)
- [Plugins](https://www.claude.com/marketplace/plugins)
- [Skills](https://www.claude.com/skills)
## Extensions
- [Claude in Chrome](https://www.claude.com/claude-in-chrome)
- [Claude for Google Workspace](https://www.claude.com/claude-for-google-workspace)
- [Claude for Microsoft 365](https://www.claude.com/claude-for-microsoft-365)
## Models
- [Mythos (including Fable)](../15-Claude-AI-Features/claude-mythos.md)
- [Opus](../15-Claude-AI-Features/claude-opus.md)
- [Sonnet](../15-Claude-AI-Features/claude-sonnet.md)
- [Haiku](../15-Claude-AI-Features/claude-haiku.md)
## Enterprise
- [Overview](pricing-enterprise.md)
- [Claude Code for Enterprise](../15-Claude-AI-Features/product-claude-code-enterprise.md)
## Departments
- [Customer support](../18-Industry-UseCases/customer-support.md)
- [Cybersecurity](../18-Industry-UseCases/cybersecurity.md)
- [Legal](../18-Industry-UseCases/legal.md)
- [Sales](../18-Industry-UseCases/sales.md)
## Industries
- [Financial advisors](../18-Industry-UseCases/financial-advisors.md)
- [Financial services](../18-Industry-UseCases/finance.md)
- [Government](../18-Industry-UseCases/government.md)
- [Healthcare](../18-Industry-UseCases/healthcare.md)
- [Higher education](../18-Industry-UseCases/education.md)
- [K-12 teachers](../18-Industry-UseCases/teachers.md)
- [Life sciences](../18-Industry-UseCases/life-sciences.md)
- [Nonprofits](../18-Industry-UseCases/nonprofits.md)
- [Small business](../18-Industry-UseCases/small-business.md)
## Programs
- [Campus](../15-Claude-AI-Features/programs-campus.md)
- [Frontier Academy](../15-Claude-AI-Features/programs-frontier-academy.md)
- [Scientists](../15-Claude-AI-Features/programs-team-plan-for-scientists.md)
- [Startups](../15-Claude-AI-Features/programs-startups.md)
## Developers
- [Developer docs](../02-Claude-Code-CLI/code-home.md)
- [Developer blog](https://claude.dev)
- [Community](https://www.claude.com/community)
- [Console](../04-API-Reference/Other/home.md)
- [Engineering at Anthropic](https://www.anthropic.com/engineering)
## Platform
- [Overview](https://www.claude.com/platform/api)
- [Marketplace](https://www.claude.com/marketplace)
- [Claude on AWS](../04-API-Reference/Other/partners-claude-on-aws.md)
- [Google Cloud](../04-API-Reference/Other/partners-google-cloud.md)
- [Microsoft Foundry](../04-API-Reference/Other/partners-microsoft-foundry.md)
- [Managed Agents](https://www.claude.com/platform/claude-managed-agents)
## Resources
- [Overview](https://www.claude.com/resources)
- [Articles](https://www.claude.com/resources/articles)
- [Webinars](https://www.claude.com/resources/webinars)
- [Claude partner network](../04-API-Reference/Other/partners.md)
- [Claude Academy](https://academy.claude.com/)
- [Customer stories](../18-Industry-UseCases/customers.md)
- [Events](https://www.anthropic.com/events)
- [Powered by Claude](../04-API-Reference/Other/partners-powered-by-claude.md)
- [Service partners](https://www.claude.com/marketplace/service-partners)
## Help and security
- [Availability](https://www.anthropic.com/legal/supported-regions)
- [Check files](https://www.claude.com/check-files)
- [Regional compliance](https://www.claude.com/regional-compliance)
- [Report abuse](https://www.claude.com/form/anthropic-content-reporting)
- [Security and compliance](https://trust.anthropic.com/)
- [Status](https://status.anthropic.com/)
- [Support center](https://support.claude.com/en/)
## Company
- [Anthropic](https://www.anthropic.com/)
- [Careers](https://www.anthropic.com/careers)
- [Policy](https://www.anthropic.com/policy)
- [Research](../19-Reference/anthropic-com-research.md)
- [Anthropic news](../19-Reference/news.md)
- [Policy on the AI Exponential](https://www.anthropic.com/policy-on-the-ai-exponential)
- [Responsible Scaling Policy](../19-Reference/announcing-our-updated-responsible-scaling-policy.md)
- [Transparency](https://anthropic.com/transparency)
## Terms and policies
- Privacy choices
- [Privacy policy](https://www.anthropic.com/legal/privacy)
- [Responsible disclosure policy](https://www.anthropic.com/responsible-disclosure-policy)
- [Terms of service: Commercial](https://www.anthropic.com/legal/commercial-terms)
- [Terms of service: Consumer](https://www.anthropic.com/legal/consumer-terms)
- [Terms of Service: US K-12](https://anthropic.com/legal/k12-terms)
- [Data Processing Agreement: US K-12](https://anthropic.com/legal/k12-dpa)
- [Usage Policy](https://www.anthropic.com/legal/aup)
## Products
- [Claude](../15-Claude-AI-Features/product-overview.md)
- [Claude Code](../15-Claude-AI-Features/product-claude-code-fad1ab4b.md)
- [Claude Cowork](../15-Claude-AI-Features/product-cowork.md)
- [Claude Duet](../15-Claude-AI-Features/product-claude-duet.md)
- [Claude Tag](../15-Claude-AI-Features/product-tag.md)
- [Claude Science](../15-Claude-AI-Features/product-claude-science.md)
- [Claude Security](../15-Claude-AI-Features/product-claude-security.md)
- [Download app](https://www.claude.com/download)
- [Pricing](pricing.md)
- [Log in](https://claude.ai/login)
## Capabilities
- [Artifacts](https://www.claude.com/features/artifacts)
- [Design](../15-Claude-AI-Features/product-design.md)
- [Connectors](https://www.claude.com/marketplace/connectors-plugins)
- [Plugins](https://www.claude.com/marketplace/plugins)
- [Skills](https://www.claude.com/skills)
## Extensions
- [Claude in Chrome](https://www.claude.com/claude-in-chrome)
- [Claude for Google Workspace](https://www.claude.com/claude-for-google-workspace)
- [Claude for Microsoft 365](https://www.claude.com/claude-for-microsoft-365)
## Models
- [Mythos (including Fable)](../15-Claude-AI-Features/claude-mythos.md)
- [Opus](../15-Claude-AI-Features/claude-opus.md)
- [Sonnet](../15-Claude-AI-Features/claude-sonnet.md)
- [Haiku](../15-Claude-AI-Features/claude-haiku.md)
## Enterprise
- [Overview](pricing-enterprise.md)
- [Claude Code for Enterprise](../15-Claude-AI-Features/product-claude-code-enterprise.md)
## Departments
- [Customer support](../18-Industry-UseCases/customer-support.md)
- [Cybersecurity](../18-Industry-UseCases/cybersecurity.md)
- [Legal](../18-Industry-UseCases/legal.md)
- [Sales](../18-Industry-UseCases/sales.md)
## Industries
- [Financial advisors](../18-Industry-UseCases/financial-advisors.md)
- [Financial services](../18-Industry-UseCases/finance.md)
- [Government](../18-Industry-UseCases/government.md)
- [Healthcare](../18-Industry-UseCases/healthcare.md)
- [Higher education](../18-Industry-UseCases/education.md)
- [K-12 teachers](../18-Industry-UseCases/teachers.md)
- [Life sciences](../18-Industry-UseCases/life-sciences.md)
- [Nonprofits](../18-Industry-UseCases/nonprofits.md)
- [Small business](../18-Industry-UseCases/small-business.md)
## Programs
- [Campus](../15-Claude-AI-Features/programs-campus.md)
- [Frontier Academy](../15-Claude-AI-Features/programs-frontier-academy.md)
- [Scientists](../15-Claude-AI-Features/programs-team-plan-for-scientists.md)
- [Startups](../15-Claude-AI-Features/programs-startups.md)
## Developers
- [Developer docs](../02-Claude-Code-CLI/code-home.md)
- [Developer blog](https://claude.dev)
- [Community](https://www.claude.com/community)
- [Console](../04-API-Reference/Other/home.md)
- [Engineering at Anthropic](https://www.anthropic.com/engineering)
## Platform
- [Overview](https://www.claude.com/platform/api)
- [Marketplace](https://www.claude.com/marketplace)
- [Claude on AWS](../04-API-Reference/Other/partners-claude-on-aws.md)
- [Google Cloud](../04-API-Reference/Other/partners-google-cloud.md)
- [Microsoft Foundry](../04-API-Reference/Other/partners-microsoft-foundry.md)
- [Managed Agents](https://www.claude.com/platform/claude-managed-agents)
## Resources
- [Overview](https://www.claude.com/resources)
- [Articles](https://www.claude.com/resources/articles)
- [Webinars](https://www.claude.com/resources/webinars)
- [Claude partner network](../04-API-Reference/Other/partners.md)
- [Claude Academy](https://academy.claude.com/)
- [Customer stories](../18-Industry-UseCases/customers.md)
- [Events](https://www.anthropic.com/events)
- [Powered by Claude](../04-API-Reference/Other/partners-powered-by-claude.md)
- [Service partners](https://www.claude.com/marketplace/service-partners)
## Help and security
- [Availability](https://www.anthropic.com/legal/supported-regions)
- [Check files](https://www.claude.com/check-files)
- [Regional compliance](https://www.claude.com/regional-compliance)
- [Report abuse](https://www.claude.com/form/anthropic-content-reporting)
---
## Plans & pricing | Claude by Anthropic
Source: https://www.claude.com/pricing
Path: 17-Billing-Plans/pricing.md
# Pricing
Individual
Developer
Team & Enterprise
API
Individual
### Free
\$0
Free for everyone
[Try Claude](https://claude.ai/login?plan=free)
- Chat on web, desktop, and mobile
- Search the web, create files, and run code
- Memory across conversations
- Connect your apps and tools
- Create Artifacts
- Claude Design, Slides, Docs
### Pro
For everyday work
\$17
Per month with annual subscription discount (\$200 billed up front). \$20 if billed monthly.
[Try Claude](https://claude.ai/login?plan=pro)
Everything in Free, plus:
- More usage\*
- Hand off and schedule tasks
- Claude Dashboards (beta)
- Claude Code
- Claude Science
- Projects
- More Claude models
- Claude in Chrome and Microsoft 365
### Max
For people who work with Claude all day
From \$100
Per month
[Try Claude](https://claude.ai/login?plan=max)
Everything in Pro, plus:
- Choose 5x or 20x more usage than Pro\*
- Higher output limits for all tasks
- Early access to advanced Claude features
- Priority access at high traffic times
- \$100 to \$200/month in API credits to build on the Claude Platform^(†)
[Usage limits](usage-limit-best-practices.md) apply. Prices shown don’t include applicable tax. Price and plans are subject to change at Anthropic's discretion.
[Usage limits](usage-limit-best-practices.md) apply. Price and plans are subject to change at Anthropic's discretion.
## Compare features across plans
Search
Free
[Try Claude](https://claude.ai/)
Pro
[Try Claude](https://claude.ai/)
Max 5x
[Try Claude](https://claude.ai/)
Max 20x
[Try Claude](https://claude.ai/)
### Features and capabilities
[TABLE]
### Security and administration
[TABLE]
### Payment options
[TABLE]
### Models and usage
[TABLE]
### Team
For teams of 2 to 150
[Get Team plan](https://claude.ai/upgrade?initialPlanType=team)
Standard seat
All Claude features, plus more usage than Pro\*
\$20
Per seat / month if billed annually. \$25 if billed monthly.
Premium seat
5x more usage than standard seats\*
\$100
Per seat / month if billed annually. \$125 if billed monthly.
- Claude Code and Claude Cowork
- Claude Design, Slides, and Docs
- Claude Motion and Dashboards (beta)
- Claude Science
- Microsoft 365, @Claude, and more
- Enterprise search across your organization
- Central billing and administration
- Single sign-on (SSO)
- Admin controls for remote and local connectors
- Enterprise deployment for the Claude desktop app
- No model training on your content by default
- Mix and match seat types
- Up to \$500 per month in pooled API credits^(†)
### Enterprise
For large businesses operating at scale
[Get Enterprise plan](https://claude.ai/create/enterprise)[Chat with buying specialist](https://claude.ai/buying-specialist)
Seat price + usage at API rates
US\$20/seat/month, billed annually, 20 seat minimum. Usage cost scales with model and task.
All Team plan features, plus:
- Admins set user and org spend limits
- Role-based access with fine grained permissioning
- System for Cross-domain Identity Management (SCIM)
- Audit logs
- Compliance API for observability and monitoring
- Custom data retention controls
- Network-level access control
- IP allowlisting
- HIPAA-ready offering available
- Claude Security (beta)
[Usage limits](usage-limit-best-practices.md) apply. Prices shown don’t include applicable tax. Price and plans are subject to change at Anthropic's discretion.
[Usage limits](usage-limit-best-practices.md) apply. Price and plans are subject to change at Anthropic's discretion.
### Education plan
Get a comprehensive university‐wide plan for an institution, including its students, faculty, and staff.
[Learn more](../18-Industry-UseCases/education.md)
-
Student and faculty access
Comprehensive access for all university members at discounted rates
-
Academic research and learning mode
Dedicated API credits and educational features for student learning
-
Training and enablement
Resources for successful adoption across your institution
## Compare features across plans
Search
Team
[Create plan](https://claude.ai/upgrade?initialPlanType=team)
Enterprise (self-serve)
[Create plan](https://claude.ai/create/enterprise)
Enterprise (sales-assisted)
[Contact sales](https://claude.com/contact-sales)
### Features and capabilities
[TABLE]
### Security and administration
[TABLE]
### Payment options
[TABLE]
### Partnership
[TABLE]
### Models and usage
[TABLE]
## Latest models
[Contact sales](https://claude.com/contact-sales)[Start building (opens in new tab)](../04-API-Reference/Other/playground.md)
Save 50% with batch processing. [Learn more](../04-API-Reference/Guides/build-with-claude-batch-processing.md)
Batch processing
### Fable 5.1
Next generation intelligence for long-running agents
Prompt caching
Read
\$0.25 / MTok
Write
\$12.50 / MTok
Input
\$10 / MTok
Output
\$50 / MTok
### Opus 5.5
Daily driver for agentic coding and enterprise work
Prompt caching
Read
\$0.20 / MTok
Write
\$5 / MTok
Input
\$4 / MTok
Output
\$20 / MTok
### Sonnet 5.5
High-performance model for coding and agents
Prompt caching
Read
\$0.10 / MTok
Write
\$2.50 / MTok
Input
\$2 / MTok
Output
\$10 / MTok
### Haiku 5.5
Fastest, most cost-efficient model
Prompt caching
Prompts ≤ 100K tokens
Read
\$0.01 / MTok
Write
\$0.125 / MTok
Prompts \> 100K tokens
Read
\$0.05 / MTok
Write
\$0.625 / MTok
Input
Prompts ≤ 100K tokens
\$0.10 / MTok
Prompts \> 100K tokens
\$0.50 / MTok
Output
Prompts ≤ 100K tokens
\$0.50 / MTok
Prompts \> 100K tokens
\$2.50 / MTok
For workloads that need to run in the US, US-only inference is available at 1.1x pricing for input and output tokens. [Learn more](../04-API-Reference/Other/manage-claude-data-residency.md).
Get up to 2.5x faster speeds with fast mode for Opus 5.5 at 2x standard pricing. [Learn more](about-claude-pricing.md#fast-mode-pricing).
Prompt caching pricing reflects 5-minute TTL. Learn about [extended prompt caching](../04-API-Reference/Guides/build-with-claude-prompt-caching.md#1-hour-cache-duration).
[Explore detailed pricing (opens in new tab)](about-claude-pricing.md)
## Pricing for Claude Platform features
Get more out of Claude with advanced features and capabilities.
[Learn more (opens in new tab)](about-claude-pricing.md#specific-tool-pricing)
### Managed Agents
Build and deploy agents at scale with a suite of composable APIs. Standard token rates apply.
Cost
\$0.08 per session-hour for active runtime
### Web search
Give Claude access to the latest information from the web. Doesn’t include input and output tokens required to process requests.
Cost
\$10 / 1K searches
### Code execution
Run Python code in a sandboxed environment for advanced data analysis. 50 free hours of usage daily per organization.
Additional hours
\$0.05 per hour per container
### Service tiers
Balance availability, performance, and predictable costs based on your needs.
[Learn more (opens in new tab)](../04-API-Reference/Endpoints/service-tiers.md)[Contact sales](https://claude.com/contact-sales)
- Standard
Default tier for both piloting and scaling everyday use cases
- Batch
For asynchronous workloads that can be processed together for better efficiency
## Legacy models
[Learn more (opens in new tab)](../20-Models/about-claude-models-overview.md)[Explore detailed pricing (opens in new tab)](about-claude-pricing.md)
### Haiku 4.5
Prompt caching
Read
\$0.10 / MTok
Write
\$1.25 / MTok
Input
\$1 / MTok
Output
\$5 / MTok
### Sonnet 5
Prompt caching
Read
\$0.20 / MTok
Write
\$2.50 / MTok
Input
\$2 / MTok
Output
\$10 / MTok
Save 50% with batch processing. [Learn more](../04-API-Reference/Guides/build-with-claude-batch-processing.md)
Batch processing
### Opus 5
Prompt caching
Read
\$0.50 / MTok
Write
\$6.25 / MTok
Input
\$5 / MTok
Output
\$25 / MTok
### Fable 5
Prompt caching
Read
\$1 / MTok
Write
\$12.50 / MTok
Input
\$10 / MTok
Output
\$50 / MTok
### Opus 4.8
Prompt caching
Read
\$0.50 / MTok
Write
\$6.25 / MTok
Input
\$5 / MTok
Output
\$25 / MTok
### Sonnet 4.6
Prompt caching
Read
\$0.30 / MTok
Write
\$3.75 / MTok
Input
\$3 / MTok
Output
\$15 / MTok
### Opus 4.7
Prompt caching
Read
\$0.50 / MTok
Write
\$6.25 / MTok
Input
\$5 / MTok
Output
\$25 / MTok
### Opus 4.6
Prompt caching
Read
\$0.50 / MTok
Write
\$6.25 / MTok
Input
\$5 / MTok
Output
\$25 / MTok
### Sonnet 4.5
Prompt caching
Read
\$0.30 / MTok
Write
\$3.75 / MTok
Input
\$3 / MTok
Output
\$15 / MTok
### Opus 4.5
Prompt caching
Read
\$0.50 / MTok
Write
\$6.25 / MTok
Input
\$5 / MTok
Output
\$25 / MTok
Prompt caching pricing reflects 5-minute TTL. Learn about [extended prompt caching](../04-API-Reference/Guides/build-with-claude-prompt-caching.md#pricing).
## FAQ
Plans and usage
Billing and payments
Managing your plan
### Plans and usage
#### What do I get with Claude Pro?
The [Pro plan](what-is-the-pro-plan.md) gives you everything in a Free plan with more usage and more of Claude's capabilities. That includes Claude Code, along with projects to organize your chats and documents, access to more Claude models, and Claude for Microsoft 365. You can choose a monthly or annual subscription.
#### How is Claude Max different from Pro?
The [Max plan](what-is-the-max-plan.md) is built for people who work with Claude throughout the day and want longer, uninterrupted sessions. You get everything in Pro, plus more usage: choose from 5x or 20x the usage of Pro per 5-hour session. Max also gives you higher output limits. Both options are billed monthly. See the cards above for current pricing.
#### What are the usage limits on each plan, and what happens when I hit them?
Every plan has [usage limits](usage-limit-best-practices.md) that reset on a rolling five-hour session window, and paid plans add weekly limits on top. Your activity across Claude on web, desktop, mobile, and Claude Code all draws from the same pool. How much you can do depends on the length and complexity of your conversations, the model you choose, and the features you use, so there's no fixed message count. Free covers everyday questions. Pro gives you at least 5x more usage per 5-hour session than Free. Max gives you 5x or 20x more usage per 5-hour session than Pro. On Team plans, Standard seats give more than Pro and Premium seats give 5x more than Standard. To manage capacity and make sure all users have fair access, we may limit your usage in other ways, such as weekly and monthly caps or model and feature usage, at our discretion. When you reach a limit, you can wait for it to reset, move to a higher plan, or, on paid plans, turn on [usage credits](https://support.claude.com/en/articles/12429409-manage-usage-credits-for-paid-claude-plans) to keep working at standard API rates. You can see where you stand anytime in [Settings \> Usage](https://claude.ai/settings/usage).
#### Is Claude Code included in my plan?
[Claude Code](../15-Claude-AI-Features/product-claude-code-fad1ab4b.md) is included in all paid plans. It shares the same usage limits as the rest of your plan, so your work in the terminal and your chats draw from one pool. For heavy coding sessions, you can also switch to pay-as-you-go API credits through a [Console account](../04-API-Reference/Other/playground.md).
#### How much does the Claude Enterprise plan cost?
The [Claude Enterprise plan](pricing-enterprise.md) is built for large businesses operating at scale. Pricing is \$20 per seat per month plus usage billed at API rates, so cost scales with the models and tasks your team runs. Enterprise is billed annually and includes everything in Team plus advanced security and admin controls, including SCIM, audit logs, custom data retention, and role-based access. You can get started self-serve or [contact sales](https://claude.com/contact-sales) for a tailored quote.
### Billing and payments
#### Can I pay annually? Does it cost less than if I pay monthly?
Yes, annual plans are designed to cost less than monthly subscriptions. Annual subscriptions are available for Pro and Team plans. Enterprise plans are only available as annual subscriptions.
When you choose to pay annually, you're billed once up front for the year. If you're already on a monthly plan, you can switch to annual in [Settings \> Billing](https://claude.ai/settings/billing), and any unused time is credited toward your first annual invoice. See the steps for [Pro](how-to-change-your-pro-plan-from-monthly-to-annual-billing.md) and [Team](change-your-team-plan-from-monthly-to-annual-billing.md).
#### Does Claude offer refunds?
Payments are generally non-refundable, except where our [Consumer Terms of Service](https://www.anthropic.com/legal/consumer-terms) say otherwise or where local law requires it.
Customers outside of Europe can follow this process to [request a refund](requesting-a-refund-for-a-paid-claude-plan.md):
- Log in, open Get help from the menu, start a message, and choose Claude Refund Request to check your eligibility.
- If you subscribed through the App Store, [Apple](https://support.apple.com/billing) handles the refund, so you'll request it from Apple.
- If you subscribed through Google Play, [contact our Support team](../15-Claude-AI-Features/how-to-get-support.md) to check eligibility for an active subscription.
If you're in the European Economic Area and the United Kingdom, and within your 14-day withdrawal period, you can request a refund directly in the app.
### Managing your plan
#### How do I upgrade, downgrade, or switch between plans?
You can change your plan any time in Settings.
- For individual plans, go to [Settings \> Billing](https://claude.ai/settings/billing) and choose Manage subscription.
- On Team plans, an Owner or Primary Owner manages this under Organization settings \> Billing. [See more details here](https://support.claude.com/en/articles/12004354-purchase-and-manage-seats-on-team-plans).
Upgrades take effect right away, and any unused time on your current plan is credited toward the new one, so you won't pay twice for the same days.
Moving from monthly to annual works the same way, with your remaining time credited to the first annual invoice.
In some upgrades (for example Pro Annual to Max 5x Monthly), your remaining value on your old plan is larger than the cost of one billing period of the new plan. In this case, the excess will be stored as credit, which will automatically get used for future purchases.
Downgrades take effect at the end of your current billing period, and your chats, projects, and files stay with your account whichever plan you're on.
#### How do I cancel my Claude subscription?
You can cancel anytime, and your plan stays active until the end of your current billing period. To avoid the next charge, cancel at least 24 hours before your renewal date.
- If you signed up on the web or the desktop app, go to [Settings \> Billing](https://claude.ai/settings/billing) and click Cancel.
- If you subscribed through the App Store or Google Play, cancel from that app under Billing \> Manage subscription, or directly in your [Apple](https://support.apple.com/en-us/118428) or [Google Play](https://support.google.com/googleplay/answer/7018481) account.
- Team and self-serve Enterprise: an Owner or Primary Owner cancels under [Organization settings \> Billing](https://claude.ai/admin-settings/billing).
- Sales-assisted Enterprise: Reach out to your Anthropic Contact or our Sales team to discuss cancellation.
Canceling doesn't delete your data. Your chats, projects, and files stay with your account, though some features aren't available on the Free plan. For Pro and Max, your account moves to the Free plan once the period ends. For step-by-step help, see [how to cancel a Pro or Max plan](how-do-i-cancel-my-paid-claude-subscription.md) or [cancel a Team plan](cancel-your-organization-s-team-plan-subscription.md).
[](https://www.claude.com/)
© 2026 Anthropic PBC
## Products
- [Claude](../15-Claude-AI-Features/product-overview.md)
- [Claude Code](../15-Claude-AI-Features/product-claude-code-fad1ab4b.md)
- [Claude Cowork](../15-Claude-AI-Features/product-cowork.md)
- [Claude Duet](../15-Claude-AI-Features/product-claude-duet.md)
- [Claude Tag](../15-Claude-AI-Features/product-tag.md)
- [Claude Science](../15-Claude-AI-Features/product-claude-science.md)
- [Claude Security](../15-Claude-AI-Features/product-claude-security.md)
- [Download app](https://www.claude.com/download)
- [Pricing](pricing.md)
- [Log in](https://claude.ai/login)
## Capabilities
- [Artifacts](https://www.claude.com/features/artifacts)
- [Design](../15-Claude-AI-Features/product-design.md)
- [Connectors](https://www.claude.com/marketplace/connectors-plugins)
- [Plugins](https://www.claude.com/marketplace/plugins)
- [Skills](https://www.claude.com/skills)
## Extensions
- [Claude in Chrome](https://www.claude.com/claude-in-chrome)
- [Claude for Google Workspace](https://www.claude.com/claude-for-google-workspace)
- [Claude for Microsoft 365](https://www.claude.com/claude-for-microsoft-365)
## Models
- [Mythos (including Fable)](../15-Claude-AI-Features/claude-mythos.md)
- [Opus](../15-Claude-AI-Features/claude-opus.md)
- [Sonnet](../15-Claude-AI-Features/claude-sonnet.md)
- [Haiku](../15-Claude-AI-Features/claude-haiku.md)
## Enterprise
- [Overview](pricing-enterprise.md)
- [Claude Code for Enterprise](../15-Claude-AI-Features/product-claude-code-enterprise.md)
## Departments
- [Customer support](../18-Industry-UseCases/customer-support.md)
- [Cybersecurity](../18-Industry-UseCases/cybersecurity.md)
- [Legal](../18-Industry-UseCases/legal.md)
- [Sales](../18-Industry-UseCases/sales.md)
## Industries
- [Financial advisors](../18-Industry-UseCases/financial-advisors.md)
- [Financial services](../18-Industry-UseCases/finance.md)
- [Government](../18-Industry-UseCases/government.md)
- [Healthcare](../18-Industry-UseCases/healthcare.md)
- [Higher education](../18-Industry-UseCases/education.md)
- [K-12 teachers](../18-Industry-UseCases/teachers.md)
- [Life sciences](../18-Industry-UseCases/life-sciences.md)
- [Nonprofits](../18-Industry-UseCases/nonprofits.md)
- [Small business](../18-Industry-UseCases/small-business.md)
## Programs
- [Campus](../15-Claude-AI-Features/programs-campus.md)
- [Frontier Academy](../15-Claude-AI-Features/programs-frontier-academy.md)
- [Scientists](../15-Claude-AI-Features/programs-team-plan-for-scientists.md)
- [Startups](../15-Claude-AI-Features/programs-startups.md)
## Developers
- [Developer docs](../02-Claude-Code-CLI/code-home.md)
- [Developer blog](https://claude.dev)
- [Community](https://www.claude.com/community)
- [Console](../04-API-Reference/Other/home.md)
- [Engineering at Anthropic](https://www.anthropic.com/engineering)
## Platform
- [Overview](https://www.claude.com/platform/api)
- [Marketplace](https://www.claude.com/marketplace)
- [Claude on AWS](../04-API-Reference/Other/partners-claude-on-aws.md)
- [Google Cloud](../04-API-Reference/Other/partners-google-cloud.md)
- [Microsoft Foundry](../04-API-Reference/Other/partners-microsoft-foundry.md)
- [Managed Agents](https://www.claude.com/platform/claude-managed-agents)
## Resources
- [Overview](https://www.claude.com/resources)
- [Articles](https://www.claude.com/resources/articles)
- [Webinars](https://www.claude.com/resources/webinars)
- [Claude partner network](../04-API-Reference/Other/partners.md)
- [Claude Academy](https://academy.claude.com/)
- [Customer stories](../18-Industry-UseCases/customers.md)
- [Events](https://www.anthropic.com/events)
- [Powered by Claude](../04-API-Reference/Other/partners-powered-by-claude.md)
- [Service partners](https://www.claude.com/marketplace/service-partners)
## Help and security
- [Availability](https://www.anthropic.com/legal/supported-regions)
- [Check files](https://www.claude.com/check-files)
- [Regional compliance](https://www.claude.com/regional-compliance)
- [Report abuse](https://www.claude.com/form/anthropic-content-reporting)
- [Security and compliance](https://trust.anthropic.com/)
- [Status](https://status.anthropic.com/)
- [Support center](https://support.claude.com/en/)
## Company
- [Anthropic](https://www.anthropic.com/)
- [Careers](https://www.anthropic.com/careers)
- [Policy](https://www.anthropic.com/policy)
- [Research](../19-Reference/anthropic-com-research.md)
- [Anthropic news](../19-Reference/news.md)
- [Policy on the AI Exponential](https://www.anthropic.com/policy-on-the-ai-exponential)
- [Responsible Scaling Policy](../19-Reference/announcing-our-updated-responsible-scaling-policy.md)
- [Transparency](https://anthropic.com/transparency)
## Terms and policies
- Privacy choices
- [Privacy policy](https://www.anthropic.com/legal/privacy)
- [Responsible disclosure policy](https://www.anthropic.com/responsible-disclosure-policy)
- [Terms of service: Commercial](https://www.anthropic.com/legal/commercial-terms)
- [Terms of service: Consumer](https://www.anthropic.com/legal/consumer-terms)
- [Terms of Service: US K-12](https://anthropic.com/legal/k12-terms)
- [Data Processing Agreement: US K-12](https://anthropic.com/legal/k12-dpa)
- [Usage Policy](https://www.anthropic.com/legal/aup)
## Products
- [Claude](../15-Claude-AI-Features/product-overview.md)
- [Claude Code](../15-Claude-AI-Features/product-claude-code-fad1ab4b.md)
- [Claude Cowork](../15-Claude-AI-Features/product-cowork.md)
- [Claude Duet](../15-Claude-AI-Features/product-claude-duet.md)
- [Claude Tag](../15-Claude-AI-Features/product-tag.md)
- [Claude Science](../15-Claude-AI-Features/product-claude-science.md)
- [Claude Security](../15-Claude-AI-Features/product-claude-security.md)
- [Download app](https://www.claude.com/download)
- [Pricing](pricing.md)
- [Log in](https://claude.ai/login)
## Capabilities
- [Artifacts](https://www.claude.com/features/artifacts)
- [Design](../15-Claude-AI-Features/product-design.md)
- [Connectors](https://www.claude.com/marketplace/connectors-plugins)
- [Plugins](https://www.claude.com/marketplace/plugins)
- [Skills](https://www.claude.com/skills)
## Extensions
- [Claude in Chrome](https://www.claude.com/claude-in-chrome)
- [Claude for Google Workspace](https://www.claude.com/claude-for-google-workspace)
- [Claude for Microsoft 365](https://www.claude.com/claude-for-microsoft-365)
## Models
- [Mythos (including Fable)](../15-Claude-AI-Features/claude-mythos.md)
- [Opus](../15-Claude-AI-Features/claude-opus.md)
- [Sonnet](../15-Claude-AI-Features/claude-sonnet.md)
- [Haiku](../15-Claude-AI-Features/claude-haiku.md)
## Enterprise
- [Overview](pricing-enterprise.md)
- [Claude Code for Enterprise](../15-Claude-AI-Features/product-claude-code-enterprise.md)
## Departments
- [Customer support](../18-Industry-UseCases/customer-support.md)
- [Cybersecurity](../18-Industry-UseCases/cybersecurity.md)
- [Legal](../18-Industry-UseCases/legal.md)
- [Sales](../18-Industry-UseCases/sales.md)
## Industries
- [Financial advisors](../18-Industry-UseCases/financial-advisors.md)
- [Financial services](../18-Industry-UseCases/finance.md)
- [Government](../18-Industry-UseCases/government.md)
- [Healthcare](../18-Industry-UseCases/healthcare.md)
- [Higher education](../18-Industry-UseCases/education.md)
- [K-12 teachers](../18-Industry-UseCases/teachers.md)
- [Life sciences](../18-Industry-UseCases/life-sciences.md)
- [Nonprofits](../18-Industry-UseCases/nonprofits.md)
- [Small business](../18-Industry-UseCases/small-business.md)
## Programs
- [Campus](../15-Claude-AI-Features/programs-campus.md)
- [Frontier Academy](../15-Claude-AI-Features/programs-frontier-academy.md)
- [Scientists](../15-Claude-AI-Features/programs-team-plan-for-scientists.md)
- [Startups](../15-Claude-AI-Features/programs-startups.md)
## Developers
- [Developer docs](../02-Claude-Code-CLI/code-home.md)
- [Developer blog](https://claude.dev)
- [Community](https://www.claude.com/community)
- [Console](../04-API-Reference/Other/home.md)
- [Engineering at Anthropic](https://www.anthropic.com/engineering)
## Platform
- [Overview](https://www.claude.com/platform/api)
- [Marketplace](https://www.claude.com/marketplace)
- [Claude on AWS](../04-API-Reference/Other/partners-claude-on-aws.md)
- [Google Cloud](../04-API-Reference/Other/partners-google-cloud.md)
- [Microsoft Foundry](../04-API-Reference/Other/partners-microsoft-foundry.md)
- [Managed Agents](https://www.claude.com/platform/claude-managed-agents)
## Resources
- [Overview](https://www.claude.com/resources)
- [Articles](https://www.claude.com/resources/articles)
- [Webinars](https://www.claude.com/resources/webinars)
- [Claude partner network](../04-API-Reference/Other/partners.md)
- [Claude Academy](https://academy.claude.com/)
- [Customer stories](../18-Industry-UseCases/customers.md)
- [Events](https://www.anthropic.com/events)
- [Powered by Claude](../04-API-Reference/Other/partners-powered-by-claude.md)
- [Service partners](https://www.claude.com/marketplace/service-partners)
## Help and security
- [Availability](https://www.anthropic.com/legal/supported-regions)
- [Check files](https://www.claude.com/check-files)
- [Regional compliance](https://www.claude.com/regional-compliance)
- [Report abuse](https://www.claude.com/form/anthropic-content-reporting)
---
## Purchase and manage seats on Enterprise plans | Claude Help Center
Source: https://support.claude.com/en/articles/13393991-purchasing-and-managing-seats-on-enterprise-plans
Path: 17-Billing-Plans/purchasing-and-managing-seats-on-enterprise-plans.md
# Purchase and manage seats on Enterprise plans
This article covers how to add seats, manage your seat allocation, and handle member access on Enterprise plans. For pricing and billing details, see **[How am I billed for my Enterprise plan?](https://support.claude.com/en/articles/11526368-usage-based-enterprise-plans)**
**Permissions note:** Only Owners and Primary Owners can purchase seats and access **[Organization settings \> Organization and access](https://claude.ai/admin-settings/organization)**. Admins and above can reassign seat types for members in **[Organization settings \> Members](https://claude.ai/admin-settings/members)**. To check your role, click your name or initials in the lower left corner—your role is listed next to your organization's plan type.
For information on adding and removing members from your organization, see **[Manage members on Team and Enterprise plans](managing-members-on-team-and-enterprise-plans.md)**.
**Important:** The main sections of this article describe the current Enterprise seat model, which applies to all new Enterprise plans.
- If your organization was provisioned before the transition to the single Enterprise seat and you see **Chat** and **Chat + Claude Code** seat types in **[Organization settings \> Members](https://claude.ai/admin-settings/members)**, refer to **[Information for Chat and Chat + Claude Code plans](#h_2673e097fb)**.
- **[HIPAA-ready Enterprise organizations](hipaa-ready-enterprise-plans.md)** are an exception: they are provisioned with separate Chat and Chat + Claude Code seat types and are not eligible for the single Enterprise seat billing model.
- If you see **Standard** and **Premium** seat types, refer to **[Information for seat-based Enterprise plans](#h_6a78e30e26)**.
- Chat-only seats and Standard/Premium seats are no longer available for new contracts—both legacy plan types are transitioning to the single Enterprise seat at their next renewal.
------------------------------------------------------------------------
## Your seat type
Usage-based Enterprise plans use a single seat type: the **Enterprise seat**, priced per user per month (billed annually). This seat includes access to Claude on web, desktop, and mobile, as well as Claude Code.
Enterprise plans require a minimum of 20 seats.
------------------------------------------------------------------------
## Who can use a seat
Each Enterprise seat is assigned to one named individual, and only that person may use it. This applies to every Enterprise seat type, including legacy Chat, Chat + Claude Code, Standard, and Premium seats. This means:
- Only the assigned user may sign in to the account. Users can't share login credentials or let others use their account.
- Users can't use another user's account to get around their own spend limits or usage limits.
Reassigning a seat is meant for normal team changes, such as a user joining, leaving, or changing roles. It isn't designed for rotating one seat among several active users. To give someone else access, assign them their own seat.
------------------------------------------------------------------------
## Purchase new seats
You can add seats to your Enterprise plan at any time during your annual term. New seats are prorated for the remainder of your billing cycle and charged immediately.
1. Log in with your Owner or Primary Owner account.
2. Go to **[Organization settings \> Organization and access](https://claude.ai/admin-settings/organization)**.
3. Click "Manage" under **Total seats**.
4. Click "Add or change seats."
5. Enter the number of seats you'd like to add.
6. Review your changes and the prorated charge before confirming.
7. Click "Confirm & purchase" to finalize.
**Note:** You can also purchase a seat while adding a new member. If you don't have an available seat when inviting someone, you'll be prompted to purchase one.
For details on how seat additions are billed, see **[How am I billed for my Enterprise plan?](how-am-i-billed-for-my-enterprise-plan.md)**
------------------------------------------------------------------------
## Remove seats
**Self-serve Enterprise plans:** Seats cannot be removed during your annual term. You can add seats at any time, but reductions to your seat count only take effect at renewal. If you need to make an exception, contact **[our Sales team](https://claude.com/contact-sales)** to discuss converting to a sales-assisted plan.
**Sales-assisted Enterprise plans:** Contact your account manager to discuss changes to your seat allocation.
Removing a member from your organization is different from reducing your seat count. When you remove a member, their seat becomes available to assign to someone else, so your total seat allocation and bill don't change. To reduce your bill, you'll need to reduce your total seat allocation. See **[Manage members on Team and Enterprise plans](managing-members-on-team-and-enterprise-plans.md)** for instructions on removing members.
------------------------------------------------------------------------
## Temporarily remove a member's access
The **No seat assigned** option lets you temporarily remove a member's access to Claude without removing them from your organization. This is useful for contractors or team members who need intermittent access.
To unassign a member:
1. Go to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
2. Find the member you want to unassign.
3. Click the dropdown under **Tier**.
4. Select "No seat assigned."
To restore their access, repeat the process and select “Enterprise seat.”
**Note:** Members with no seat assigned remain part of your organization but can't use Claude until you reassign them a seat. They do not count toward your organization's seat limit. Pending invitations do count. If "Add member" is unavailable even though seats show as available, revoke pending invitations that won't be accepted, or purchase additional seats.
------------------------------------------------------------------------
## Seat assignment with JIT or SCIM provisioning
**[Users provisioned via JIT or SCIM](../13-Enterprise-Admin/setting-up-jit-or-scim-provisioning-to-manage-user-assignments-on-team-or-enterprise-plans.md)** are automatically assigned an Enterprise seat when they're added, provided one is available in your allocation. If no seat is available, provisioning will not complete until an owner purchases an additional seat.
Admins and above can manually adjust a member's status (e.g., remove their seat assignment) afterward in **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
------------------------------------------------------------------------
## Cancel your Enterprise plan
**Self-serve Enterprise plans:** An Owner or Primary Owner can cancel your plan from **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**. Cancellation takes effect at the end of your current annual billing cycle—your organization will continue to have access until then.
**Sales-assisted Enterprise plans:** Reach out to your Anthropic Contact or **[our Sales team](https://claude.com/contact-sales)** to discuss cancellation.
------------------------------------------------------------------------
## Information for Chat and Chat + Claude Code plans
**Important:** Chat and Chat + Claude Code are legacy seat types that are no longer available for new Enterprise contracts. This section only applies to organizations that were provisioned with these seat types before the transition to the single Enterprise seat. If you recently signed a new Enterprise contract, the main sections of this article apply to you—your plan uses the single Enterprise seat, which includes Claude Code access for all members.
Some existing usage-based Enterprise organizations currently have two seat types: **Chat** and **Chat + Claude Code**. If you see these seat types in **[Organization settings \> Members](https://claude.ai/admin-settings/members)**, this section applies to you. Your plan will transition to the single Enterprise seat model at your next contract renewal—see below for more information.
### Seat types
[TABLE]
You can mix and match seat types based on your team's needs. Assign Chat + Claude Code seats to team members who need coding workflows, while keeping others on Chat seats.
### Reassign users between seat types
You can move users between Chat and Chat + Claude Code seats within your existing allocation.
1. Go to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
2. Find the member you want to reassign.
3. Click the dropdown under **Tier**.
4. Select "Chat" or "Chat + Claude Code."
Members moved from Chat + Claude Code to Chat will lose Claude Code access, and vice versa.
The **Tier** dropdown only shows seat types your plan already owns. If your plan includes Chat + Claude Code seats but they're all assigned, you'll be prompted to purchase one. If your plan has no seats of that type, see **[Purchase new seats](#h_91344d9191)** above to add one first.
### Swap users between seat types
If all your Chat + Claude Code seats are assigned and you need to move one user to that type while moving another off it, use **No seat assigned** to free up a seat first.
**Example:** You have ten Chat + Claude Code seats, all assigned. You want to move User A (currently on Chat + Claude Code) to Chat, and move User B (currently on Chat) to Chat + Claude Code — without purchasing an additional seat.
1. Go to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
2. Find User A and change their seat type to "No seat assigned." This frees up one Chat + Claude Code seat.
3. Find User B and change their seat type to "Chat + Claude Code." They now occupy the freed seat.
4. Find User A and change their seat type to "Chat."
### Seat assignment with JIT or SCIM provisioning
Users provisioned via JIT or SCIM are automatically assigned to the highest-available seat type (Chat + Claude Code, if available) when they're added. Admins and above can manually reassign seat types afterward in **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
You can also use Advanced Group Mappings with JIT or SCIM to provision users directly to a specific seat type.
### Transition to the single Enterprise seat
**Note: [HIPAA-ready organizations](hipaa-ready-enterprise-plans.md)** are provisioned with separate Chat and Chat + Claude Code seat types and are not eligible for the unified seat type.
At your next renewal, you will switch to the single Enterprise seat model upon signing a new contract. This seat includes Claude Code, Cowork, Chat and more.
Reach out to your Anthropic Contact or **[our Sales team](https://claude.com/contact-sales)** with questions about your upcoming renewal.
------------------------------------------------------------------------
## Information for seat-based Enterprise plans
**Important:** Standard and Premium are legacy seat types that are no longer available for new Enterprise contracts. This section only applies to organizations that were provisioned with these seat types before the transition to usage-based billing. If you recently signed a new Enterprise contract, the main sections of this article apply to you.
Some Enterprise organizations are on older seat-based plans with a different billing structure than the usage-based model described above. If you see **Standard** and **Premium** seats in **[Organization settings \> Members](https://claude.ai/admin-settings/members)**, this section applies to you.
### Seat types
[TABLE]
**Note:** Only Admins and above can see each user’s seat type, shown in the **Tier** column in **[Organization settings \> Members](https://claude.ai/admin-settings/member)**. Other users can’t see their own seat type anywhere in Claude. If you need to confirm whether your seat is Standard or Premium, ask an Owner or Admin in your organization.
### Reassign users between seat types
You can move users between Standard and Premium seats within your existing allocation.
1. Go to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
2. Find the member you want to reassign.
3. Click the dropdown under **Tier**.
4. Select "Standard" or "Premium."
Members moved from Premium to Standard will have lower usage limits, and vice versa.
The **Tier** dropdown only shows seat types your plan already owns. If your plan includes Premium seats but they're all assigned, reassigning another user to Premium will prompt you to purchase an additional seat. If your plan has no seats of that type, see **[Purchase new seats](#h_91344d9191)** above to add one first.
### Swap users between seat types
If all your Premium seats are assigned and you need to move one user to Premium while moving another to Standard, use **No seat assigned** to free up a seat first.
**Example:** You have ten Premium seats, all assigned. You want to move User A (currently on Premium) to Standard, and move User B (currently on Standard) to Premium—without purchasing an additional seat.
1. Go to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
2. Find User A and change their seat type to "No seat assigned." This frees up one Premium seat.
3. Find User B and change their seat type to "Premium." They now occupy the freed seat.
4. Find User A and change their seat type to "Standard."
### Billing and usage credits
Seat-based Enterprise plans charge a flat monthly fee per seat that includes usage limits. Owners can enable usage credits to allow team members to continue working after reaching their seat's usage limits. For details, see **[Manage usage credits for Team and seat-based Enterprise plans](https://support.claude.com/en/articles/12005970-)**.
For specific information about seat-based Enterprise pricing, reach out to your Anthropic Contact or **[our Sales team](https://claude.com/contact-sales)**.
### Transition to the single Enterprise seat
At your next contract renewal, your plan will transition to the usage-based single Enterprise seat model described in the main sections of this article. If you'd like to migrate before your renewal, reach out to your Anthropic Contact or **[our Sales team](https://claude.com/contact-sales)**.
---
## Purchase and manage seats on Team plans | Claude Help Center
Source: https://support.claude.com/en/articles/12004354-purchasing-and-managing-seats-on-team-plans
Path: 17-Billing-Plans/purchasing-and-managing-seats-on-team-plans.md
# Purchase and manage seats on Team plans
Seat management allows Team plan owners to control their organization's seat allocation, assign users to different seat types, and manage billing. For pricing and billing details, see **[How is my Team plan bill calculated?](how-is-my-team-plan-bill-calculated.md)**
**Permissions note:** Only Owners and Primary Owners can purchase seats and access **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**. Admins and above can reassign seat types for members in **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
For information on adding and removing members from your organization, see **[Manage members on Team and Enterprise plans](https://support.claude.com/en/articles/13133750)**.
------------------------------------------------------------------------
## Understanding seat types
Team plans offer two seat types:
[TABLE]
Organizations can mix and match seat types based on team needs. Assign Premium seats to power users who need more capacity, while keeping other team members on Standard seats.
Your plan has a total seat allocation (e.g., 30 Standard seats and 10 Premium seats). Within that allocation, you can assign and reassign users to different seat types as needed.
**Note:** Only Admins and above can see each user’s seat type, shown in the **Tier** column in **[Organization settings \> Members](https://claude.ai/admin-settings/member)**. Other users can’t see their own seat type anywhere in Claude. If you need to confirm whether your seat is Standard or Premium, ask an Owner or Admin in your organization.
------------------------------------------------------------------------
## Who can use a seat
Each seat on a Team plan is assigned to one named individual, and only that person may use it. This means:
- Only the assigned user may sign in to the account. Users can't share login credentials or let others use their account.
- Users can't route their work through another user's account to use that user's remaining usage.
- Unused usage on one seat can't be transferred to another user.
If a user regularly needs more capacity, an owner can move them to a Premium seat or turn on usage credits. Learn more about **[managing usage credits for Team and seat-based Enterprise plans](https://support.claude.com/en/articles/12005970)**.
Reassigning a seat is meant for normal team changes, such as a user joining, leaving, or changing roles. It isn't designed for rotating one seat among several active users.
------------------------------------------------------------------------
## Purchase new seats
**Important:** If you want to upgrade an existing member from Standard to Premium and already have Premium seats available, you don't need to purchase a new seat. Use the seat tier reassignment in **[Organization settings \> Members](https://claude.ai/admin-settings/members)** instead. See **[Upgrade a Standard seat to Premium](#h_e7a7f4f396)** below.
Follow these steps to add seats to your plan's total allocation:
1. Log in with your Owner or Primary Owner account.
2. Navigate to **[Organization settings \> Organization and access](https://claude.ai/admin-settings/organization)**.
3. Click "Manage" under "Total seats."
4. In the "Seat breakdown" modal, click "Add or change seats."
5. Click the "+" next to the seat type you want to add (Standard or Premium).
6. Click "Next" to review your purchase details and confirm the billing impact.
7. Check the confirmation box before continuing.
8. Click "Confirm & purchase" to complete the transaction.
**Note:** You can also purchase seats while adding a new member. The seat type selector only shows seat types your plan already owns—if all seats of the selected type are assigned, you'll be prompted to purchase one.
------------------------------------------------------------------------
## Reduce your seat allocation
You can reduce the total number of seats on your Team plan:
1. Log in with your Owner or Primary Owner account.
2. Navigate to **[Organization settings \> Organization and access](https://claude.ai/admin-settings/organization)**.
3. If needed, remove members or reassign them to free up the seats you want to eliminate.
4. Click “Manage” under **Total seats**.
5. Click “Add or change seats” in the **Seat breakdown** modal.
6. Click the "**-**" next to the seat type you want to reduce.
7. Click “Next” to review the changes.
8. Check the confirmation box and click "Confirm & purchase" to complete the change.
Reducing your organization's seat count takes effect at your next renewal (on the annual renewal date for annual plans). There is no prorated refund at the time you submit this change.
------------------------------------------------------------------------
## Assign and reassign seat types
You can move users between Standard and Premium seats within your existing allocation.
To reassign a user's seat type:
1. Go to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
2. Find the member you want to reassign.
3. Click the dropdown under **Tier**.
4. Select "Standard" or "Premium."
Members moved from Premium to Standard will have lower usage limits, and vice versa.
To move several members from Premium to Standard, do not use the per-member **Tier** dropdown. Instead, open **Organization and access**, click "Manage" under **Total seats**, then "Add or change seats," and set the Premium and Standard totals in one submission. You can set Premium below the number of members currently assigned to it: those members are moved onto Standard seats automatically at renewal. The Standard total cannot be lower than your current billable members.
Only one scheduled seat change can be pending at a time. Submitting a new one, adding seats, or accepting a new invite replaces the pending change.
Moving a member from Premium to Standard takes effect at your next renewal (on the annual renewal date for annual plans). There is no prorated refund at the time you submit this change.
------------------------------------------------------------------------
## Upgrade a Standard seat to Premium
Upgrading a member from Standard to Premium is a reassignment, not a new purchase. You don't need to buy an additional seat unless your Premium allocation is already full.
**Note:** The **Tier** dropdown only shows seat types your plan already owns. If your plan has zero Premium seats, Premium won't appear as an option yet. First add at least one Premium seat by following the steps in **[Purchase new seats](#h_f05a756e78)** above. Once your plan includes a Premium seat, you can select "Premium" from the dropdown.
1\. Go to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
2\. Find the member assigned to a Standard seat you want to upgrade.
3\. Click the dropdown under **Tier**.
4\. Select "Premium."
If your plan includes Premium seats but they're all assigned, you'll be prompted to purchase an additional one at this point. The upgrade is prorated based on your billing cycle, and you'll be charged the price difference immediately.
### What if I don't have an available seat?
If your plan includes Premium seats but they're all assigned, reassigning another user to Premium will prompt you to purchase an additional Premium seat. If your plan has no Premium seats at all, see **[Purchase new seats](#h_f05a756e78)** above to add one first.
------------------------------------------------------------------------
## Swap users between seat types
Selecting **No seat assigned** lets you temporarily remove a user from a seat without removing them from your organization. This is useful when you need to swap people between seat types within your existing allocation.
**Example:** You have five Premium seats, all assigned. You want to move User A (currently on Premium) to Standard, and move User B (currently on Standard) to Premium—without purchasing an additional seat.
1. Go to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
2. Find User A and change their seat tier to "No seat assigned." This frees up one Premium seat.
3. Find User B and change their seat tier to "Premium." They now occupy the available Premium seat.
4. Find User A and change their seat tier to "Standard."
**Note:** Members with no seat assigned remain part of your organization but can't use Claude until you reassign them a seat. They do not count toward your organization's seat limit. Pending invitations do count. If "Add member" is unavailable even though seats show as available, revoke pending invitations that won't be accepted, or purchase additional seats.
------------------------------------------------------------------------
## Seat assignment with JIT or SCIM provisioning
**[Users provisioned via JIT or SCIM](../13-Enterprise-Admin/setting-up-jit-or-scim-provisioning-to-manage-user-assignments-on-team-or-enterprise-plans.md)** are automatically assigned to the highest-available seat type when they're added. Admins and above can manually reassign seat types afterward in **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
You can also enable group mappings with JIT or SCIM to provision users directly to a specific seat type.
------------------------------------------------------------------------
## Understanding billing
- **New seats** are prorated based on your billing cycle and charged immediately.
- **Seat type upgrades** (Standard → Premium) are prorated and charged immediately for the price difference.
- **Removing members** does not trigger an immediate credit or refund. The seat becomes available to assign to another member. To reduce your bill, you'll need to reduce your plan's total seat allocation.
For detailed billing calculations and examples, see **[How is my Team plan bill calculated?](how-is-my-team-plan-bill-calculated.md)**
---
## Request a refund for a paid Claude plan | Claude Help Center
Source: https://support.claude.com/en/articles/12386328-requesting-a-refund-for-a-paid-claude-plan
Path: 17-Billing-Plans/requesting-a-refund-for-a-paid-claude-plan.md
# Request a refund for a paid Claude plan
**Important:** Except as expressly provided in our **[Consumer Terms of Service](https://www.anthropic.com/legal/consumer-terms)** or where required by law, all payments are non-refundable.
To request a refund for a payment defined as refundable in our Terms of Service, follow these instructions:
1. Log in to your account and click on your initials or name in the lower left corner.
2. Select "Get help" from the menu to open a messenger on the right side of the window.
3. Click the "Send us a message" button.
4. Click "Accept," then "Claude Refund Request" from the available options.
5. Select your refund reason from the available options.
6. Follow the prompts to check your refund eligibility.
7. If eligible, continue in the support messenger to cancel and refund your plan.
**Note:** If you’ve claimed monthly API credits on a Max or Team plan, new credits stop when your plan is refunded. Credits you already have stay usable until they expire and can’t be refunded.
------------------------------------------------------------------------
## Refunds for customers in the European Economic Area (EEA) and the United Kingdom (UK)
In the European Economic Area and the United Kingdom, you may receive a refund within 14 days of purchase. You may find this option available in your **Settings**. Your refunds will be prorated according to your use.
------------------------------------------------------------------------
## What should I do if I can't access the account I'm requesting a refund for?
If you're unable to log in to the account associated with your payment (for example, if you can't access the email account you used to sign up), you'll need to **[contact our Support team](../15-Claude-AI-Features/how-to-get-support.md)** using another email and 'cc' the email address tied to the account you can't access. Write back to cancel your paid plan and request a refund so our team can assist.
## I paid for my plan on Claude for iOS—what's the process for requesting a refund?
If you paid for your plan on **[Claude for iOS](https://support.claude.com/en/collections/9879000-claude-for-ios)**, this means your subscription was purchased through the Apple App Store. Apple processed this payment, so only Apple can review and issue a refund—our Support team can't access or refund App Store charges.
To request a refund from Apple:
1. Sign in at **reportaproblem.apple.com** with the Apple Account you used to purchase your subscription.
2. Tap or click "I'd like to," then choose "Request a refund."
3. Choose the reason for your refund request, then click "Next."
4. Select your Claude subscription, then click "Submit."
Apple will review your request and notify you of their decision. You can check the status of your request any time by returning to reportaproblem.apple.com. Refunds for App Store purchases are granted at Apple's discretion.
**Note:** Requesting a refund doesn't cancel your subscription. To avoid future charges, you'll also need to cancel. For instructions, see **[Cancel your Pro or Max subscription](https://support.claude.com/en/articles/8325617)**.
For more details, see Apple's guide: **[Request a refund for apps or content that you bought from Apple](https://support.apple.com/en-us/118223)**.
## I paid for my plan on Claude for Android—what's the process for requesting a refund?
If you have an active subscription purchased on **[Claude for Android](https://support.claude.com/en/collections/9879004-claude-for-android)**, our Support team will need to check your eligibility before assisting with a refund. When contacting us, provide any relevant details upfront so our team can help with your request.
If you're requesting a refund for an inactive subscription, you'll need to **[contact our Support team](../15-Claude-AI-Features/how-to-get-support.md)** with the email address associated with your Google Play account or your GPA order number (found on your Google Play receipt, formatted GPA.xxxx-xxxx-xxxx-xxxxx) to further review the charge and refund eligibility.
### I upgraded from Pro or Max to Team—when do I get my refund?
When you upgrade to a Team plan from a Pro or Max plan, your individual subscription is cancelled automatically and you receive a prorated refund for the unused portion of your billing period. You don't need to request it manually. The refund is issued about 24 hours after your Team payment goes through, and depending on your bank, it can take several more business days to appear on your statement. Google Play purchases don't have this wait, but the refund can take a few days to appear. Any prepaid usage credits on your individual account are refunded.
If you claimed monthly API credits on your Max plan, your Max link ends. A Team Owner or Primary Owner can claim the team’s credits once the Team plan has been active for seven days.
If you signed up for Pro or Max through the Apple App Store, you can't upgrade to Team in place. **[Cancel your iOS subscription](https://support.claude.com/en/articles/8325617-cancel-your-pro-or-max-subscription#h_54384c9962)** through your Apple ID settings first, then start the Team upgrade. App Store subscription refunds need to be requested through Apple directly, as described above.
For full upgrade details, see **[Get started with the Team plan](get-started-with-the-team-plan.md#h_830eec632d)**.
## How do I request a refund when I'm disputing the payment?
Our Support team cannot process refunds during pending disputes, as the disputed funds are pulled back immediately. You can choose to either continue working with your bank until the dispute is resolved, or to withdraw the bank dispute, which will allow us to process a refund.
---
## Set up browser use in Claude Cowork for Team and Enterprise plans | Claude Help Center
Source: https://support.claude.com/en/articles/16635803-set-up-browser-use-in-claude-cowork-for-team-and-enterprise-plans
Path: 17-Billing-Plans/set-up-browser-use-in-claude-cowork-for-team-and-enterprise-plans.md
# Set up browser use in Claude Cowork for Team and Enterprise plans
**Note:** Claude Cowork and chat are now one Claude. Ask for what you need, and Claude decides whether that’s a quick answer or a task. This is rolling out gradually to Pro and Max plans, and it’s in beta for Enterprise plans, where an admin turns it on as **Chat and Cowork unified (beta)**. Team organizations, and Enterprise organizations that haven’t turned it on, keep chat and Claude Cowork as they are today, so everything in this article still applies. If you’re an Enterprise admin, learn more in **[Set up and manage the new unified Claude experience for your Enterprise organization](../13-Enterprise-Admin/set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization.md)**, or read our **[blog post](https://claude.com/blog/cowork-is-now-claude)**.
Claude can use the web in Claude Cowork in two ways: a browser built into the Claude Desktop app, or your users' own Chrome browser through the Claude in Chrome extension. This article explains the difference, how to enable each one for your organization, and what your users see when both are on.
Browser controls for Cowork are available on Team and Enterprise plans. The built-in browser is rolling out gradually this week and works in the Claude Desktop app on macOS, Windows, and Linux (beta). The **Built-in browser** setting may not appear in Organization settings until the rollout reaches your organization. When the desktop app is online, the built-in browser is also available in Cowork on web or mobile.
## Two ways for Claude to use the web
- **Built-in browser.** Claude works in its own browser, which opens in the Claude side panel inside the Cowork desktop app. There's nothing to install. It's separate from users' own browsers, so Claude doesn't see their logins unless they choose to import them. It requires the desktop app to be open and online.
- **Claude in Chrome.** Claude works in the user's own Chrome browser through the Claude in Chrome extension, on the page they're already on, with the accounts they're already signed in to. Your users' browsers need the extension deployed or installed. Cowork sessions on web and mobile can also use Claude in Chrome when it's the user's preferred browser.
Both run the same safety layers: per-site permission prompts before Claude acts on a new site, a blocklist for high-risk sites, and safety checks on every action. Learn more in **[Use the built-in browser in Claude Cowork](https://support.claude.com/en/articles/16607400)** and **[Use Claude in Chrome safely](https://support.claude.com/en/articles/12902428)**.
You can enable one, both, or neither.
## Enable or disable the built-in browser
- **Team plans:** On by default as it rolls out.
- **Enterprise plans:** It turns on by default unless you've turned it off. In organizations that have enabled HIPAA, the built-in browser stays off until an Owner turns it on in **Organization settings \> Cowork**. With the **[HIPAA configuration applied to Claude Code (local mode) and Cowork (local mode)](https://support.claude.com/en/articles/17318731)**, the built-in browser isn't available, and no setting turns it on.
To turn the built-in browser on or off for your organization:
1. Sign in to Claude as an Owner or Primary Owner.
2. Navigate to **[Organization settings \> Cowork](https://claude.ai/admin-settings/cowork)**.
3. Find **Built-in browser** and turn it on or off.
When the built-in browser is off, users can't open it and Claude can't use it. This setting doesn't affect Claude in Chrome or the browser in Claude Code.
**Note:** On Enterprise plans, users aren't notified automatically when you turn the built-in browser on. You may want to communicate availability through your internal channels.
## Enable or disable Claude in Chrome
Claude in Chrome is managed separately, in **[Organization settings \> Claude in Chrome](https://claude.ai/admin-settings/browser-extension)**. It's on by default on Team plans. On Enterprise plans, it turns on by default unless you've already disabled it. In organizations that have enabled HIPAA, the Claude in Chrome extension stays off until an Owner turns it on in **Organization settings \> Claude in Chrome**. Site allowlists and blocklists you configure there apply to both the extension and the built-in browser. The same list governs both, so there's no separate list to maintain. For setup, deployment, and pilot guidance, see **[Claude in Chrome admin controls](https://support.claude.com/en/articles/13065128)**.
## When both are enabled
If your organization has both the built-in browser and Claude in Chrome turned on, each user chooses which one Claude uses with the **Preferred browser** toggle in **[Settings \> Cowork](https://claude.ai/settings/cowork)**. Users who already use Claude in Chrome keep it as their preferred browser. Users who don't have the extension get the built-in browser.
Claude uses the preferred browser for web tasks. If the preferred browser isn't available when a task needs one:
- If the user asked Claude to use a browser generally, Claude tells them their preferred browser is offline and continues with the other one.
- If the user asked for a specific browser by name, Claude tells them it's unavailable and asks before using the other one.
The preferred browser setting also applies to Cowork sessions on web and mobile. A session started on web or mobile uses the built-in browser when it's the user's preference and the desktop app is open and online. If Claude in Chrome is the preference, the session uses the extension. For web and mobile sessions to use Claude in Chrome, they must be connected to a desktop, but the app doesn't have to be open.
---
## Set up role-based permissions on Enterprise plans | Claude Help Center
Source: https://support.claude.com/en/articles/13930458-set-up-role-based-entitlements-on-enterprise-plans
Path: 17-Billing-Plans/set-up-role-based-entitlements-on-enterprise-plans.md
# Set up role-based permissions on Enterprise plans
This guide walks you through setting up role-based permissions for your Enterprise organization. This lets you control which features and connectors specific teams or groups of members can access, and delegate specific admin access like billing or user management, rather than giving everyone the same permissions.
Before you start, make sure you're familiar with:
- **[Manage groups and group spend limits on Enterprise plans](manage-groups-and-group-spend-limits-on-enterprise-plans.md)** — how to create and manage groups
- **[Manage custom roles on Enterprise plans](manage-custom-roles-on-enterprise-plans.md)** — how custom roles and capabilities work
------------------------------------------------------------------------
## Before you begin
You'll need Owner or Primary Owner access to your Enterprise organization, or a custom role with Identity & Access set to Manage.
**Note:** Some of these steps require more than the Identity & Access custom role: enabling features at the organization level requires the Owner role, and changing member roles requires User Management set to Manage.
**Check which capabilities are enabled at the org level.** Go to **Organization settings** and ensure you know which capabilities members can access currently. For settings managed by RBAC, both the org setting and role setting are required to be on for users to get access.
**Back up your member list.** Export a CSV of your current members from **[Organization settings \> Members](https://claude.ai/admin-settings/members)** before making any changes. If something goes wrong during migration, this gives you a reference to restore access. See **[Manage members on Team and Enterprise plans](https://support.claude.com/en/articles/13133750-manage-members-on-team-and-enterprise-plans)**.
**Determine which teams or functions need each capability.** For example, Engineering gets Claude Code + Fast Mode and Marketing gets Cowork + Web Search. From here, define your custom roles.
**Dual-seat plans.** If your organization is on a dual-seat Enterprise plan (with Chat and Chat + Claude Code seats), custom roles don't override seat-level restrictions. A member assigned to a Chat-only seat can't access Claude Code even if their custom role grants it. The same applies in reverse: if a member's custom role doesn't grant the chat capability, they won't have chat access regardless of their seat type. Plan your role structure with seat assignments in mind.
**Note:** "Chat + Claude Code" refers to a seat type on legacy dual-seat plans. The "chat" capability in custom roles is separate—it governs chat access for any member whose role is set to "Custom" on any plan.
**Decide how you'll create groups.** You can create groups manually in Claude, or sync them from your identity provider (IdP) via SCIM. You can also use both methods simultaneously. If you plan to use IdP groups from Okta, Entra ID, or another provider, make sure SCIM directory sync is configured. See **[Set up JIT or SCIM provisioning](https://support.claude.com/en/articles/13133195-set-up-jit-or-scim-provisioning)**.
**Add the connectors you plan to govern.** Connector permissions only cover connectors that an Owner or Primary Owner has already added under **Organization settings \> Connectors** and connected with admin credentials. Review your organization-wide tool policy there as well, since role grants narrow within it and can’t widen past it. See **[Use connectors to extend Claude’s capabilities](https://support.claude.com/en/articles/11176164-)**.
------------------------------------------------------------------------
## Planning your role structure
Before creating anything, decide which features each team or group of members should have access to. Here are four common patterns:
### Base plus additive roles
This is the recommended approach for most organizations. Create a "Standard Access" role for everyone with common features like web search, memory, and projects. Then create additive roles that grant specific capabilities — for example, a "Cowork Enabled" role that only adds Cowork. Assign all members to the base role through an "All Users" group, and add specific members to additional groups that layer on extra features.
This pattern is flexible because permissions are additive — combining a base role with additive roles composes cleanly without conflicts.
### Tier-based roles
Create distinct tiers: "Full Access" with all features, "Standard Access" with most features, and "Restricted Access" with minimal features. Each member goes into exactly one group assigned to one tier.
### Department-based roles
Create roles that map to departments: "Engineering" with chat, Cowork, Claude Code, and code execution; "Research" with chat, web search, memory, and projects; "Business" with chat, web search and projects only. Assign each department group to its corresponding role.
### Admin delegation roles
Create roles that delegate parts of administration without granting the Owner role. A custom role with admin permissions does not need any user capabilities, and vice versa. You could create a "Finance" role that grants Billing access but no chat or Claude Code capability, or an "Engineering Lead" role that grants Claude Code plus Analytics view access. To give a role every admin permission an Owner has, turn on **Owner access** (beta). Learn more **[about admin permissions for custom roles](manage-custom-roles-on-enterprise-plans.md#h_536123d968)**.
------------------------------------------------------------------------
## Step 1: Audit your current settings
1. Review which features are currently enabled or disabled at the organization level in **[Organization settings \> Capabilities](https://claude.ai/admin-settings/capabilities)**.
2. Go to **[Organization settings \> Members](https://claude.ai/admin-settings/members)** to export or review your member list.
3. Note each member's current built-in role (User, Admin, or Owner).
4. For each team or department, decide which features they need access to.
Remember: any feature you want to control per-group must be **enabled** at the organization level. If a feature is toggled off at the organization level, no custom role can grant access to it.
**Important:** Unlike members with the User role, members assigned to custom roles don't automatically inherit organization-enabled capabilities. Every capability a "Custom" role member needs must be explicitly granted by a custom role assigned to one of their groups.
------------------------------------------------------------------------
## Step 2: Create custom roles
Create your custom roles before enabling any features or migrating members. This ensures your roles are ready to enforce access the moment features turn on.
1. Navigate to **[Organization settings \> Roles](https://claude.ai/admin-settings/roles)**.
2. Click "Add role."
3. Name the role and enable the appropriate capabilities on the **Capabilities** tab, or choose "All capabilities" or "All generally available" to grant everything at once:
4. On the **Permissions** tab, set admin permissions for the role. See **Step 3**.
5. On the **Connectors** tab, set connector permissions for the role. See **Step 4**.
6. On the **Models** tab, set model access and a default model for the role. See **Step 5**.
7. Click "Save."
8. Repeat for each role in your plan.
Role changes may take up to 15 minutes to take effect. Members may need to refresh their browser to see updated access.
See **[Manage custom roles on Enterprise plans](manage-custom-roles-on-enterprise-plans.md)** for details on available capabilities, admin permissions, and connectors.
------------------------------------------------------------------------
## Step 3: Configure admin permissions (optional)
Set admin permissions on each role to delegate access to admin settings, like billing, user management, or privacy, without granting the Owner role. This step is optional. If you don't configure it, roles grant no admin access and administration stays with Owners and Primary Owners. For what each permission area covers, see **[Manage custom roles on Enterprise plans](manage-custom-roles-on-enterprise-plans.md)**.
### Locate the Permissions tab
1. Navigate to **[Organization settings \> Roles](https://claude.ai/admin-settings/roles)**.
2. Open an existing role, or click “Add role” to create one.
3. Select the **Permissions** tab, between **Capabilities** and **Connectors**.
### Set admin permissions
The **Permissions** tab lists each admin area: Identity & Access, Billing, Analytics, Privacy, User Management, Libraries, and Directory. Set each admin area to one of the following options:
- **No access:** The member doesn't see this area in their organization settings.
- **Can view:** View grants read-only access. The member sees the same pages and settings as someone who can manage that area, but every control is disabled or shown as read-only. Use this permission level for compliance reviewers, finance auditors, security teams, or anyone who needs to see the configuration without changing it.
- **Can manage:** Manage grants full read and write access to the area and includes view access.
Within an area, you grant all of View or all of Manage. You can't grant or restrict individual pages or settings.
The **Permissions** tab also includes **Owner access** (beta), which gives the role all the admin permissions of an Owner. Only Owners, Primary Owners, and custom roles with Identity & Access set to Manage can turn it on. Learn more about **Owner access**.
**Note:** A role with Identity & Access set to Manage can create and edit groups and roles, including its own role definition, and can turn on **Owner access**. Members with this permission can expand their own access, so reserve it for trusted security and IT administrators.
### Verify enforcement
Verify admin permissions after you’ve migrated members to "Custom" roles (Step 7). See **Step 11: Verify and monitor**.
------------------------------------------------------------------------
## Step 4: Configure connector permissions (optional)
Set connector permissions on each role to control which connectors, and which tools on those connectors, the role can use. This step is optional. If you don’t configure it, your roles fall back to the default behavior described below. For how the permission model works end to end, see **[Manage custom roles on Enterprise plans](manage-custom-roles-on-enterprise-plans.md)**.
**Important:** When Anthropic enables connector permissions for your organization, every existing custom role is seeded with the “All connectors” grant at “Always allow.” Because “Always allow” is the most permissive grant, your organization-wide tool policy alone determines each member’s effective ceiling at enablement. Members neither gain nor lose access at enablement. Your first configuration pass narrows from that baseline.
**Note:** A newly created role defaults to “Needs approval” on every connector. The create-role flow steps through the Connectors tab so you see this default before saving. Raise a connector to “Always allow” or lower it to “Blocked” as needed.
### Locate the Connectors tab
1. Navigate to **[Organization settings \> Roles](https://claude.ai/admin-settings/roles)**.
2. Open an existing role, or click “Add role” to create one.
3. Select the **Connectors** tab, next to **Permissions**.
The default settings for new roles are permissive. When creating or modifying a role, confirm the settings on each tab to avoid granting unintended permissions.
### Set connector-level permissions
The **Connectors** tab lists an **All connectors** row at the top, followed by every connector your organization has added. Each row has a dropdown with four options:
- **Always allow:** Every tool on the connector is available, and members can set their own approval to “Always allow.”
- **Needs approval:** Every tool is available, but members confirm each call.
- **Blocked:** The connector is hidden from members with this role.
- **Custom:** Set each tool on the connector individually. See “Set per-tool permissions” below.
Choosing “Always allow,” “Needs approval,” or “Blocked” applies that level to every tool on the connector. The **All connectors** row works the same way one level up: it sets a baseline for every connector at once, including any connector you add later. Use it to set a role’s default, then override individual connectors.
### Set how members connect
The **How members connect** dropdown controls whether the role's members sign in to connectors with their own accounts or connect automatically through your identity provider:
- **Individually:** Members sign in to each connector with their own account.
- **Managed authorization:** Members connect through your identity provider automatically, without signing in themselves.
- **Set per connector:** Choose Individually or Managed authorization separately for each connector, instead of one setting for all of them.
If a connector has both **Individually** and **Managed authorization** turned on, Claude tries managed authorization first. If that fails, members can still sign in individually with their own account, so they're not locked out of the connector while an identity provider issue gets resolved.
Choosing **Individually** or **Managed authorization** in the **All connectors** row sets a baseline for every connector at once, including any connector you add later. Use it to set a role’s default, then override individual connectors.
### Set per-tool permissions
Set a connector to **Custom** to reveal its tools as individual rows. You can choose "Always allow," "Needs approval," or "Blocked" for each tool.
Per-tool permissions let a role reach part of a connector. For example, with Jira set to **Custom**, its `search_issues` tool set to “Needs approval,” and every other Jira tool set to “Blocked,” members with the role can search Jira but nothing else. Claude only sees the tools you’ve granted, so asking it to create a ticket returns “I don’t have a tool for that” rather than an error.
### Review cross-role conflicts
Because connector permissions are additive across roles, blocking a connector in one role has no effect on a member who also holds another role that grants it. Each connector row shows a warning when other roles grant the same connector at a different level. The warning names those roles and links to them, and the most permissive grant is the one that applies.
If you have unsaved edits when you open a linked role, you’re asked to discard them first.
### Verify enforcement
Verify connector permissions after you’ve migrated members to "Custom" roles (Step 7). See **Step 11: Verify and monitor**.
**Important:** If your organization uses Claude Code, enabling connector permissions also applies your organization-wide tool policy to Claude Code. This can only narrow tool access there, never widen it, and it affects all members. Review your organization-wide tool policy before enablement if Claude Code is widely deployed. Connector permissions and Claude Code Managed Settings compose by most-restrictive. See **[Claude Code settings](../02-Claude-Code-CLI/settings.md#settings-files)**.
**Note:** Whether members can set "Always allow" on write-capable connector tools in Cowork is additionally controlled by the organization setting **Allow "Always allow" for connector tools**, which is off by default. Role grants can't override it. Learn more about the **[Cowork approval setting for write tools](https://support.claude.com/en/articles/13455879-use-claude-cowork-on-team-and-enterprise-plans#h_1bd1fa754d)**.
------------------------------------------------------------------------
## Step 5: Configure model access (optional)
Set model access on each role to control which Claude models the role can use, cap the maximum effort level per model, and choose the model new conversations start on. This step is optional; if you don't configure it, new roles can use every model that's enabled at the organization level, at any effort level, and start on the organization default model.
For how the model access and default model settings work end to end, see **[Manage model access for your organization](https://support.claude.com/en/articles/15694740)** and **[Set a default model for your organization](https://support.claude.com/en/articles/15330088)**.
### Locate the Models tab
1. Navigate to **[Organization settings \> Roles](https://claude.ai/admin-settings/roles)**.
2. Open an existing role, or click "Add role" to create one.
3. Select the **Models** tab, next to **Connectors**.
### Set model access
Under **Model access**, turn each model on or off for this role. Models disabled at the organization level appear but can't be enabled here until you turn them on for the organization in **[Organization settings \> Models](https://claude.ai/admin-settings/models)**. Haiku models are always on and can't be disabled.
To cap the effort level a role can select on a model, click the gear icon next to the model and choose a level.
Under **Default model**, optionally select the model new conversations start on for this role. Only models the role has access to can be selected.
### Verify enforcement
Verify model access after you've migrated members to "Custom" roles. See **Step 11: Verify and monitor**.
------------------------------------------------------------------------
## Step 6: Create groups and assign roles
1. Navigate to **[Organization settings \> Groups](https://claude.ai/admin-settings/groups)**.
2. Click “Add group” to create a group for each team or tier in your plan.
3. Assign each group to the custom roles you created in step 2.
4. Add members to the appropriate groups.
If you use SCIM directory sync, you can sync groups from your identity provider instead of creating them manually. For details on SCIM group sync, see **[Manage groups and group spend limits on Enterprise plans](manage-groups-and-group-spend-limits-on-enterprise-plans.md)**.
**Multiple organizations under the same parent organization:** Groups are managed at the parent organization level and propagate to all child organizations. You may see members from other organizations listed in a group—this doesn't mean they have access to your organization. Custom roles assigned to a group only grant capabilities to members who are part of your specific organization.
If you request to move an organization from one parent to another (this is rare in practice), groups and roles will become undefined and you will need to re-create them.
**Important:** If your organization uses Invite only or JIT provisioning, you can only use manually created groups for RBAC. SCIM-synced groups aren't supported in these modes.
------------------------------------------------------------------------
## Step 7: Verify group and role assignments
Before migrating members to custom roles, confirm that every member you plan to migrate is in at least one group assigned to a custom role. Members who are migrated without group or role coverage will lose access to all governed features.
1. Navigate to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
2. Use the Role and Group filters to identify members who aren't assigned to any group.
3. Alternatively, click "Export CSV" to download the full member list with role and group columns for review.
4. Add any unassigned members to the appropriate groups before continuing.
------------------------------------------------------------------------
## Step 8: Migrate members to custom roles
For custom role capabilities to take effect, members must have their role set to "Custom." Members with the User, Admin, or Owner roles get their permissions from those roles directly, not from custom roles.
**Important:** Complete this step only after you’ve created your custom roles, configured admin and connector permissions if you’re using them, created your groups, and verified all members are assigned to groups. Members moved to custom roles before setup is complete will immediately lose access to all governed features and their previous role. Switching an Owner or Admin to custom roles removes their Owner or Admin access, so don't migrate Owners or Admins unless you intend to replace that access with custom role permissions. To keep an Owner's admin access, add them to a group whose role has **Owner access** turned on before you change their role.
Choose the migration path based on whether your organization already enabled group mappings:
### Path A: Enable group mappings (only if already in use)
Use this path only if your organization already enabled group mappings for role assignment. If you aren't already using this setting, skip to Path B.
1. Navigate to **[Organization settings \> Organization and access](https://claude.ai/admin-settings/organization)**.
2. In the role mappings section, assign the IdP groups you want governed by custom roles to the "Custom" role.
3. Save your changes. Members in those IdP groups are migrated to "Custom" roles on the next sync.
Members in IdP groups mapped to "Custom" roles follow the permissions of the custom roles assigned to their groups in Claude. Members in IdP groups mapped to User follow the organization-level capability settings. If a member is in groups across both mappings, "Custom" roles take precedence.
### Path B: Bulk assignment tool
Use this path if your organization hasn’t enabled group mappings.
**Warning:** If you didn’t already enable group mappings, do not enable it during RBAC setup. Enabling it without first assigning all members to mapped groups can result in members losing access to your organization.
1. Navigate to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**.
2. Use the Role and Group filters to select the members you want to migrate.
3. Click "Update \# selected."
4. Under **Action**, select "Change role."
5. Under **Role**, select "Custom."
6. Click "Update members."
We recommend migrating a pilot group first—one team or department—and verifying their access is correct before expanding to the rest of the organization.
### Gradual rollout
Whichever path you use, we recommend migrating in stages:
1. Start with a pilot group of one team or department.
2. After migration, verify the pilot group has the correct feature access based on their group and role assignments.
3. If something isn't right, switch the affected members back to their previous role while you adjust.
4. Expand to more members once you've confirmed the setup works.
------------------------------------------------------------------------
## Step 9: Enable features at the organization level
Only enable organization-level features after roles, groups, and member migration are complete. This ensures custom role capabilities are already in place, with no window where unauthorized members could access a feature.
For any feature you want to control per-group:
1. Navigate to the feature's settings page in **Organization settings** (for example, **[Organization settings \> Cowork](https://claude.ai/admin-settings/cowork)**).
2. Enable the feature at the organization level.
Enabling a feature at the organization level doesn't mean everyone gets it—custom role permissions are already in place to control who can use it. Think of the organization-level toggle as making the feature "available for role-based assignment" rather than "on for everyone."
**Note:** This includes the Design, Slides, and Docs settings in **[Organization settings \> Artifacts](https://claude.ai/admin-settings/artifacts)**. Users without the **Artifacts** capability can still open artifacts shared with them, comment on them, and change their data, up to Contributor access. They can't create, edit, publish, or share artifacts.
------------------------------------------------------------------------
## Step 10: Apply a group spend limit (usage-based orgs only)
To assign a per-user monthly spend limit to a group:
1. Navigate to the **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**.
2. Select the "By group/tier" tab under **Spend limits**.
3. Click "+."
4. Select a group then add a custom limit.
5. When you’re done, click "Add spend limit."
Note the following precedence rules:
- Individual limits always override group limits, regardless of which is higher.
- If a user belongs to multiple groups with different limits, the **Multi-group spend limit** setting under **Spending defaults** controls whether the higher or lower limit applies.
- Org-wide limits remain the hard ceiling.
Membership changes take effect automatically—users inherit or lose limits as soon as their group membership changes. Relevant only for usage-based billing orgs.
------------------------------------------------------------------------
## Step 11: Verify and monitor
1. **Spot-check access**: Open the "⋮" menu on a the right side of a member's row in **[Organization settings \> Members](https://claude.ai/admin-settings/members)** and select "View effective role." The modal shows every capability, admin permission, and connector the member has across all their roles, with a "Granted by" label naming which role provides each one. You can do the same for a group from **[Organization settings \> Groups](https://claude.ai/admin-settings/groups)**. For details, see **[Manage custom roles on Enterprise plans](https://support.claude.com/en/articles/13930452)**.
2. **Test the restricted state**: Log in as (or ask) a member who should not have a feature like Cowork. They should see it greyed out with the message "Contact your admin to request access to this feature."
3. **Test the granted state**: Confirm a member who should have the feature sees it working normally.
4. **Check edge cases**: Test members in multiple groups, members with no group, and new members joining via SSO.
**If you configured admin permissions, also check:**
- **Group and role assignments:** Owners can verify a member's access by checking their group assignments on the Members page and the roles those groups are assigned to on the Roles page.
- **Organization settings:** In organization settings, the member only sees the sections their admin permissions cover. Everything else is hidden from their settings. Members with view access see pages as read-only, with controls disabled.
- **Analytics access:** Members with Analytics access will view analytics in **[Settings \> Analytics](https://claude.ai/analytics/activity)**, not organization settings.
**If you configured connector permissions, also check:**
- **Connector menu:** blocked connectors don’t appear, and connectors with at least one granted tool do.
- **Connector settings:** blocked tools are grayed out with “This tool is not enabled for your role. Contact your administrator.” Tools capped at “Needs approval” show a personal approval menu limited to “Ask” and “Never.”
- **In a conversation:** ask Claude to use a blocked tool, and it reports it has no tool for the task. Ask it to use a “Needs approval” tool, and the approval prompt appears without an “Always allow” option.
**If you configured model access, also check:**
- **Model picker:** disabled models don't appear, and the effort menu stops at the role's cap.
- **In a conversation:** ask the member to switch to a disabled model. It shouldn't be listed, and in Claude Code CLI, /model \<disabled-model\> returns an error.
Role changes may take up to 15 minutes to take effect across the platform. Members may need to refresh their browser to see updated access.
------------------------------------------------------------------------
## Use SCIM with role-based capabilities
SCIM connects to your role-based capabilities through two mechanisms that work together.
**Important:** Set these up in this order. Members in groups mapped to “Custom” have no permissions until their groups are assigned to custom roles.
1. Save SCIM directory sync with **Enable group mappings** off and let the initial sync finish.
2. In **[Organization settings \> Groups](https://claude.ai/admin-settings/groups)**, click “Check for updates” and sync Groups only.
3. Assign the synced groups to your custom roles, and to group spend limits if you use them.
4. Turn on **Enable group mappings** and map the groups to “Custom.”
### IdP group-to-role mapping
This controls which built-in role a member gets when they're provisioned. Map your IdP groups to "Custom" roles so that new members' access is automatically governed by custom role capabilities.
1. Navigate to **[Organization settings \> Organization and access](https://claude.ai/admin-settings/organization)**.
2. In the role mappings table, map your IdP groups to "Custom" roles.
### Group sync
This pulls your IdP groups into Claude so they can be assigned to custom roles.
1. Navigate to **[Organization settings \> Groups](https://claude.ai/admin-settings/groups)**
2. Click “Check for updates” in the **SCIM sync** section.
3. When prompted to sync Groups, Members, or Both, select Groups only. Syncing Members can affect provisioning and member access.
4. Your IdP groups appear as SCIM-sourced groups in the list.
5. Assign SCIM groups to custom roles just like manually created groups.
6. In your IdP, only push the groups you actually intend to use for RBAC or spend limits. Syncing all IdP groups can slow page loads in the Groups section.
**Note:** Custom role permissions only apply to members with "Custom" roles selected in **[Organization settings \> Members](https://claude.ai/admin-settings/members)**. If you map an IdP group to a different role (like User) through the group-to-role mapping but assign that same SCIM group to a custom role, the custom role's permissions have no effect—the member gets their permissions from their assigned role instead. To use custom roles, make sure the IdP group is mapped to "Custom."
### Ongoing management with SCIM
- To grant a member access to a feature, add them to the appropriate IdP group. On the next sync, they pick up the custom role assigned to that group.
- To revoke access, remove them from the IdP group. On the next sync, the permission is removed.
- Click “SCIM sync” in the Groups section to force an immediate sync rather than waiting for the next scheduled sync.
------------------------------------------------------------------------
## Rollback plan
If you notice your role structure is misconfigured after migration:
1. Turn off any organization-level features that were enabled as part of the migration.
2. Change affected members back to their previous built-in role (for example, User).
3. They immediately regain the static permissions from that role, and custom role permissions stop applying.
4. Adjust roles and groups as needed, then re-migrate.
If you enabled group mappings during setup and lost admin access, follow the recovery steps in **[Set up JIT or SCIM provisioning](https://support.claude.com/en/articles/13133195-set-up-jit-or-scim-provisioning#h_74979446b3)** under "I lost Admin/Owner access after enabling group mappings."
------------------------------------------------------------------------
## Frequently asked questions
### Do I need to enable a feature at the organization level if I only want some members to have it?
Yes. The organization-level toggle must be on for custom roles to control per-member access. If a feature is off at the organization level, no one can access it regardless of their role. Think of it as a main switch—custom roles control who gets access underneath it. This includes the Design, Slides, and Docs settings in **Organization settings \> Artifacts**.
### What happens if a member whose role is set to "Custom" isn't in any groups?
They have no custom role permissions, so all features that require permissions are greyed out or hidden. Make sure every member whose roles is set to "Custom" is in at least one group that's assigned to a custom role.
### A model is missing from a member's model picker.
Either the model is disabled at the organization level (**[Organization settings \> Models](https://claude.ai/admin-settings/models)**) or none of the member's custom roles grant it. Org-level disables affect everyone, including Owners and Admins.
### What if a custom role doesn't grant chat access?
Members in that role won't see Claude's chat interface. They'll land on their settings page when they sign in. If their role grants other products like Cowork or Claude Code, those remain accessible from their settings page and from the relevant apps.
Chat is enabled by default in all custom roles, so you only need to worry about this if you intentionally toggled chat off for a role.
### Can I use both built-in and custom roles?
Yes. Members with the User, Admin, or Owner roles are unaffected by custom role permissions because they get their permissions from those roles directly. Only members with a role set to "Custom" are controlled by the group-and-role system. This allows gradual migration.
### What if a member is in two groups with different roles?
Permissions are additive. If any role in a member's chain grants a feature, they have it. You can't use a role to remove a permission granted by another role.
### Can I use SCIM groups and manual groups together?
Yes. Both types can be assigned to custom roles. The difference is that SCIM group membership is managed in your identity provider, while manual group membership is managed in Claude's organization settings.
### Are Owners and Primary Owners affected by custom role permissions?
No. Owners and Primary Owners always have full access to all features.
### How does this work across parent and child organizations?
Groups and SCIM sync are managed at the parent organization level and shared across all child organizations. Role and spend limit assignments are configured independently in each child organization—changes in one child organization don't affect others. Group membership changes and SCIM resyncs propagate across all child organizations under the same parent.
### What happens to my existing custom roles when connector permissions are enabled?
Each existing role is seeded with the “All connectors” grant at “Always allow,” so members’ access doesn’t change at enablement. You narrow access from there.
### What’s the default connector permission on a new role?
“Needs approval” on every connector. The create-role flow steps through the Connectors tab so you see this before saving.
### What happens when I add a new connector after my roles exist?
A role whose “All connectors” row is set to “Always allow,” “Needs approval,” or “Blocked” covers the new connector at that level automatically. A role whose “All connectors” row is set to “Custom” treats the new connector as “Blocked” until you set it.
### I blocked a connector in a role, but a member with that role can still use it. Why?
Check whether the member holds another role that grants it, since the most permissive grant wins across roles. The conflict warning on the connector row lists those roles. Also confirm the member’s role is set to "Custom."
### My organization-wide tool policy already blocks a tool. Do I need to block it in every role?
No. The organization-wide policy is the ceiling. A tool blocked there is blocked for everyone, regardless of role grants.
### A member's role and the organization-wide policy are both set to "Always allow," but "Allow for all tasks" is grayed out in Cowork. Why?
Cowork has a separate organization setting, **Allow "Always allow" for connector tools**, that gates write-capable connector tools. It's off by default. Until it's turned on, "Allow for all tasks" stays grayed out regardless of role grants and tool policies, and previously saved always-allow preferences aren't honored. Read-only tools are exempt only when the connector annotates them as read-only, which most custom connectors don't. For more information, see **[Connector tool approvals](https://support.claude.com/en/articles/13455879-use-claude-cowork-on-team-and-enterprise-plans#h_1bd1fa754d).**
### Can a role grant a tool that the organization-wide policy sets to “Needs approval”?
The role can grant it, but the stricter setting wins, so members see it capped at “Needs approval.” To let members set “Always allow,” raise the organization-wide policy to “Always allow” first.
### Can I grant one tool on a connector without granting the whole connector?
Yes. Set the connector to “Custom,” set the one tool to “Always allow” or “Needs approval,” and leave the rest “Blocked.”
### Do connector permissions apply to built-in tools like web search or code execution?
No. Built-in features are governed on the Capabilities tab. The Connectors tab governs connectors your organization has added.
### How quickly do connector permission changes take effect?
Role changes may take up to 15 minutes to take effect. Members may need to refresh their browser.
### Can someone in a custom role with permissions give themselves more access?
Only if their role includes Identity & Access set to Manage, which covers editing roles and groups. Reserve that permission for trusted security and IT administrators, since it can be used to change role definitions including their own.
### Can I give admin permissions to a member on the User, Admin, Owner, or Primary Owner role?
No. Admin permissions only apply to members in a custom role. Members on a built-in role keep the access that role grants. To give someone specific admin permissions, change the member to a custom role and add them to a group assigned to a role with the permissions they need. Keep in mind this removes their previous built-in role access. To keep the full admin access of an Owner, use a role with **Owner access** turned on.
### Can an Owner get capabilities or model access from custom roles?
Not while their role is Owner, because Owners get their permissions from that role directly. Instead, change their role to "Custom" and add them to groups whose roles grant **Owner access** plus the capabilities and models they need. They keep an Owner's admin permissions, and their feature access follows their custom roles. Owner access doesn't cover the Primary Owner role.
### What does someone see when they don’t have permissions for a certain setting?
Organization settings only shows the sections their permissions cover. Sections they don’t have access to are hidden entirely from their organization settings.
### How do I audit who has admin access?
**[Organization settings \> Roles](https://claude.ai/admin-settings/roles)** shows the admin permissions each custom role grants, and **[Organization settings \> Groups](https://claude.ai/admin-settings/groups)** shows which groups are assigned to each role and who belongs to them. To check a specific member, look up their groups on **[Organization settings \> Members](https://claude.ai/admin-settings/members)**, then the roles those groups are assigned to.
### What if someone needs permissions across multiple areas?
Create one role that grants access to multiple areas, or add the member to multiple groups whose roles cover the areas they need. Permissions combine additively.
---
## Team plan billing FAQs | Claude Help Center
Source: https://support.claude.com/en/articles/12997503-team-plan-billing-faqs
Path: 17-Billing-Plans/team-plan-billing-faqs.md
# Team plan billing FAQs
## What payment methods can I use to pay for the Team plan?
Accepted payment methods are credit, debit, or prepaid cards. Other forms of payment, including ACH bank transfers, are not accepted at this time.
## How do I update my billing information and payment method?
An organization Owner can update your Team plan’s payment method by navigating to **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**.
**Note:** Your billing address determines your tax jurisdiction. See **[Understanding your billing address and tax calculation](understanding-your-billing-address-and-tax-calculation.md)** for details on how to view or update your billing address.
## How can I change my billing email address?
Your organization's billing address determines where your invoices are sent. You can request to change this email address, or add additional billing email addresses, by **[contacting our Support team](../15-Claude-AI-Features/how-to-get-support.md)**. Note that an organization Owner must authorize any changes to your billing address. For additional invoice recipients, the account Owner must be copied on the request. Once approved, all future invoices will be sent to the new email address(es).
## How can I use a different name on my invoices?
If you want to use a name other than the one tied to your payment method, an organization Owner should check the "Use a different name on invoices" box when adding or updating your payment method in **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**:
## When will I be billed?
Your payment method on file will be charged at the beginning of your billing cycle. The amount is based on the number of members on your team at the beginning of the billing cycle. If you add members or upgrade seats during the billing cycle, you'll be charged the prorated amount immediately. Removing members doesn't generate a credit or refund. The seat becomes available to assign to someone else.
See **[How is my Team plan bill calculated?](how-is-my-team-plan-bill-calculated.md)** for more information about Team plan pricing.
## Where can I see my monthly API credits?
In the Claude Console. All credits appear under **[Settings \> Billing](../04-API-Reference/Other/playground.md)** in your linked Console organization, with their amount and expiry date. Usage is never charged to your Claude plan. Learn more about **[monthly API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)**.
## Where can I find the invoice or receipt for my Team plan payment?
An organization owner can follow these steps to access invoices:
1. Navigate to **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**.
2. Find the **Invoices** section.
3. Click the "View" button next to the invoice you want to open.
4. A new Stripe tab will open.
5. Click "Download invoice."
All invoices are automatically emailed to your organization's billing email address(es), so recipients can also search using the subject line "Your receipt from Anthropic" to find previous invoice emails.
## My organization is tax-exempt; how can I remove the tax from our monthly invoices for our Team plan account?
It's not currently possible to create a tax-exempt Team plan account while signing up. However, after subscribing to the Team plan, you can send your tax-free verification document to our Support team for review. After our Billing team reviews the document, we can manually mark your billing account as exempt and issue a credit note to refund any tax charges.
Please click on the message icon in the bottom right of our Help Center to contact our Support team and share the relevant documentation.
## My Team plan access is no longer active and I want to resubscribe.
An organization owner can resubscribe for Team plan access by navigating to **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**.
## What happens to my Pro or Max subscription when I upgrade to Team?
When you upgrade from Pro or Max to Team in place, your individual subscription is cancelled automatically and you receive a prorated refund for the unused portion of your billing period. The refund is issued about 24 hours after your Team payment goes through, and depending on your bank, it can take several more business days to appear on your statement. Google Play purchases don't have this wait, but the refund can take a few days to appear. Any prepaid usage credits on your individual account are refunded
If you signed up for Pro or Max through the Apple App Store, in-place upgrades work differently. For more information, refer to **[Get started with the Team plan](get-started-with-the-team-plan.md#h_5d142d3f45)**.
If you'd rather keep your personal subscription active, check the opt-out box (**Keep your personal account separate**) in the team-creation flow when you upgrade.
---
## Understanding your billing address and tax calculation | Claude Help Center
Source: https://support.claude.com/en/articles/12997130-understanding-your-billing-address-and-tax-calculation
Path: 17-Billing-Plans/understanding-your-billing-address-and-tax-calculation.md
# Understanding your billing address and tax calculation
August 6, 2026
Your billing address determines how taxes are calculated on your Claude purchases. This address should represent the primary place of business receiving the product.
## How billing addresses work by plan type
### Pro, Max, self-serve Team, and self-serve Enterprise plans
Your billing address is automatically set to match your payment method's billing address. To update it, navigate to **[Settings \> Billing](https://claude.ai/settings/billing)** and click “Update” to the right of your current payment method.
### Sales-assisted Team plans and sales-assisted Enterprise plans
You can update your billing address directly in Settings → Billing → Billing Addresses. Changes take effect immediately for future invoices.
### API (usage tiers / self-serve)
Your billing address is tied to your payment method. Update your payment method by navigating to **[Settings \> Billing in the Claude Console](../04-API-Reference/Other/playground.md)** and clicking the pencil icon to the right of your current card number to change your billing address.
### Paid API contracts
You can update your billing address directly in the Claude Console under Settings → Billing → Billing Addresses.
## Requesting a different billing address
If your billing address doesn't match your payment method's address—for example, you're on a self-serve plan and need it to reflect a different business location for VAT purposes—you have two options:
- **Update your payment method's address.** Self-serve plans (Pro, Max, self-serve Team, self-serve Enterprise, and API usage tiers) take their billing address from the payment method, so updating the address on your card or Link wallet updates your billing address too.
- **Contact support to lock a fixed address.** If you need an address that stays the same even when you change payment methods, contact our Support team with documentation verifying your primary business location:
- **Non-US customers:** VAT registration certificate matching your requested location
- **US customers:** State of incorporation, business license, or tax ID documentation
Once verified, your billing address won't automatically update when you change payment methods.
---
## Understanding your Pro or Max plan invoices | Claude Help Center
Source: https://support.claude.com/en/articles/16607638-understanding-your-pro-or-max-plan-invoices
Path: 17-Billing-Plans/understanding-your-pro-or-max-plan-invoices.md
# Understanding your Pro or Max plan invoices
This article explains the invoices you'll receive for a Pro or Max plan, where to find them, and how to read the charges on them.
This article covers Pro and Max plans purchased on the web. If you subscribed through Claude for iOS or Claude for Android, Anthropic doesn't issue your invoices. The Apple App Store or Google Play bills you directly, and your receipts are available in your app store account.
## Types of invoices you may receive
**Subscription invoices.** You'll receive an invoice each time your plan renews: every month on a monthly plan, or once a year on an annual plan. Your subscription renews automatically until you cancel it.
**Plan change invoices.** If you upgrade your plan in the middle of a billing cycle, you'll reset your billing cycle and receive an immediate invoice for the change rather than waiting for your next renewal. For example, upgrading from Pro to Max charges you one full month of Max, less the unused value in your current billing cycle on your old plan.
Learn more about **[signing up for the Max plan](https://support.claude.com/en/articles/11049752)**.
**Usage credit receipts.** If you've enabled usage credits, each purchase of funds is charged separately from your subscription and has its own receipt. This includes purchases made automatically by auto-reload and any usage bundles you buy.
Learn more about **[managing usage credits for paid Claude plans](https://support.claude.com/en/articles/12429409)**.
## Find your invoices
After each charge, we automatically email the invoice to your billing email address. To find a past invoice in your inbox, search for the subject line "Your receipt from Anthropic."
You can also open any invoice from your account:
1. Go to **[Settings \> Billing](https://claude.ai/settings/billing)**.
2. Find the **Invoices** section.
3. Click "View" next to the invoice you want to open.
## Read your invoice
**Prorated charges.** When you upgrade in the middle of a billing cycle, you are charged for one full billing cycle of the new plan, less a prorated amount for value remaining in your old plan. Your next renewal invoice charges the full price.
**Credits.** For some mid-cycle plan changes, the cost of one cycle of the new plan is less than the remaining value of the current cycle of the old plan. In this case, any excess value from your old plan will be stored as a credit on your account, and will be used automatically to pay towards future invoices.
**Tax.** Tax is calculated from your billing address, which is taken from your payment method’s address. Learn more about **[your billing address and tax calculation](https://support.claude.com/en/articles/12997130)**.
**Applied balance.** An "Applied balance" line means a credit already on your account was used to pay part or all of the invoice. It's not a new charge and not a discount on that invoice.
**Amount due.** The invoice total minus any applied balance. This is what your payment method was charged.
## Billing details on your invoice
The name and address on an invoice come from your payment method at the time the invoice was issued. To show a different name, such as a company name, check "Use a different name on invoices" when you add or update your payment method in **[Settings \> Billing](https://claude.ai/settings/billing)**.
You can also add a tax or VAT ID. Learn more about **[adding a tax or VAT ID to your paid Claude account](https://support.claude.com/en/articles/9889408)**.
For help updating your payment method or other billing details, see **[Paid plan billing FAQs](https://support.claude.com/en/articles/8325618)**.
Changes to your billing details apply to future invoices only. Once an invoice has been issued, we can't edit or reissue it.
## Frequently asked questions
### Why doesn't my invoice match my plan price?
The most common reasons are a plan change in the middle of a billing cycle, which is charged at a prorated amount, or a credit or applied balance that reduced the amount due. Both are shown as their own lines on the invoice.
### Why did I get two receipts in the same month?
If you use usage credits, those purchases are billed separately from your subscription. One receipt is for your plan and the other is for the usage credits you added, whether you added them yourself or auto-reload did.
### Can you correct the details on an invoice I already received?
No. Issued invoices can't be changed. Update your billing details in **[Settings \> Billing](https://claude.ai/settings/billing)** and the changes will appear on your next invoice.
### Can I be invoiced in a different currency?
Some subscribers pay their subscriptions using a different currency than the currency (or currencies) new subscribers would be offered in their region. To change your subscription currency, you must first mark your plan to cancel at the end of the current term, and wait for the end of term. Then when you re-purchase a new Pro or Max plan, you will use the same currency (or currency options) as new subscribers would in your region.
### Where can I see my monthly API credits?
In the Claude Console. All credits appear under **[Settings \> Billing](../04-API-Reference/Other/playground.md)** in your linked Console organization, with their amount and expiry date. Usage is never charged to your Claude plan. Learn more about **[monthly API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)**.
---
## Understanding your Team plan invoices | Claude Help Center
Source: https://support.claude.com/en/articles/16607668-understanding-your-team-plan-invoices
Path: 17-Billing-Plans/understanding-your-team-plan-invoices.md
# Understanding your Team plan invoices
This article explains the invoices your organization receives for a Team plan, where to find them, and how to read the charges on them.
This article covers Team plans purchased directly on the web.
## Types of invoices your organization may receive
**Subscription invoices.** Your organization is invoiced at the start of each billing cycle, every month or once a year depending on your billing interval, for the seats on your plan at that time.
**Seat change invoices.** When an owner adds members or upgrades seats in the middle of a billing cycle, your organization is invoiced right away for the prorated cost of those seats for the rest of the cycle. Upgrading a seat from Standard to Premium works the same way and charges the prorated price difference. Removing members doesn't generate an invoice or a credit; the seat stays available to assign to someone else.
Learn more about **[how your Team plan bill is calculated](https://support.claude.com/en/articles/9267289)**.
**Usage credit receipts.** If your organization has enabled usage credits, each purchase of funds is charged separately from your subscription and has its own receipt. This includes purchases made automatically by auto-reload and any usage bundles an owner buys.
Learn more about **[managing usage credits for Team and seat-based Enterprise plans](https://support.claude.com/en/articles/12005970)**.
**Credit notes.** If we refund part of an invoice after it's been issued, for example the tax on an invoice after your organization is marked tax-exempt, you'll receive a credit note that references the original invoice.
## Find your invoices
After each charge, we automatically email the invoice to your organization's billing email address(es). To find a past invoice in that inbox, search for the subject line "Your receipt from Anthropic."
An organization owner can also open and download any invoice from your organization's account:
1. Go to **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**.
2. Find the **Invoices** section.
3. Click “View” next to the invoice you want to open. A new Stripe tab opens.
4. Click “Download invoice.”
To change the billing email address or add more recipients, contact our Support team. Learn more in **[Team plan billing FAQs](https://support.claude.com/en/articles/12997503)**.
## Read your invoice
**Seat charges.** A renewal invoice charges the full seat price for each seat on your plan at the start of the cycle. On a monthly plan, that's the monthly seat price times the number of seats. On an annual plan, it's the monthly seat price times 12, times the number of seats.
**Prorated charges.** A seat change invoice charges only for the part of the billing cycle that's left when the seats were added or upgraded, so the amount is less than the full seat price. For a worked example, see **[How is my Team plan bill calculated?](https://support.claude.com/en/articles/9267289)**
**Applied balance.** An "Applied balance" line means a credit already on your organization's account was used to pay part or all of the invoice. It's not a new charge and not a discount on that invoice. Credits come from a credit note or an overpayment on an earlier invoice, and they're applied to your next invoices automatically.
**Tax.** Tax is calculated from your organization's billing address. Learn more about **[your billing address and tax calculation](https://support.claude.com/en/articles/12997130)**. If your organization is tax-exempt, see **[Team plan billing FAQs](https://support.claude.com/en/articles/12997503)** for how to have tax removed.
**Amount due.** The invoice total minus any applied balance. This is what your organization's payment method was charged.
**Note:** The **Projected total** shown in **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)** doesn't include tax, so it will be lower than the total on your invoice.
## Billing details on your invoice
The name and address on an invoice come from your organization's payment method at the time the invoice was issued. To show a different name on invoices, an owner can check "Use a different name on invoices" when adding or updating the payment method in **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**.
Changes to your billing details apply to future invoices only. Once an invoice has been issued, we can't edit or reissue it.
## Frequently asked questions
### Why did we receive an invoice in the middle of our billing cycle?
An owner added members or upgraded seats. Those changes are invoiced immediately at a prorated amount rather than being added to your next renewal invoice.
### We removed members. Why didn't our invoice go down?
Removing a member frees up the seat but doesn't reduce your bill or generate a credit. You're charged for the seats on your plan at the start of each billing cycle, so to lower your next invoice, an owner needs to reduce your plan's total seat allocation before it renews.
Learn more about **[purchasing and managing seats on Team plans](https://support.claude.com/en/articles/12004354)**.
### Why did we get two receipts in the same month?
If your organization uses usage credits, those purchases are billed separately from your subscription. One receipt is for your seats and the other is for the usage credits that were added, whether an owner added them or auto-reload did.
### Can you correct the details on an invoice we already received?
No. Issued invoices can't be changed. An owner can update your billing details in **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**, and the changes will appear on your next invoice.
### Where can I see our team’s monthly API credits?
In the Claude Console. All credits appear under **[Settings \> Billing](../04-API-Reference/Other/playground.md)** in your linked Console organization, with their amount and expiry date. Usage is never charged to your Claude plan. Learn more about **[monthly API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)**.
---
## Usage limit best practices | Claude Help Center
Source: https://support.claude.com/en/articles/9797557-usage-limit-best-practices
Path: 17-Billing-Plans/usage-limit-best-practices.md
# Usage limit best practices
September 22, 2026
The number of messages you can send will vary based on your Claude plan. For more information on your plan’s usage, refer to the following resources.
- **[Free Claude](https://support.claude.com/en/articles/8114491-getting-started-with-claude#h_57262af5ae)**
- **[Pro plan](what-is-the-pro-plan.md#h_62ccc00135)**
- **[Max plan](what-is-the-max-plan.md#h_cfd2904008)**
- **[Team plan](what-is-the-team-plan.md#h_b59203dff2)**
- **[Enterprise plan](what-is-the-enterprise-plan.md#h_8294bce903)**
Additional factors that affect your usage limits include:
- Message length
- File attachment size
- Current conversation length
- Tool usage (e.g., Research, web search)
- Model choice
- Effort level
- Artifact creation and usage
- Multi-step tasks, like running code, creating files, or browsing websites
Our system also includes caching that helps you optimize your limits:
- Content in projects is cached and counts less against your limits when reused.
- Claude remembers context from earlier in the conversation.
------------------------------------------------------------------------
## 1. Start by planning your conversations
Before starting a conversation with Claude, consider the following:
- What specific information or assistance do you need?
- Can you combine multiple related questions into a single message?
- Is there any background information you can provide upfront?
Planning helps reduce the number of back-and-forth messages needed.
## 2. Be specific and concise
- Provide clear, detailed instructions or questions in each message.
- Avoid vague queries that may require clarification.
- Include relevant context to help Claude understand your needs better.
## 3. Use Claude's chat search and memory capabilities
- All users can follow these guidelines to take advantage of Claude's memory within a single chat:
- Refer back to previous information instead of repeating it.
- Use phrases like "As mentioned earlier" to build on earlier parts of the conversation.
- Users with paid plans (Pro, Max, Team, and Enterprise) can prompt Claude to search through previous conversations and reference relevant information in new chats. Giving Claude access to additional context prevents you from needing to provide the same information repeatedly.
- Learn more here: **[Searching past chats with Claude](https://support.claude.com/en/articles/11817273-using-claude-s-chat-search-and-memory-to-build-on-previous-context#h_89b670b004)**
- Users with paid plans (Pro, Max, Team, and Enterprise) can use Claude's memory and project summaries to build context across conversations.
- Learn more here: **[What is Claude's memory?](https://support.claude.com/en/articles/11817273-using-claude-s-chat-search-and-memory-to-build-on-previous-context#h_c1c0b33879)**
## 4. Batch similar requests in one message
If you have multiple related tasks or questions, group them in a single message. For example, instead of sending separate messages for each math problem, send them all in one message.
## 5. Review and edit your prompt before sending
Take a moment to review your message for clarity and completeness to reduce the need for follow-up messages.
## 6. Use project knowledge bases effectively
Projects offer significant caching benefits:
- When you upload documents to a project, they're cached for future use.
- When you reference that content again while it’s still cached, cached portions count less against your limits than new content.
- This means you can work with the same documents repeatedly without using up your messages as quickly.
- Example: If you're working on a research paper and add all your reference materials to a project, you can ask multiple questions about those materials while using fewer messages than if you uploaded them each time.
- Caches expire after a period of inactivity. If you come back to a project after a long break, your first message counts that content in full again.
- Projects offer a Retrieval Augmented Generation (RAG) mode allowing for expanded project knowledge capacity.
- Learn more here: **[Retrieval Augmented Generation (RAG) for projects](../15-Claude-AI-Features/retrieval-augmented-generation-rag-for-projects.md)**
## 7. Monitor your consumption in Usage settings
- If you're using a Pro, Max, Team, or seat-based Enterprise plan, you can navigate to **[Settings \> Usage](https://claude.ai/settings/usage)** to view progress bars showing how much of your five-hour session and weekly usage limits you’ve consumed.
- The **Plan usage limits** section at the top shows your progress towards both your session limit and weekly limits.
- **Current session:** How much of your plan’s five-hour session limit you’ve used thus far, plus the amount of time remaining in the session.
- **Weekly limits:** Check when your plan’s weekly usage limit resets, for all models, and for Fable (if included in your plan).
- **Usage credits:** If you are using a Pro, Max, Team, or seat-based Enterprise plan, your usage settings page will also show how much of your plan's limit you've used. Refer to these articles for more information about enabling usage credits depending on your plan:
- **[Manage usage credits for paid Claude plans](https://support.claude.com/en/articles/12429409-)**
- **[Manage usage credits for Team and seat-based Enterprise plans](https://support.claude.com/en/articles/12005970-)**
- If your organization is on a usage-based Enterprise plan, you won’t have specific usage limits, but will be charged based on consumption. You can also track this in **[Settings \> Usage](https://claude.ai/settings/usage)**.
## 8. Quick caching tips
- Use projects for anything you'll reference multiple times.
- Upload your core working documents to the project knowledge section when starting a project.
- The more you use the same content, the more benefit you get from caching.
------------------------------------------------------------------------
## Best practices for specific use cases
### For coding tasks
- Provide complete context about your coding environment in your initial message.
- Include entire relevant code snippets in one message for reviews or debugging.
### For writing assistance
- Outline requirements, target audience, and key points comprehensively.
- Send entire texts for editing in one message rather than breaking them up.
### For research and analysis
- Clearly define your research question and focus areas initially.
- Provide all relevant data in a single, well-structured message.
By following these best practices, you can make the most efficient use of your Claude plan's message allocation.
---
## Use Claude Code (local mode) and Claude Cowork (local mode) on a HIPAA-ready Enterprise plan | Claude Help Center
Source: https://support.claude.com/en/articles/17318731-use-claude-code-local-mode-and-claude-cowork-local-mode-on-a-hipaa-ready-enterprise-plan
Path: 17-Billing-Plans/use-claude-code-local-mode-and-claude-cowork-local-mode-on-a-hipaa-ready-enterprise-plan.md
# Use Claude Code (local mode) and Claude Cowork (local mode) on a HIPAA-ready Enterprise plan
The HIPAA configuration is an organization setting on Enterprise plans. It brings local Claude Code and Claude Cowork sessions under your Business Associate Agreement (BAA) with Anthropic. Cloud sessions, including Claude Code sessions in the cloud and Cowork in the cloud, aren't covered. This article calls them Claude Code (local mode) and Cowork (local mode). They run in one of these places:
- Claude Code in the terminal
- Claude Code in the Code section of Claude Desktop
- Cowork in Claude Desktop
With the configuration applied, members can use both products with protected health information (PHI), on the conditions in **[Check what your BAA covers](#h_eba343b314)**. Applying it also turns off certain features across your organization.
Available on Enterprise plans with an Anthropic account team. Only the Primary Owner can apply the HIPAA configuration.
This article is for the Primary Owner, who applies the configuration, and for any Owner who helps decide whether to apply it, prepare for it, and confirm it.
"HIPAA-ready" means the product is configured to support your HIPAA obligations under the BAA. Compliance remains your organization's responsibility.
**Note:**
- If your organization hasn't enabled HIPAA, start with **[HIPAA-ready Enterprise plans](hipaa-ready-enterprise-plans.md)**. Enabling HIPAA brings chat under your BAA. That step alone doesn't bring Claude Code (local mode) or Cowork (local mode) under your BAA.
- If you prepare members' computers, see **[Set up Claude Code (local mode) for a HIPAA-ready organization](../02-Claude-Code-CLI/hipaa-setup.md)** and **[Set up Cowork (local mode) for a HIPAA-ready organization](https://claude.com/docs/cowork/hipaa-setup)**.
- If you want to check whether a specific feature is covered under your BAA, see the list of Eligible Services in the **[Implementation Guide for HIPAA Entities](https://trust.anthropic.com/resources?s=l1wrssd9hsbi4gak0tp5a6&name=%5Banthropic%5D-hipaa-ready-offering-implementation-guide)** and **[Business Associate Agreements (BAA) for Commercial Customers](../13-Enterprise-Admin/business-associate-agreements-baa-for-commercial-customers.md)**.
## Check what your BAA covers
After you apply the HIPAA configuration, your BAA covers each product in the table, on the condition in the second column. Applying the configuration turns off Cowork and the Code section of Claude Desktop, even if they were on, so an Owner has to turn each one on afterward.
[TABLE]
You don't need zero data retention (ZDR) to apply the configuration. If your organization has ZDR for Claude Code, see **[Replace ZDR with the configuration](#h_a6b761685a)**.
### Products and features your BAA doesn't cover
Keep PHI out of these products and features. Your BAA doesn't cover them, even with the configuration applied:
- The Claude Code extensions for VS Code and JetBrains, which keep working after you apply the configuration
- Any feature labeled beta or research preview
- Claude Code sessions that connect through a cloud provider such as Amazon Bedrock, an LLM gateway, or a custom base URL
- Claude Code sessions that use a Claude Console API key, unless the Claude Console organization has ZDR enabled
- Connectors, MCP servers, plugins, desktop extensions, Claude in Chrome, and skills, including after an Owner turns them on
- Cloud and remote features such as Claude Code cloud sessions, which the configuration makes unavailable
Ask your IT team to **[deploy managed settings](../02-Claude-Code-CLI/hipaa-setup.md#deploy-managed-settings)**, a policy file on each computer that directs members to sign in with a Claude Enterprise account and refuses cloud providers and gateways. For a full list of Eligible Services, please review the **[Implementation Guide](https://trust.anthropic.com/resources?s=l1wrssd9hsbi4gak0tp5a6&name=%5Banthropic%5D-hipaa-ready-offering-implementation-guide)** and **[Business Associate Agreements (BAA) for Commercial Customers](../13-Enterprise-Admin/business-associate-agreements-baa-for-commercial-customers.md)**.
## Ask Anthropic to turn on the HIPAA configuration
You apply the configuration with the "Apply HIPAA configuration" button in **Organization settings \> Data and privacy**. The button is grayed out until Anthropic turns it on for your organization. Ask your Anthropic account team to turn it on. The HIPAA configuration is only available to organizations with an Anthropic account team at this time. Anthropic Support can’t turn it on for your organization.
See **[Coverage until you apply the configuration](#h_415ff36247)** and **[Business Associate Agreements (BAA) for Commercial Customers](../13-Enterprise-Admin/business-associate-agreements-baa-for-commercial-customers.md)** for what your BAA covers if you haven't applied it.
### Coverage until you apply the configuration
Until you apply the configuration, members can still use Claude Code (local mode) and Cowork (local mode) where an Owner has them turned on, but your BAA may not cover their use. Coverage differs for organizations with and without zero data retention (ZDR) for Claude Code:
- **Without ZDR for Claude Code:** Your BAA doesn't cover Claude Code or Cowork, so don't use them to process PHI.
- **With ZDR for Claude Code:** Your BAA covers Claude Code through ZDR. It doesn't cover Cowork, so don't use Cowork to process PHI.
Your account team can tell you whether your organization has ZDR for Claude Code.
### Replace ZDR with the configuration
The configuration is meant to replace ZDR for Claude Code (local mode). Applying it doesn't turn ZDR off. Don't apply the configuration if you wish to keep your existing access through ZDR.
If you have ZDR enabled for Claude Code within Claude for Enterprise, email your account team for help switching to the HIPAA configuration.
Once ZDR is removed, Anthropic keeps Claude Code data under standard retention, as it does for your organization's chat data.
## Prepare your organization
Complete these tasks before you apply the configuration.
### Review what changes for members
The table shows the changes members are most likely to notice, and what to do about each one before you apply the configuration. The **[Implementation Guide for HIPAA Entities](https://trust.anthropic.com/resources?s=l1wrssd9hsbi4gak0tp5a6&name=%5Banthropic%5D-hipaa-ready-offering-implementation-guide)** and **[Business Associate Agreements (BAA) for Commercial Customers](../13-Enterprise-Admin/business-associate-agreements-baa-for-commercial-customers.md)** list the Eligible Services under your BAA.
[TABLE]
Chat uses the same connectors, skills, and Claude in Chrome settings, so when these turn off, they turn off in chat too.
### Have your team review the terms
When you apply the configuration, you accept the BAA and confirm that you reviewed the **[Implementation Guide for HIPAA Entities](https://trust.anthropic.com/resources?s=l1wrssd9hsbi4gak0tp5a6&name=%5Banthropic%5D-hipaa-ready-offering-implementation-guide)**, which includes a list of Eligible Services under your BAA. Ask your legal and compliance teams to review both documents before you apply the configuration.
### Ask your IT team to prepare computers
Ask your IT team to follow **[Set up Claude Code (local mode) for a HIPAA-ready organization](../02-Claude-Code-CLI/hipaa-setup.md)**. If members use Cowork, ask the team to follow **[Set up Cowork (local mode) for a HIPAA-ready organization](https://claude.com/docs/cowork/hipaa-setup)** too. They update Claude Code and Claude Desktop to the latest versions, allow network access to Anthropic's servers, and deploy managed settings and the Claude Desktop policy.
The update matters because once the configuration is applied, Anthropic's servers reject requests from versions older than the minimum.
### Choose a time and tell members
Apply the configuration at a quiet time for your organization because Cowork, the Code section of Claude Desktop, and some connectors stay off until an Owner turns them on. Keep an Owner available afterward, and plan time to turn on each connector separately.
Tell members the date and time, which features turn off, and which ones you plan to turn back on.
## Apply the HIPAA configuration
To apply the configuration, you must be the Primary Owner and have a verified email address. Other Owners and Admins can't apply it, because applying it includes accepting the BAA for your organization.
The configuration applies to your existing Claude Enterprise organization, the same one your members use for chat, not to a separate account. It applies to Claude Code and Cowork together, and to every member.
**Warning:** When you apply the HIPAA configuration, certain features start turning off across your organization as soon as you confirm. An Owner can turn some features back on, but cloud features such as Claude Code cloud sessions stay unavailable.
To apply the configuration:
1. Sign in to Claude as the Primary Owner and go to **[Organization settings \> Data and privacy](https://claude.ai/admin-settings/data-privacy-controls)**.
2. In the "Compliance" section, find the row for Claude Code (local mode) and Cowork (local mode).
3. Select "Apply HIPAA configuration." A dialog opens.
4. In the dialog, review what changes, then download the Implementation Guide for HIPAA Entities, and the BAA if your organization has none on file. The "Apply HIPAA configuration" button in the dialog stays grayed out until you download them. Selecting it accepts Anthropic's updated BAA.
5. Select "Apply HIPAA configuration" to confirm. A message confirms that the configuration is applied.
If the button is grayed out, check that you're signed in as the Primary Owner and that your email address is verified. If it's still grayed out, **[ask Anthropic to turn it on](#h_a54ff1eb7a)**.
## Turn features back on
Cowork, the Code section of Claude Desktop, skills, and Claude in Chrome are off after you apply the configuration, and so is each connector whose terms no Owner had accepted. An Owner turns on the ones your organization approved. The **[Implementation Guide for HIPAA Entities](https://trust.anthropic.com/resources?s=l1wrssd9hsbi4gak0tp5a6&name=%5Banthropic%5D-hipaa-ready-offering-implementation-guide)** and **[Business Associate Agreements (BAA) for Commercial Customers](../13-Enterprise-Admin/business-associate-agreements-baa-for-commercial-customers.md)** list the Eligible Services under your BAA.
Turning a feature on doesn't change whether your BAA covers it.
Connectors take more steps, because you turn on each one separately. Go to **Organization settings \> Connectors**, open the connector, select "Enable" in the banner, select the checkbox to accept the terms, and click "Continue." Then set the connector's tool permissions again.
## Confirm the configuration is applied
Ask members to restart Claude Code and Claude Desktop, so that both get the configuration right away. Without a restart, a running Claude Code session gets it within about an hour. Claude Desktop might not get it until a member restarts or reloads the app.
Organization settings, Claude Code, and Claude Desktop each show the configuration once it's applied:
- **Organization settings:** Go to **[Organization settings \> Data and privacy](https://claude.ai/admin-settings/data-privacy-controls)**. Confirm that the row for Claude Code (local mode) and Cowork (local mode) says they're HIPAA configured for this organization, and shows the date you applied the configuration.
- **Claude Code:** Ask a member to run `/status` in a session. Confirm that the **Status** tab lists `HIPAA` on the `Organization configuration` line.
- **Claude Desktop:** Confirm that the title bar shows a **HIPAA configured** label. On a Mac, open the sidebar to see it.
Tell members not to process PHI until they see `HIPAA` in `/status`, or the **HIPAA configured** label, on their own computer.
If either one is missing on a member's computer, ask your IT team to follow **[Confirm the configuration on a computer](../02-Claude-Code-CLI/hipaa-setup.md#confirm-the-configuration-on-a-computer)**, which lists the likely causes in order. For the Claude Desktop label, see **[The HIPAA configured label is missing](https://claude.com/docs/cowork/hipaa-setup#the-hipaa-configured-label-is-missing)**. If it's still missing, contact your account team.
## Manage data on members' computers
Claude Code (local mode) and Cowork (local mode) store session data, such as transcripts, on each member's computer. Securing and deleting that data is your organization's responsibility.
Removing a member from your organization deletes nothing on their computer, so wipe the computer when a member leaves. Keep full-disk encryption turned on.
**[Manage local session data](../02-Claude-Code-CLI/hipaa-setup.md#manage-local-session-data)** lists where the data is stored, what Claude Code (local mode) and Claude Desktop delete automatically, and how to delete the rest. For Cowork data, see **[Manage Cowork data on each computer](https://claude.com/docs/cowork/hipaa-setup#manage-cowork-data-on-each-computer)**.
## Monitor sessions
These tools show what happens in Claude Code (local mode) and Cowork (local mode). They differ in whether they include session content:
- **Compliance API:** With the **[Compliance API](https://support.claude.com/en/articles/13015708)** turned on for your organization, Anthropic captures session activity and content from both products so that your organization can read it through the API. Sessions are readable for 30 days, or for your organization's retention period if it's shorter. While your organization has ZDR for Claude Code, Anthropic doesn't capture Claude Code sessions.
- **Audit logs and data exports:** Audit logs and data exports don't include session content. The audit log records administrative changes, such as enabling HIPAA and applying the configuration.
- **OpenTelemetry:** You can send events from both products to your own monitoring tools. The data you export is your organization's responsibility. Set the destination for Cowork in **Organization settings \> Data and privacy \> Monitoring**. Your IT team sets the destination for Claude Code in **[managed settings](../13-Enterprise-Admin/monitoring-usage.md#administrator-configuration)**.
**Important:** Cowork's OpenTelemetry events can include prompt text, Claude's responses, and tool inputs, so PHI in a session may reach your monitoring tools. Current versions of Claude Desktop only send metadata unless content capture is turned on, but some older versions send content such as prompt text and tool inputs by default. No organization setting turns that content off. Ask your IT team to set `otlpContentCapture` to `[]` so that every version that supports the policy sends metadata only, as described in **[Content capture](https://claude.com/docs/cowork/monitoring#content-capture)**. Metadata still includes the paths of connected folders, user email addresses, and API error messages, and an API error message can sometimes repeat part of the request. If these can contain PHI, filter or redact them at your collector.
## Get help
For questions about the BAA, the Implementation Guide for HIPAA Entities, or the configuration, contact your Anthropic account team. If your organization doesn’t have an account team, contact **[our Support team](../15-Claude-AI-Features/how-to-get-support.md)**. Do not include PHI in a support request.
---
## Use Claude Code with your Team or Enterprise plan | Claude Help Center
Source: https://support.claude.com/en/articles/11845131
Path: 17-Billing-Plans/use-claude-code-with-your-team-or-enterprise-plan-claude-help-center.md
# Use Claude Code with your Team or Enterprise plan
This article applies to members of Team or Enterprise plan organizations using their subscription plans to access Claude Code. If you’re an individual consumer using a Pro or Max plan subscription, see **[Use Claude Code with your Pro or Max plan](https://support.claude.com/en/articles/11145838-use-claude-code-with-your-pro-or-max-plan)**.
## What is Claude Code?
Claude Code is a coding tool that gives you access to Claude models directly in your terminal or supported IDE, allowing you to delegate complex coding tasks while maintaining transparency and control.
Claude Code is included with every Team plan seat. Premium seats offer more usage for team members with heavier workloads. For Enterprise plans, Claude Code is included with the single Enterprise seat on new and self-serve plans. On older Enterprise plans, Claude Code is available on Chat + Claude Code seats (usage-based billing) and Premium seats (seat-based billing).
With a Team or Enterprise plan, you can access Claude on the web, desktop, and mobile apps, plus Claude Code in your terminal—all with one unified subscription.
### Why use Claude and Claude Code?
Combine two powerful AI products in one unified subscription:
- Use Claude for writing, research, analysis, and collaboration across teams.
- Use Claude Code for terminal-based coding workflows and development tasks.
------------------------------------------------------------------------
## Connect Claude Code to your Team or Enterprise plan
### Step 1: Confirm Claude Code access (Enterprise plans only)
If your organization is on a new or self-serve Enterprise plan, Claude Code is already included with every Enterprise seat—no additional purchase is needed. Proceed to Step 2.
**Note:** On a HIPAA-ready Enterprise plan, after the Primary Owner applies the HIPAA configuration to Claude Code (local mode) and Cowork (local mode), your Business Associate Agreement (BAA) covers Claude Code in the terminal and in the Code tab of Claude Desktop. Without that configuration or zero data retention (ZDR) for Claude Code, Claude Code is included in your seat, and it's available but not covered under your BAA. Don't use it with protected health information (PHI). See **[Use Claude Code (local mode) and Cowork (local mode) on a HIPAA-ready Enterprise plan](https://support.claude.com/en/articles/17318731)**.
If your organization is on an older Enterprise plan with Chat and Chat + Claude Code seats, or Standard and Premium seats, you'll need to ensure you have a seat type that includes Claude Code. Owners can purchase or reassign **Chat + Claude Code / Premium seats** in **[Organization settings \> Organization](https://claude.ai/admin-settings/organization)**. See **[Purchase and manage seats on Enterprise plans](https://support.claude.com/en/articles/13393991-purchase-and-manage-seats-on-enterprise-plans)** for details.
### Step 2: Download and install Claude Code
**Note:** If you already have Claude Code installed on your computer, proceed to Step 3.
Once you confirm you have access, follow the installation instructions in our **[Claude Code Docs](../01-Getting-Started/quickstart.md#step-1-install-claude-code)** for the environment you're using.
### Step 3: Authenticate with the Team or Enterprise account
1. Type `claude` within your Terminal window to start a Claude Code session.
2. When prompted during setup or first use, select a login method.
1. If you're already logged in to Claude Code via a different account, run /login to select a different login method.
3. Select “Claude account with subscription” to be routed to an OAuth prompt.
4. Select your Team or Enterprise plan and click “Authorize.”
5. Your premium seat subscription will be linked to Claude Code.
Once you're signed in, skills and plugins from your Claude account, including those your organization provides, load in Claude Code automatically. This needs Claude Code v2.1.273 or later. Learn more about **[how synced skills behave](../08-Plugins-Skills/skills.md#how-synced-skills-behave)** in the Claude Code docs.
### Having trouble using your Team or Enterprise account to access Claude Code?
If you're not seeing the option to authenticate with your preferred account, follow these steps to update Claude Code:
1. Log out of your active session completely using the `/logout` command.
2. Run `claude update`.
3. Restart your terminal completely for the change to take effect.
4. Run `claude` and select the correct account to use Claude Code.
## Use Claude Code in your IDE
Your seat also covers Claude Code in supported IDEs, including VS Code, Cursor and other VS Code forks, and JetBrains IDEs like IntelliJ and PyCharm. Log in with the same Team or Enterprise account you use in the terminal. IDE usage is limited and billed the same way as terminal usage on your plan.
To install and set up the extension for your IDE, see **[Platforms and integrations](../02-Claude-Code-CLI/platforms.md)** in our Claude Code Docs.
**Note:** On a HIPAA-ready Enterprise plan, the Claude Code extensions for VS Code and JetBrains are available but not covered under your BAA, including with the HIPAA configuration applied to Claude Code (local mode) and Cowork (local mode). Don't use them to process protected health information (PHI).
------------------------------------------------------------------------
## What happens when you hit usage limits
If your organization is on a **usage-based Enterprise plan** (including self-serve Enterprise), there are no per-seat usage limits—usage is based on consumption and billed at API rates. See **[How am I billed for my Enterprise plan?](how-am-i-billed-for-my-enterprise-plan.md)** for details on how usage billing works.
If your organization is on a Team plan or a seat-based Enterprise plan, you can enable usage credits to allow team members to continue working with Claude, Cowork, and Claude Code after reaching their included usage limits. For more information, see **[Manage usage credits for Team and seat-based Enterprise plans](https://support.claude.com/en/articles/12005970-)**.
Monthly API credits included with Team plans can’t be used in Claude Code or the Claude apps, including for extra usage. Learn more about **[monthly API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)**.
---
## Use the Claude Agent SDK with your Claude plan | Claude Help Center
Source: https://support.claude.com/en/articles/15036540-use-the-claude-agent-sdk-with-your-claude-plan
Path: 17-Billing-Plans/use-the-claude-agent-sdk-with-your-claude-plan.md
# Use the Claude Agent SDK with your Claude plan
**Update October 7, 2026:** Claude Max and Team plans now include **[monthly API credits](https://support.claude.com/en/articles/17154008)**, which cover the Claude Agent SDK, `claude -p`, the Claude API, and Claude Managed Agents. You can still use the Claude Agent SDK, `claude -p`, and third-party apps with your subscription limits.
**Update June 15, 2026:** We’ve paused the previously-announced changes to Claude Agent SDK usage. For now, nothing has changed: Claude Agent SDK, `claude -p`, and third-party app usage still draw from your subscription limits.
---
## Use visual and interactive content on Team and Enterprise plans | Claude Help Center
Source: https://support.claude.com/en/articles/13663666-use-visual-and-interactive-content-on-team-and-enterprise-plans
Path: 17-Billing-Plans/use-visual-and-interactive-content-on-team-and-enterprise-plans.md
# Use visual and interactive content on Team and Enterprise plans
March 16, 2026
Maps and image search results are enabled by default on Team plans. On Enterprise plans, these features are off by default — an Owner or Primary Owner can enable them in **[Organization settings \> Capabilities](https://claude.ai/admin-settings/capabilities)**.
When these features are active, some data is shared with third-party services. For more information, see **[Visual and interactive content](../15-Claude-AI-Features/visual-responses-and-interactive-widgets.md)**.
## How is your information processed by Google?
Maps and weather content is powered by Google Maps. Users’ prompts aren't sent to Google — instead, Claude transforms queries into generic search requests. Google also receives users’ IP addresses and, if they’ve consented, their location data to return relevant results. Data sent to Google is subject to **[Google's privacy policy](https://policies.google.com/privacy)**.
## How is your information processed by Bing?
Image results are powered by Bing Image Search. Users’ prompts aren’t sent to Bing — instead, Claude transforms queries into generic search requests. If users click a URL associated with an image, anonymized click data is also sent to Bing. Data sent to Bing is subject to **[Microsoft's privacy policy](https://privacy.microsoft.com/en-us/privacystatement)**.
Interactive inputs don't involve third-party services.
---
## Use Claude Code with your Pro or Max plan | Claude Help Center
Source: https://support.claude.com/en/articles/11145838-using-claude-code-with-your-pro-or-max-plan
Path: 17-Billing-Plans/using-claude-code-with-your-pro-or-max-plan.md
# Use Claude Code with your Pro or Max plan
This article applies to individual consumers using Pro or Max plan subscriptions to access Claude Code. If you’re a member of a Team or Enterprise plan organization, see **[Use Claude Code with your Team or Enterprise plan](use-claude-code-with-your-team-or-enterprise-plan-claude-help-center.md)**.
## What is Claude Code?
Claude Code is a coding tool that gives you access to Claude models directly in your terminal or supported IDE, allowing you to delegate complex coding tasks while maintaining transparency and control. With Pro and Max plans, you now have access to both Claude on the web, desktop, and mobile apps and Claude Code in your terminal with one unified subscription.
### Why use Claude and Claude Code?
Use two powerful AI products in one simple subscription.
- Use Claude for writing, research, analysis, and more—at work and at home.
- Use Claude Code for your terminal-based coding workflows.
------------------------------------------------------------------------
## How to connect Claude Code to your Pro or Max plan
1. **Ensure you have an active Pro or Max plan subscription**
- If you're not already subscribed, upgrade at **[claude.ai/upgrade](https://claude.ai/upgrade)**
2. **Install Claude Code**
- Visit the **[Claude Code page in our Claude Docs](../01-Getting-Started/quickstart.md#step-1-install-claude-code)** to download and install Claude Code.
- Follow the installation instructions for your operating system.
3. **Authenticate with your Claude credentials**
- When prompted during setup or first use, log in with the same credentials you use for Claude.
- This will connect your Pro or Max plan subscription to Claude Code.
- If you're already logged in to Claude Code via Claude Console PAYG, run /login from within Claude Code to switch to your subscription plan.
### Having trouble using your Pro or Max plan to access Claude Code?
If you're not seeing the option to authenticate with your preferred account, follow these steps to update Claude Code:
1. Log out of your active session completely using the `/logout` command.
2. Run `claude update`.
3. Restart your terminal completely for the change to take effect.
4. Run `claude` and select the correct account to use Claude Code.
**Important:** If you have an ANTHROPIC_API_KEY environment variable set on your system, Claude Code will use this API key for authentication instead of your Claude subscription (Pro, Max, Team, or Enterprise plans), resulting in API usage charges rather than using your subscription's included usage. See this article for more information: **[Managing API key environment variables in Claude Code](../02-Claude-Code-CLI/managing-api-key-environment-variables-in-claude-code.md).**
## Use Claude Code in your IDE
Your Pro or Max plan also covers Claude Code in supported IDEs, including VS Code, Cursor and other VS Code forks, and JetBrains IDEs like IntelliJ and PyCharm. Log in with the same Claude credentials you use in the terminal. IDE usage counts toward the same usage limits shared across Claude and Claude Code.
To install and set up the extension for your IDE, see **[Platforms and integrations](../02-Claude-Code-CLI/platforms.md)** in our Claude Code Docs.
------------------------------------------------------------------------
## What happens when you hit usage limits
Both Pro and Max plans have a five-hour session limit and a weekly limit. Max plans also have a separate weekly limit for Fable. These limits are shared across Claude and Claude Code, meaning all activity in both tools counts against the same limits. To help you monitor your usage, you’ll see warning messages as you approach any limit.
If you reach your five-hour session limit while Claude Code is partway through a response, Claude Code may keep working briefly so it can finish the step in progress instead of stopping mid-step. While this happens, you’ll see “Usage limit reached · wrapping up” in Claude Code. This wrap-up allowance is small and capped, and the usage counts toward your weekly limit. It applies only to a response that’s already in progress, not to a new message you send after reaching your limit. On the Pro plan, it applies up to once per weekly usage period. On the Max plan, it can apply each time you reach a five-hour session limit, within your weekly limit. It’s rolling out gradually, so it may not be available on your account yet. Learn more about the **[Claude Code wrap-up allowance](../02-Claude-Code-CLI/claude-code-wrap-up-allowance-claude-help-center.md)**.
When you reach your usage limits, you can select from a few options based on your needs:
### Pro plan users
- Consider upgrading to the Max 5x plan if you consistently hit limits and need more capacity for larger repositories.
- **[Enable usage credits](https://support.claude.com/en/articles/12429409-)** to keep using Claude with your Pro plan after you reach your five-hour session limit or your weekly limit.
- Switch to a Claude Console account and **[purchase API usage credits](../22-Safety-Policy/how-do-i-pay-for-my-claude-api-usage.md)** for intensive coding sprints.
- Wait until your usage limits reset.
### Max plan users
- If you're on the Max 5x plan, consider upgrading to the Max 20x plan if you consistently hit limits.
- **[Enable usage credits](https://support.claude.com/en/articles/12429409-)** to keep using Claude with your Max plan after you reach your five-hour session limit, your general weekly limit, or your separate weekly limit for Fable.
- Switch to a Claude Console account and **[purchase API usage credits](../22-Safety-Policy/how-do-i-pay-for-my-claude-api-usage.md)** for intensive coding sprints.
- Monthly API credits included with Max plans can’t be used in Claude Code or the Claude apps, including for extra usage. Learn more about **[monthly API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)**.
- Wait until your usage limits reset.
For more details on efficient usage, refer to our **[Usage limit best practices](usage-limit-best-practices.md)**.
------------------------------------------------------------------------
## Claude Code billing
### Understanding two distinct systems
It's important to recognize these are separate systems:
- **Claude Code:** Presents options for continuing usage through API credits.
- **Claude Console / Claude API:** Contains optional auto-reload settings for API credit management where your terminal is located.
### Choosing to use API credits
If you want to use API credits through Claude Code:
- Usage will be billed at **[standard API rates](pricing.md#api)** (distinct from Pro/Max Plan pricing).
- If auto-reload is enabled in your Console account, additional credits will be automatically added when your balance runs low.
### Staying within your plan
To maintain usage strictly within your Pro or Max Plan allocation:
- Decline the API credit option when presented.
- Allow your usage period to reset before continuing to use Claude Code.
- Monitor your remaining allocation using the /status command.
### Opting out of API credits for Claude Code
If you prefer to prevent the API credit option from appearing entirely:
- Run `claude logout` in your terminal.
- Run `claude login` and authenticate using only your Pro or Max plan credentials.
- Avoid adding any Claude Console credentials during the login process.
This ensures Claude Code will only use your plan allocation and you won't be prompted to use API credits when you reach your limits.
### Managing auto-reload settings
Auto-reload functionality is managed within your Claude Console account, not through Claude Code:
- Review your **[Console Billing settings](../04-API-Reference/Other/playground.md)** to check auto-reload status.
- Adjust these settings in the Console if you prefer to avoid automatic credit purchases.
- Remember, auto-reload only applies when you've chosen to use API credits.
### Summary
- Claude Code maintains strict user control over billing decisions.
- Auto-reload is an independent Claude Console feature.
- To maintain your Pro or Max plan budget, simply decline API credit options when offered.
---
## View usage analytics for Team and Enterprise plans | Claude Help Center
Source: https://support.claude.com/en/articles/12883420-view-usage-analytics-for-team-and-enterprise-plans
Path: 17-Billing-Plans/view-usage-analytics-for-team-and-enterprise-plans.md
# View usage analytics for Team and Enterprise plans
This article explains how to view and export usage analytics for your organization.
Usage analytics are available to Team plan Owners and Primary Owners, and Enterprise plan Owners, Primary Owners, and Admins. Enterprise Admins can view all analytics except Spend.
Usage analytics help you track team activity, feature adoption, and spend directly from your admin dashboard. You can monitor how your organization uses Claude and export detailed reports for your own analysis.
Primary Owners and Owners can access analytics via dedicated Analytics settings by clicking your initials in the lower left corner and selecting **[Analytics](https://claude.ai/analytics/overview)** from the menu. Additionally, the Chat, Claude Code, Claude Design, and Cowork options offer product-specific analytics, and the Surveys option lets you ask users directly about their experience.
------------------------------------------------------------------------
## Overview
This page includes the following analytics:
### Summary
- Weekly active members
- PRs created in Code
- Sessions in Cowork
### Who’s using Claude?
- Active members and assigned seats
- Groups
- Members
Use the dropdown on the **Active members and assigned seats** chart to filter by product, including Claude Design.
### How are they using Claude?
- Adoption level
- Product stickiness
- Skills (including cost per use and number of uses)
- Connectors (including the number of users, plus counts of read and write actions)
- How agentic is their work? (beta)
### What are the results?
- PRs created
- Designs created
- File operations
- Conversations
- MCP writes
- Estimated time saved
### How much is Claude costing?
**Note:** If you're on a **[seat-based Enterprise plan](https://support.claude.com/en/articles/13393991-purchase-and-manage-seats-on-enterprise-plans#h_6a78e30e26)**, spend reports only appear if your organization has **[enabled usage credits](https://support.claude.com/en/articles/12005970-)**. The spend data covers overage spend only—usage within seat-based allotments isn't included.
This section includes the following analytics:
- Usage limits
- Spend concentration
- Total spend (month-to-date, quarter-to-date, year-to-date, 1 year)—the graph shows your actual spend and list price
- Spend by model (month-to-date, quarter-to-date, year-to-date, 1 year)
**Note:** For a view of how spend limits are affecting your organization, you can also check the **Blocked by a spend limit** section at the top of **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**. **Blocked by a spend limit** is built for usage-based Enterprise plans. Orgs without usage-based seats only see how many members are blocked or near their limit right now. Learn more about **[monitoring usage and spend on Enterprise plans](how-am-i-billed-for-my-enterprise-plan.md#h_ae17ec8236)**.
## Export a spend report
You can export a detailed spend report as a CSV file. The report provides per-user, per-model visibility into token usage and estimated spend within a selected time period, updated daily.
To export spend data:
1. Navigate to **[Settings \> Analytics](https://claude.ai/analytics/activity)**.
2. Scroll down to the **How much is Claude costing?** section.
3. Click the "Export spend report" button.
4. Select a time period: MTD, Last Month, Last 90 Days, or Custom.
5. If you select "Custom," choose your start and end dates. You can go back up to 90 days, and the most recent data available is from yesterday.
6. Click "Download."
### What's included in the report?
Each row in the CSV represents a specific person's usage of a specific model, with spend summed across the entire date range selected for the export. The report includes the following fields:
- User's email
- Account UUID
- Product (such as Chat, Claude Code, Cowork, or Office Agents)
- Office Agents aggregates usage from the Claude add-ins for Excel, PowerPoint, and Word.
- Model and model family
- Request count (`total_requests`)
- The count of individual API calls made to Claude. Each time an app or user sends a message and gets a response, that counts as a request.
- Prompt tokens (`total_prompt_tokens`)
- The number of tokens consumed by the input side of each request. This includes system prompts, conversation history, user messages, tool definitions, etc.
- Completion tokens (`total_completion_tokens`)
- The number of tokens generated by Claude when it responds*,* including extended thinking tokens.
- Net spend (`total_net_spend_usd`)
- Your cost (in USD) after any discounts, credits, or negotiated rates are applied. This is what you actually spent.
- Gross spend (`total_gross_spend_usd`)
- Your cost (in USD) before any discounts or credits.
Analytics chat, the Analytics API, and exported spend reports from the analytics dashboard should closely match your invoice. The cost and usage endpoints of the Analytics API export include both discounted price and list price.
**Note:** Some activity previously grouped under Claude Code, including Code Review and security features, now appears as separate line items.
**Important:** Spend data refreshes daily and has a one-day delay. For usage-based Enterprise plans, the export captures your organization's full usage. For seat-based Enterprise plans with usage credits enabled, **the export only reflects spend that exceeds your seat allotment.**
------------------------------------------------------------------------
## Claude Chat
Navigate to **[Analytics \> Claude Chat](https://claude.ai/analytics/usage)** to view usage and activity metrics for your organization. This page includes the following analytics:
### Chats
- Chats per day
- Percentage of users with 1 or more chat
- Total number of chats (1 week, 1 month, 3 months, 1 year)
- Top members by chats
### Projects
- Projects created per day
- Percentage of users with 1 or more project
- Projects listed with the number of users, conversations, and messages associated with each one.
- Top members by project usage
### Artifacts
- Artifacts created per day
- Percentage of users with 1 or more artifact
- Top 10 users by artifacts generated (month-to-date, quarter-to-date, year-to-date, 1 year)
------------------------------------------------------------------------
## Claude Code
Navigate to **[Analytics \> Claude Code](https://claude.ai/analytics/claude-code)** to view usage and value metrics for Claude Code across your organization. The page has three tabs.
### Productivity
- PRs with Claude Code
- LOC with Claude Code
- Adoption
- Total PRs per user
- Pull requests / lines of code
- Suggestion accept rate
- Lines of code accepted
- Leaderboard (Pull requests / lines of code) with an option to export users
### Usage
- Users with skills
- Known MCP servers
- Top skills
- Top MCP servers
- Tool usage
- Feature adoption
- Sessions by agent type
Usage data refreshes daily.
### Value
- Estimated productivity lift
- Time recovered (annual)
- Cost per commit
- Cost per PR
- Cost per session
- Top spenders
- Spend concentration
- Automation leverage
- Observed metrics
- Calibrations
Every formula on the Value tab is shown inline, and you can adjust the inputs to match your organization's assumptions.
For contribution metrics, GitHub setup, and per-developer detail, refer to [**Claude Code usage analytics**](../22-Safety-Policy/claude-code-usage-analytics.md).
------------------------------------------------------------------------
## Claude Design
Navigate to **[Analytics \> Claude Design](https://claude.ai/analytics/claude-design)** to view usage and activity metrics for Claude Design across your organization. This page includes:
- Daily, weekly, and monthly active users
- An active users chart showing daily and weekly trends (1 week, 1 month, 3 months, 1 year)
Data is shown in UTC and refreshes daily.
**Note:** Claude Design must be enabled for your organization. On Enterprise plans with the Analytics API enabled, Claude Design analytics are also available in the **[Analytics API](../04-API-Reference/Other/manage-claude-analytics-api.md#get-access-to-the-claude-enterprise-analytics-api)**.
------------------------------------------------------------------------
## Cowork
Navigate to **[Analytics \> Cowork](https://claude.ai/analytics/cowork)** to view usage and activity metrics for Claude Cowork across your organization. This page includes:
- Cowork sessions per day
- Percentage of users with one or more Cowork sessions
- Daily, weekly, and monthly active Cowork users
**Note:** Cowork analytics are available alongside Chat and Claude Code data in the **[Analytics API](../04-API-Reference/Other/manage-claude-analytics-api.md)**.
------------------------------------------------------------------------
## Surveys
Navigate to **[Analytics \> Surveys](https://claude.ai/analytics/surveys)** to ask users short, in-product questions about what they're getting out of Claude and review the aggregated answers. Surveys appear to users as a small card in Cowork or chat, and results include response rates, a breakdown by surface and group, and a CSV export per survey. Learn more about **[creating surveys for your organization](https://support.claude.com/en/articles/16764057)**.
------------------------------------------------------------------------
## View your own usage as a member
On Enterprise plans with usage-based billing, when your admin turns on individual usage analytics, any member of the organization can see their own usage broken down by product, model, and skill, along with where they stand against any spend limits set for them. Individual usage analytics are available in **[Settings \> Usage](https://claude.ai/settings/usage)**.
------------------------------------------------------------------------
## Turn individual usage analytics on or off
**Note:** Individual usage analytics is available to Enterprise organizations on usage-based billing. The **Member analytics** toggle does not appear for Team plan organizations or for seat-based Enterprise organizations.
Owners and Primary Owners control whether members can see this view. The setting applies to the whole organization.
1. Navigate to **[Organization settings \> Usage](https://claude.ai/admin-settings/usage)**.
2. Find the **Member analytics** toggle.
3. Switch it on or off.
**Note:** Individual usage analytics is default on since July 11, 2026. If you want to keep member-level visibility off, change the setting.
------------------------------------------------------------------------
## Access your analytics data programmatically
If you’re on an Enterprise plan and want to pull analytics data into your own dashboards or reporting tools, the Analytics API gives you programmatic access to the same usage and engagement metrics available in the analytics dashboard. To get started, refer to our **[Analytics API docs](../04-API-Reference/Other/manage-claude-analytics-api.md)**.
**Important**: Only your organization's Primary Owner can enable the Analytics API and create Analytics API keys, from **[Organization settings \> API](https://claude.ai/admin-settings/api-access)**: under **APIs**, turn on Analytics API; under **Keys**, click "+Create key" and select the `read:analytics` scope. Owners and Admins don't see the Analytics API on that page at all. That's expected, not a permissions error—ask your Primary Owner to enable it and create the key. If your organization is linked to a parent organization, the parent organization's Primary Owner does this.
---
## What is the Enterprise plan? | Claude Help Center
Source: https://support.claude.com/en/articles/9797531-what-is-the-enterprise-plan
Path: 17-Billing-Plans/what-is-the-enterprise-plan.md
# What is the Enterprise plan?
September 1, 2026
The **[Enterprise plan](pricing-enterprise.md)** is designed for organizations that need advanced security, compliance controls, and scalable AI across their teams. It includes everything in the **[Team plan](what-is-the-team-plan.md)**, plus additional security and compliance features. Enterprise plan pricing works differently than Team plans: the seat fee covers access only, and all usage is billed separately at API rates.
For more information on Enterprise plan pricing, refer to **[our pricing page](pricing-enterprise.md)**.
Enterprise plans are available two ways:
- **[Self-serve](https://claude.ai/create/enterprise?utm_source=support&utm_medium=article&utm_content=enterprise-plan_self-serve_intro)** — purchase directly online without sales involvement.
- **[Sales-assisted](https://claude.com/contact-sales?utm_source=support&utm_medium=article&utm_content=enterprise-plan_contact-sales_intro)** — work with our Sales team for advanced options and dedicated support.
**Important:** If your organization currently uses **Chat** and **Chat + Claude Code** seats, or **Standard** and **Premium** seats, refer to the sections at the end of this article for information specific to your plan.
------------------------------------------------------------------------
## What's included in the Enterprise plan?
Enterprise includes everything in the Team plan, plus the following:
- **Security features** to ensure the safety and compliance of your organization's data including:
- **Audit logs:** capture key information about user actions, system events, and data access.
- **System for Cross-domain Identity Management (SCIM)**
- **Custom data retention controls**
- **Compliance API:** programmatically access Claude usage data including activity logs, chat histories, and file content, with filtering capabilities by user and time range.
- **Analytics API:** Programmatically access aggregated engagement and adoption metrics for your organization.
- **Customer-managed encryption keys:** Provision an encryption key in your own cloud provider that your organization controls, and have Anthropic use it to protect your team's chats, projects, and files in Claude.
- **US-only inference:** Keep your organization's inference within the United States.
- **Usage-based pricing**
- The seat fee only covers access to the platform and doesn't include any usage. All usage across Claude, Claude Code, and Cowork is billed separately at standard API rates, based on what your team actually consumes. There are no per-seat usage limits and no included token allowance.
- Admins can set spend limits at the organization and individual user levels to manage costs.
- **Connectors for workplace tools**
- Connect Claude to Google Drive, Gmail, Google Calendar, GitHub, Microsoft 365, and Slack to search and retrieve context from your existing documents, emails, calendars, and team communications without manual uploads.
- **HIPAA-readiness**
- Eligible organizations can enable a HIPAA-ready configuration and accept a BAA from organization settings. Learn more about **[HIPAA-ready Enterprise plans](hipaa-ready-enterprise-plans.md).**
------------------------------------------------------------------------
## Pricing
Enterprise uses a single seat type, priced per user per month and billed annually. The seat fee gives each user access to Claude on web, desktop, and mobile, plus Claude Code and Cowork.
**Usage isn't included in the seat fee.** Every token your team uses—in Chat, Claude Code, or Cowork—is billed at standard API rates on top of your seat cost. For full details on how usage billing works for your plan, see **[How am I billed for my Enterprise plan?](how-am-i-billed-for-my-enterprise-plan.md)**
Price and plans are subject to change at Anthropic's discretion.
------------------------------------------------------------------------
## Do Enterprise plans have any usage limits?
Usage-based Enterprise plans—including the single Enterprise seat described above—have **no plan or seat-level usage limits**. Usage is billed based on actual consumption rather than capped at a fixed amount.
If your organization is on a seat-based plan with Standard and Premium seats, usage limits do apply. See the **[Standard and Premium seats section](#h_f8351870fb)** below for details, including how to enable usage credits on those plans.
### How does usage apply across the team?
On usage-based Enterprise plans, there's no token allowance to divide up. Instead, every team member's usage is metered and billed to the organization at API rates. One person's heavy usage doesn't reduce what's available to anyone else, because nothing is allocated in the first place. If you need cost predictability, admins can set spend limits at the organization or user level.
------------------------------------------------------------------------
## Self-serve vs. sales-assisted Enterprise
Both self-serve and sales-assisted Enterprise plans include the same features and the same seat pricing. The differences are in how you purchase, pay, and manage your plan:
[TABLE]
\*New self-serve Enterprise organizations can choose ACH bank transfer, credit card, or debit card at signup. Organizations upgrading from a Team plan start on credit card and can switch to ACH bank transfer afterward in **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**.
†For sales-assisted invoices of \$50,000 or more, only bank transfer (ACH or wire) is available.
**When to contact Sales:** If your organization needs invoicing, dedicated customer success management, or to pay with a currency other than USD, reach out to our **[Sales team](https://claude.com/contact-sales)** to set up a sales-assisted Enterprise plan.
------------------------------------------------------------------------
## How to get the Enterprise plan
### Self-serve Enterprise plans
Visit **[claude.ai/create/enterprise](https://claude.ai/create/enterprise)** to purchase an Enterprise plan directly. You can pay with a credit card or ACH bank transfer (USD only).
**About ACH bank transfers**
New self-serve Enterprise organizations can choose to pay by ACH bank transfer instead of credit card. ACH is a push-based payment method, which means you initiate the transfer from your bank's interface to send funds to Anthropic's virtual bank account number (VBAN). You select your payment method when you create your organization, and you can switch between ACH bank transfer, credit card, or debit card at any time in **[Organization settings \> Billing](https://claude.ai/admin-settings/billing)**.
Here's what to know about ACH payments:
- **Activation timing:** If you choose ACH as your payment method, your plan won't be activated until we receive the payment, which can take up to five business days.
- **No auto-reload for credits:** Auto-reload isn't available with ACH payments. To set up auto-reload for credits, you can add a credit card to your account.
- **Subscription and credits:** ACH organizations can pay both their subscription invoices and credit purchases via ACH. If you purchase credits with ACH, the credits won't be added to your account until the payment settles.
- **Adding seats:** If you increase your seat count, we'll generate an invoice for the additional seats, but the new seats are available to use right away.
- **Upgrading from Team:** Organizations upgrading from a Team plan pay by credit card during the upgrade. Once the upgrade is complete, you can switch to ACH in **Organization settings \> Billing**.
### Sales-assisted Enterprise plans
**[Contact our Sales team](https://claude.com/contact-sales)** to discuss your organization's needs.
### AWS Marketplace
Enterprise is also available through the **[AWS Marketplace](https://aws.amazon.com/marketplace/pp/prodview-nnvi6wff6ef6m)**.
If your organization is currently on a Team plan and you're interested in upgrading to Enterprise, see this article for more information: **[Migrate your organization from Team to Enterprise](../13-Enterprise-Admin/migrate-your-organization-from-team-to-enterprise.md)**.
------------------------------------------------------------------------
## Information for organizations on Chat and Chat + Claude Code seats
**Note:** Organizations currently using usage-based Enterprise plans with Chat and Chat + Claude Code seats will not be able to continue with this billing model past your next contract renewal.
Some existing usage-based Enterprise organizations currently have two seat types: **Chat** and **Chat + Claude Code**. If you see these seat types in **[Organization settings \> Members](https://claude.ai/admin-settings/members)**, this section applies to you.
Your current seat types and pricing will remain in place until your next contract renewal. At renewal, your plan will automatically transition to the single Enterprise seat model described above—all users will move to the all-inclusive **Enterprise seat** **priced** **per user per month**, which includes Claude Code access.
For details on how seat management works on your current plan, see **[Purchase and manage seats on Enterprise plans](purchasing-and-managing-seats-on-enterprise-plans.md#h_2673e097fb)**.
------------------------------------------------------------------------
## Information for organizations on seat-based Enterprise plans
**Note:** Organizations currently using seat-based Enterprise plans with Standard and Premium seats will not be able to continue with this billing model past your next contract renewal.
Some Enterprise organizations are on older seat-based plans that use **Standard** and **Premium** seats with per-seat usage limits, rather than the usage-based model described above. If you see "Standard" and "Premium" seats when you navigate to **[Organization settings \> Members](https://claude.ai/admin-settings/members)**, this section applies to you.
Seat-based Enterprise plans haven't changed; your seat types, usage limits, and usage credit options will remain as they are until you migrate to the current usage-based billing model. For details on how usage credits work on your plan, see **[Manage usage credits for Team and seat-based Enterprise plans](https://support.claude.com/en/articles/12005970-)**.
If you're interested in migrating to the current usage-based model, reach out to your Anthropic Contact or **[our Sales team](https://claude.com/contact-sales)**.
---
## What is the Max plan? | Claude Help Center
Source: https://support.claude.com/en/articles/11049741-what-is-the-max-plan
Path: 17-Billing-Plans/what-is-the-max-plan.md
# What is the Max plan?
This article is about paid Max plans for individual consumers. If you're part of an organization looking to use Claude with your team, refer to **[Team and Enterprise plans](https://support.claude.com/en/collections/9387370-team-and-enterprise-plans)**.
The Max plan is designed for users who collaborate with Claude frequently and need more usage to work on a variety of tasks. In addition to providing higher usage limits than the Pro plan, Max plan subscribers will also receive priority access to our newest features and models.
## Key benefits
- **More usage capacity**: Get 5x or 20x the Pro plan's usage allowance, depending on your selected tier.
- **Fewer interruptions**: Stay in flow when it matters most with higher usage limits that allow for deeper, more extensive work with Claude.
- **Scale as needed**: Choose the usage tier that matches your workflow, with the flexibility to adjust as your needs change.
- **Priority access**: Be among the first to experience new models, features, and products.
- **Access to Claude Code: [Use Claude Code](https://support.claude.com/en/articles/11145838)** for your terminal-based coding workflows with one unified subscription.
- **Longer, multi-step tasks:** Hand Claude work like reports, spreadsheets, and presentations, and it keeps going in the background. Learn more in **[Claude Cowork and chat are one Claude](https://support.claude.com/en/articles/16761823)**.
- **Monthly API credits:** Claude Max and Team plans include monthly credits for the Claude API. Learn more about **[monthly API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)**.
------------------------------------------------------------------------
## How much does the Max plan cost?
### Pricing tiers
The Max plan is available in two tiers to match your usage needs:
- **Max 5x**: \$100 per month
- **Max 20x**: \$200 per month
**Note:** These prices are for web subscriptions only. Mobile pricing may vary depending on your app platform.
Price and plans are subject to change at Anthropic's discretion.
### Billing information
- The Max plan is currently available as a monthly subscription only.
- When upgrading from a lower to a higher tier, your account will be charged on a prorated basis for the remainder of your billing cycle. If you’ve claimed monthly API credits, you receive prorated credits right away, then the higher amount each billing cycle after that.
- When moving from an annual Pro plan to a Max plan, if the remaining balance on your annual Pro plan is greater than your Max plan price, you will receive a credit to your account for the remaining balance. This credit will be applied to future subscription costs.
- To receive your credit, the billing address used to purchase your Max plan must be the same as your previous subscription’s billing address.
- If your billing address has changed, you will need to cancel your Pro subscription and wait for the subscription end date before signing up for a new Max subscription with a new billing address.
- If you subscribed through Google Play, you're charged the full price of your new plan when you upgrade. The unused value of your previous plan is converted into extra days on your new plan, so your renewal date will land a few days later than a full month.
### How can I get a free or discounted Max plan?
We don’t offer standard discounted pricing for individual plans (Pro and Max), including Max 5x and Max 20x. With that said, anyone in a supported location can access the free version of Claude by navigating to **[claude.ai](https://claude.ai/)** and signing up using an email address.
We occasionally run limited-time promotions, but we don't have any standing discounts available upon request. These promotional offers are typically announced through our official channels when available. If you're interested in potential future promotions, we recommend following our official social media accounts or signing up for our newsletter to be notified of any special offers. Our Support team cannot issue one-off discounts or coupons.
Eligible nonprofit organizations can get discounted pricing on Team and Enterprise plans. Learn more about **[Claude for Nonprofits](../18-Industry-UseCases/nonprofits.md)**.
------------------------------------------------------------------------
## Does the Max plan have any usage limits?
Yes. The Max plan offers substantially higher usage compared to our Pro plan and is available in two tiers:
**Max 5x** includes five times the Pro plan's per-session usage allowance. This tier is ideal for frequent users who work with Claude on a variety of tasks.
**Max 20x** includes 20 times the Pro plan's per-session usage allowance. This tier is ideal for daily users who collaborate often with Claude for most tasks.
Your session-based usage limit will reset every five hours. Max plans also have a weekly usage limit that applies across all models. The weekly limit resets at a fixed time each week that is assigned to your account. Your reset day and time stay the same regardless of when you start using Claude or when your subscription begins, and you receive your full weekly allowance each cycle. You can see your next reset time in **[Settings \> Usage](https://claude.ai/new#settings/usage)**.
In addition, to manage capacity and ensure fair access to all users, we may limit your usage in other ways, such as weekly and monthly caps or model and feature usage, at our discretion.
For more information about usage and length limits, refer to **[Understanding usage and length limits](../22-Safety-Policy/understanding-usage-and-length-limits.md)**. For guidance on using your Max capacity efficiently, we also have **[Usage limit best practices](usage-limit-best-practices.md)**.
**Note:** If you have a limit reset, you can use it to reset your five-hour session limit or weekly usage limits back to full. Learn more **[about limit resets](https://support.claude.com/en/articles/17007452)**.
---
## What is the Pro plan? | Claude Help Center
Source: https://support.claude.com/en/articles/8325606-what-is-the-pro-plan
Path: 17-Billing-Plans/what-is-the-pro-plan.md
# What is the Pro plan?
This article is about paid Pro plans for individual consumers. If you're part of an organization looking to use Claude with your team, refer to **[Team and Enterprise Plans](https://support.claude.com/en/collections/9387370-team-and-enterprise-plans)**.
The Pro plan is a paid plan for our Claude chat experience. It is currently available in certain **[supported locations](../15-Claude-AI-Features/where-can-i-access-claude.md)**.
## Key benefits
The benefits of the Pro plan are:
- More usage per session than the Free plan.
- Priority access to Claude during high-traffic periods.
- Early access to new features that help you get the most out of Claude.
- **[Claude Code access](using-claude-code-with-your-pro-or-max-plan.md)**
- **[Longer, multi-step tasks](https://support.claude.com/en/articles/16761823)**
Learn how to **[sign up for the Pro plan](../21-Account-Support/how-do-i-sign-up-for-the-pro-plan.md)**.
**Note:** The Pro plan does not include API usage through the Claude Console. If you're interested in both enhanced Claude features and the Claude API, you'll need to **[set up Console access](../04-API-Reference/Other/how-can-i-access-the-claude-api.md)** to pay for API usage separately.
------------------------------------------------------------------------
## How much does the Pro plan cost?
The Pro plan is available for \$20 per month (US), with pricing in your local currency where supported. Monthly pricing varies by region, and some regions include applicable taxes in the displayed price while others add tax at checkout.
You can choose to save with an annual subscription plan. Annual subscriptions are billed once yearly at a discounted rate.
Visit **[claude.ai/upgrade](https://claude.ai/upgrade)** or check your mobile app store for current pricing in your region.
Price and plans are subject to change at Anthropic's discretion.
## How can I get a free or discounted Pro plan?
We don’t offer standard discounted pricing for individual plans (Pro and Max). With that said, anyone in a supported location can access the free version of Claude by navigating to **[claude.ai](https://claude.ai/)** and signing up using an email address.
We occasionally run limited-time promotions, but we don't have any standing discounts available upon request. These promotional offers are typically announced through our official channels when available. If you're interested in potential future promotions, we recommend following our official social media accounts or signing up for our newsletter to be notified of any special offers. Our Support team cannot issue one-off discounts or coupons.
Eligible nonprofit organizations can get discounted pricing on Team and Enterprise plans. Learn more about **[Claude for Nonprofits](../18-Industry-UseCases/nonprofits.md)**.
------------------------------------------------------------------------
## Does the Pro plan have any usage limits?
Yes. The Pro plan offers more usage per session than the Free plan. The number of messages you can send will vary based on message length, including the length of files you attach, the length of your current conversation, and the model or feature you use. Your session-based usage limit will reset every five hours.
Pro plans also have a weekly usage limit that applies across all models. Weekly limits reset at a fixed time each week that is assigned to your account. Your reset day and time stay the same regardless of when you start using Claude or when your subscription begins, and you receive your full weekly allowance each cycle. You can see your next reset time in **[Settings \> Usage](https://claude.ai/new#settings/usage)**.
In addition, to manage capacity and ensure fair access to all users, we may limit your usage in other ways, such as weekly and monthly caps or model and feature usage, at our discretion.
For more information about usage and length limits, refer to **[Understanding usage and length limits](../22-Safety-Policy/understanding-usage-and-length-limits.md)**. For guidance on using your Pro capacity efficiently, we also have **[Usage limit best practices](usage-limit-best-practices.md)**.
**Note:** If you have a limit reset, you can use it to reset your five-hour session limit or weekly usage limits back to full. Learn more **[about limit resets](https://support.claude.com/en/articles/17007452)**.
### How do I increase my Pro plan usage limits?
Our Max plans offer more usage for individuals than Pro plans. For additional information, see **[What is the Max plan?](what-is-the-max-plan.md)**
Pro subscribers can also enable usage credits to continue working with Claude beyond the plan’s included usage limits. For more information and instructions for enabling this feature, see **[Manage usage credits for paid Claude plans](https://support.claude.com/en/articles/12429409-)**.
---
## What is the Team plan? | Claude Help Center
Source: https://support.claude.com/en/articles/9266767-what-is-the-team-plan
Path: 17-Billing-Plans/what-is-the-team-plan.md
# What is the Team plan?
The Team plan is a paid plan for our Claude chat experience built for ambitious teams. It is currently available in certain **[supported locations](../15-Claude-AI-Features/where-can-i-access-claude.md)**.
## What’s included in the Team plan?
Users with Standard seats on the Team plan can access the following:
- **Increased usage:** A larger per-session usage allowance than the Pro plan, so every team member can get what they need from Claude.
- **Option to purchase usage credits:** Prepay for usage credits, allowing team members to continue working after reaching limits.
- Read more here: **[Manage usage credits for Team and seat-based Enterprise plans](https://support.claude.com/en/articles/12005970-)**
- **Admin tools and billing management:** Manage access and billing in a centralized place.
- **Advanced identity and access management:**
- **Single-Sign-On (SSO) and Domain Capture:** Enhance authentication security and user experience.
- **Just-in-Time Provisioning (JIT):** Streamline user authentication and manage access across your organization.
- **Role-based permissioning:** Customize access levels and control user privileges across your organization.
- **Spend controls:** Set spending caps at organization and individual user levels.
- **Enterprise search capabilities:** Dedicated search project for unified knowledge access.
- Pre-configured with optimized search instructions
- Automatic provisioning for all organization members
- Search across Slack, Microsoft 365, and custom connectors
- For more details, see **[Use enterprise search](https://support.claude.com/en/articles/12489464)**
- **Connectors for your workplace tools:** Connect Claude to Google Drive, Gmail, Google Calendar, GitHub, Microsoft 365, and Slack to search and retrieve context from your existing documents, emails, calendars, and team communications—without manual uploads.
- **Monthly API credits:** Claude Max and Team plans include monthly credits for the Claude API. Learn more about **[monthly API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)**.
- **Everything in Pro, including:**
- Access to all available models.
- Access to Claude Code to delegate coding tasks from concept to completion directly from your terminal.
- Access to **[Cowork](https://support.claude.com/en/articles/13345190-get-started-with-cowork)**.
- Access to projects, knowledge bases, and collaboration features.
- 200k context window. Room to process long documents, discuss complex topics, and maintain multi-step conversations.
- Priority access during high-traffic periods, early access to new features, more usage, and more.
------------------------------------------------------------------------
## Premium seats for Team plans
In addition to all features of Standard seats listed above, Premium seats offer significantly more usage than Standard seats. This makes Premium seats ideal for power users who need extended capacity for demanding workloads.
Organizations can mix and match seat types, assigning Premium seats to power users who need more usage while keeping other team members on Standard seats.
Refer to this article for more information about Premium seats: **[Purchase and manage seats on Team plans](https://support.claude.com/en/articles/12004354)**.
------------------------------------------------------------------------
## How much does the Team plan cost?
Team plans require a minimum of two members. Pricing varies by seat type and billing interval:
**Standard seats**
- \$25 per member per month, billed monthly
- \$20 per member per month, billed annually
**Premium seats**
- \$125 per member per month, billed monthly
- \$100 per member per month, billed annually
Prices shown are for US customers and exclude applicable taxes. Pricing, currency, and tax handling vary by region. Visit **[claude.ai/upgrade](https://claude.ai/upgrade)** to see current pricing for your location.
For more details on billing, see **[How is my Team plan bill calculated?](how-is-my-team-plan-bill-calculated.md)**
Team plans support up to 150 seats. If your organization is on the Team plan and needs more than 150 seats, you can upgrade to the **[Enterprise plan](what-is-the-enterprise-plan.md)**. For more information, see **[Migrate your organization from Team to Enterprise](../13-Enterprise-Admin/migrate-your-organization-from-team-to-enterprise.md)**.
Price and plans are subject to change at Anthropic's discretion.
------------------------------------------------------------------------
## Do Team plans have any usage limits?
Yes. For both Standard and Premium seats, weekly limits reset at a fixed time each week that is assigned to your account. Your reset day and time stay the same regardless of when you start using Claude or when your subscription begins, and you receive your full weekly allowance each cycle. You can see your next reset time in **[Settings \> Usage](https://claude.ai/new#settings/usage)**.
Usage limits differ between Standard and Premium seats in the following ways:
**Standard seats:** Team plan Standard seats include 1.25x the Pro plan's per-session usage allowance and have a weekly usage limit that applies across all models.
**Premium seats:** Team plan Premium seats include 6.25x the Pro plan's per-session usage allowance and have a weekly usage limit that applies across all models.
**Note:** If you have a limit reset, you can use it to reset your five-hour session limit or weekly usage limits back to full. Learn more **[about limit resets](https://support.claude.com/en/articles/17007452)**.
### Do usage limits apply across the team or to individual members?
Usage limits on Team plans are per-member, rather than applied to the team as a whole.
This means:
- Each team member has their own set of usage limits.
- If one team member reaches their seat's included usage limit, it does not affect the limits of other team members.
- Other team members can continue to use the service even if one member has reached their seat's included limit.
- Usage limits can't be transferred or shared between team members. Each seat is for one named individual. Learn more about **[who can use a seat](https://support.claude.com/en/articles/12004354-purchase-and-manage-seats-on-team-plans#h_b8a7d07129)**.
### How do I increase my Team plan usage limits?
Your Team plan organization can enable usage credits to allow team members on all seat types to continue working with Claude, Cowork, and Claude Code after reaching their included usage limits. For more information, see **[Manage usage credits for Team and seat-based Enterprise plans](https://support.claude.com/en/articles/12005970-)**.
---
## Why am I being asked to verify my payment method? | Claude Help Center
Source: https://support.claude.com/en/articles/11818288-why-am-i-being-asked-to-verify-my-payment-method
Path: 17-Billing-Plans/why-am-i-being-asked-to-verify-my-payment-method.md
# Why am I being asked to verify my payment method?
March 16, 2026
If you see the following pop-up when you log in to your Claude account, you’ll need to click the “Verify now” button to verify your payment method:
## What happens if I click “Remind me later?”
Clicking “Remind me later” will dismiss the verification modal for 24 hours, after which you’ll be prompted again.