# Account Support All documentation for Account Support. --- ## account-management-faqs-c6267449e9.md # Account management FAQs August 6, 2026 Copy for LLM ## How do I change my team name? Owners can update the team name on their plan by navigating to **[Organization settings \> Organization](https://claude.ai/admin-settings/organization)** and clicking "Update" under the current team name. Type in a new name and click "Save." ## How can I change a Team or Enterprise plan member’s name? It's not possible to change another user's name on their behalf, but a user can edit their own name by following these steps: 1. Log in to your Claude account. 2. Navigate to **[Settings \> General](https://claude.ai/settings/general)**. 3. Make edits to the "Full name" field and click "Save changes." ## Can I create multiple teams? **For Team plans:** Yes, you can create multiple teams by purchasing multiple Team plans. To create a new Team plan, you can navigate directly to our team creation page and start by naming your team. **For Enterprise plans:** If you're interested in purchasing multiple Enterprise plans, you can **[reach out to our Sales team](https://claude.com/contact-sales)**. ## How do I view a list of all members on a team? Admins and Owners can view a list of all members on a team by navigating to **[Organization settings \> Organization](https://claude.ai/admin-settings/organization)**. ## How can I view or add allowed email domains? The email domain that was used to create your Team or Enterprise plan organization is the allowed email domain for your team members. After the account is created, Owners of organizations that are not using domain capture can add additional domains by following these steps: 1. Navigate to **[Organization](https://claude.ai/admin-settings/organization) [settings \> Identity and access](https://claude.ai/admin-settings/identity).** 2. Click "Add or edit domains" under **Domains**. 3. In the **Update organization email domains** modal that appears, enter the new domain. 4. Click the "+" button to add the domain. 5. Click the "Save" button. Owners can remove domains by opening up the same modal and clicking the trash can icon to the right of the domain: While the account creator must use a business email address, you can add public domains like @gmail.com, @yahoo.com, and @hotmail.com as allowed domains for other members of your organization. --- ## account-management-faqs.md # Account management FAQs ## How do I change my team name? Owners can update the team name on their plan by navigating to **[Organization settings \> Organization](https://claude.ai/admin-settings/organization)** and clicking "Update" under the current team name. Type in a new name and click "Save." ## How can I change a Team or Enterprise plan member’s name? It's not possible to change another user's name on their behalf, but a user can edit their own name by following these steps: 1. Log in to your Claude account. 2. Navigate to **[Settings \> General](http://claude.ai/settings/general)**. 3. Make edits to the "Full name" field and click "Save changes." ## Can I create multiple teams? **For Team plans:** Yes, you can create multiple teams by purchasing multiple Team plans. To create a new Team plan, you can navigate directly to our team creation page and start by naming your team. **For Enterprise plans:** If you're interested in purchasing multiple Enterprise plans, you can **[reach out to our Sales team](https://claude.com/contact-sales)**. ## How do I view a list of all members on a team? Admins and Owners can view a list of all members on a team by navigating to **[Organization settings \> Organization](https://claude.ai/admin-settings/organization)**. ## How can I view or add allowed email domains? The email domain that was used to create your Team or Enterprise plan organization is the allowed email domain for your team members. After the account is created, Owners of organizations that are not using domain capture can add additional domains by following these steps: 1. Navigate to **[Organization](https://claude.ai/admin-settings/organization)** **[settings \> Identity and access](https://claude.ai/admin-settings/identity).** 2. Click "Add or edit domains" under **Domains**. 3. In the **Update organization email domains** modal that appears, enter the new domain. 4. Click the "+" button to add the domain. 5. Click the "Save" button. Owners can remove domains by opening up the same modal and clicking the trash can icon to the right of the domain: While the account creator must use a business email address, you can add public domains like @gmail.com, @yahoo.com, and @hotmail.com as allowed domains for other members of your organization. --- ## add-or-update-your-claude-console-organization-s-tax-or-vat-id.md 4. Add or update your Claude Console organization's tax or VAT ID # Add or update your Claude Console organization's tax or VAT ID Updated today ## 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. Navigate to [Settings \> Organization](https://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. See [Understanding your billing address and tax calculation](../17-Billing-Plans/understanding-your-billing-address-and-tax-calculation.md) for details on how to view or update your billing address. --- ## add-or-update-your-paid-claude-account-s-tax-or-vat-id-f252f64856.md # Add or update your paid Claude account’s tax or VAT ID August 6, 2026 Copy for LLM ## 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](https://support.claude.com/en/articles/12997130-understanding-your-billing-address-and-tax-calculation)** for details on how to view or update your billing address. --- ## add-or-update-your-paid-claude-account-s-tax-or-vat-id.md 4. Add or update your paid Claude account’s tax or VAT ID # Add or update your paid Claude account’s tax or VAT ID ## 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](http://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](http://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](../17-Billing-Plans/understanding-your-billing-address-and-tax-calculation.md) for details on how to view or update your billing address. --- ## assign-a-program-to-workspaces-in-claude-console-d6333251d9.md # Assign a program to workspaces in Claude Console Copy for LLM Anthropic offers several verification programs, such as the Cyber Verification Program, or access to models that might not be generally available. In order to gain access to these programs, go to our **[Verification Portal](https://portal.anthropic.com/)** to see what programs are available to you, and apply. Once you’ve applied and been approved for a program, Anthropic issues a “program” to your organization. In order for it to be used, you must assign it to a group of people within the organization. In the Claude Console, a program applies to workspaces, either automatically (for programs like the Cyber Verification Program) or by assignment. This article covers how to enable programs for the Console. ## Before you start - Your organization must already have a grant. Grants appear only after Anthropic issues one to your organization. To apply to a specific program, go to our **[Verification Portal](https://portal.anthropic.com/)** to see what programs are available. - In the Console, you need to be an organization Admin. Other roles cannot view or manage grants. ## Give a Console workspace access In the Console, programs are issued to your organization and apply to workspaces. Some programs, such as the Cyber Verification Program, apply automatically to every workspace that meets their requirements. Others need workspaces assigned. A program only applies to API traffic from workspaces that meet its requirements. **Follow these steps:** 1. **[Sign in to the Console](https://platform.claude.com/)** as an organization Admin. Go to **[Organization settings \> Programs](https://platform.claude.com/settings/organization/programs)**. The program card shows whether it applies automatically or needs workspaces assigned. 2. Select the program to open its page. The **Workspaces** table shows each workspace's status. A workspace marked with an issue does not meet a requirement yet. Hover over the issue to see which requirement is not met. 3. To give a workspace access, make it meet the requirements. Open the workspace, select "Manage," then "Programs," and check the **Qualifications** panel. 4. Fix the requirement. For the Cyber Verification Program, turn on data retention under Manage, then Privacy controls. Then select "Rerun." 5. The program shows **Active** for the workspace. ## Troubleshooting - **The Grants page is missing.** Your organization does not have a grant yet, or you are not an organization Admin. Contact your Anthropic account team or your admin. - **The workspace shows as inactive.** Open the workspace, select "Manage," then "Programs," and check the **Qualifications** panel for an unmet requirement. Fix each unmet requirement and try again. - **The grant is over its seat limit.** Some programs have a seat cap. Assigned workspaces lose access until your organization is back under the limit. Reduce the number of members counted toward the grant, then check again. - **You are trying to use the default Console workspace.** Some programs don't allow the program to be assigned to the default workspace. If the default workspace isn’t working, assign a different workspace or create a new one. --- ## assign-tasks-from-anywhere-in-claude-cowork-7d0db733ce.md # Assign tasks from anywhere in Claude Cowork Copy for LLM **Note:** Claude Cowork is now just 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, with more plans to follow. If you're on a Pro or Max plan and your message box no longer shows "Chat" and "Cowork" options, you have the new experience, and some steps in this article may look different. Learn more in **[Claude Cowork and chat are one Claude](https://support.claude.com/en/articles/16761823)**, or read our **[blog post](https://claude.com/blog/cowork-is-now-claude)**. Claude Cowork gives you one continuous conversation with Claude that you can reach from your phone or your desktop. With Dispatch, you can message Claude from your phone and have it work on your desktop computer, using your local files, connectors, plugins, and apps, then come back to the finished work. **Note:** Dispatch isn't available to new users. If you already use Dispatch, you can keep using it for now, and this article still applies. Dispatch runs your tasks on your desktop, so your computer needs to be awake and the Claude Desktop app open while Claude works. This is different from a cloud session, which runs on Anthropic's servers and keeps working even when your computer is off. For where Cowork runs on each surface, see **[Use Claude Cowork on web, desktop, and mobile](https://support.claude.com/en/articles/15520349)**. This capability is in limited beta for Pro and Max plans on Claude Cowork, and it requires both the Claude Desktop app and the Claude mobile app. Dispatch is only available for some Pro and Max plans, so if you don't see Dispatch in the Cowork side panel, you should **[use Cowork in the cloud](https://support.claude.com/en/articles/15520349)** instead of the pairing flow described here. ------------------------------------------------------------------------ ## Requirements To use this capability, you need: - The most recent version of the **Claude Desktop app** installed and running on your computer (macOS, Windows x64, or Linux). Your computer must be awake and the app must be open for Claude to work on tasks. Download or update at **[claude.com/download](http://claude.com/download)**. - The most recent version of the **Claude mobile app** installed on your phone. Existing mobile app users will need to update to the latest version before using this capability. - **A Pro or Max plan**. - **An active internet connection** on both devices. ------------------------------------------------------------------------ ## How it works Instead of starting a new session for each task, you have a single persistent thread with Claude. This thread doesn't reset. Claude retains context from previous tasks, so you can pick up where you left off. Message Claude from your phone on the way to work, then follow up from your desktop when you sit down. It's the same conversation, same context, wherever you reach it. When you assign a task, Claude figures out what kind of work is needed and spins up the right session. Development tasks run in Claude Code; knowledge work runs in Cowork. These sessions appear in their respective sidebars. You can click into any session for details, or wait for the result in the thread. Claude messages you the outcome (a spreadsheet, a memo, a comparison table, a pull request) rather than showing you every step of the process. You'll get a push notification on your phone when a task is done or when Claude needs your go-ahead. ------------------------------------------------------------------------ ## Get started Follow these steps to get started: 1. Download or update Claude Desktop. 2. Download or update Claude for iOS or Android. 3. Open Cowork on either your phone or your desktop. 4. Click “Dispatch” on the left side panel. 5. You’ll land on a page describing the functionality. Click “Get started”: 6. On the next screen, you can give Claude access to your files and keep your computer awake by toggling those on: 7. Click “Finish setup.” 8. Start messaging Claude within the “Dispatch” section. After completing these steps, your continuous conversation with Claude syncs across both surfaces automatically. ------------------------------------------------------------------------ ## What you can do From your phone, you can hand Claude tasks that use everything on your desktop, including things you can't open on your phone. For example: - Ask Claude to pull data from a local spreadsheet and compile a summary report. - Have Claude search your Slack messages and email, then draft a briefing document. - Request a formatted presentation built from files in your Google Drive. - Tell Claude to organize or process files in a specific folder on your computer. Claude uses the same connectors, plugins, and file access you've already configured in Cowork. You don't need to set anything up separately for mobile. ### Retrieve files and outputs When Claude finishes a task that produces a file, you can access it directly from mobile or find it on your desktop at the location Claude specifies. ### Memory Claude remembers what you've worked on and learns how you work. Context carries across sessions, so you don't have to re-explain your preferences, your projects, or how you like things done. You control what Claude remembers. You can view, edit, and delete your memory at any time. ### Scheduled tasks and routines You can set up tasks that Claude runs automatically on a schedule. Tell Claude once to check your email every morning, pull your metrics every week, or compile a Friday report, and it handles it from there without being asked again. For more on setting up and managing scheduled tasks, see **[Schedule recurring tasks in Cowork](https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-cowork)**. ### Computer use Claude can use the apps on your computer to complete tasks you assign through Dispatch. If you ask Claude to update a spreadsheet in Excel, navigate an internal dashboard, or run your dev tools, Claude can work directly with those apps on your desktop. For details on how computer use works, permissions, and safety guidance, see **[Let Claude use your computer in Cowork](https://support.claude.com/en/articles/14128542-computer-use-safety)**. **Note:** Computer use isn't available in the Linux beta. On a Linux desktop, Dispatch still works with your files, connectors, and plugins, but it can't drive desktop apps through computer use. ------------------------------------------------------------------------ ## Safety considerations From your phone, you can now access everything on your desktop through Claude—including files, connectors, any plugins you've installed, and your apps through computer use. Giving a mobile AI agent remote control of a desktop AI agent creates a chain where instructions from your phone can trigger real actions on your computer: reading, moving, or deleting local files, interacting with connected services, controlling your browser, and using your desktop apps. This is powerful, but it also means mistakes (or malicious content the model encounters along the way) can have real consequences. A manipulated instruction, an unexpected command, or a phishing link opened in your browser could cascade into actions that are difficult or impossible to undo. Before enabling this, make sure you: - Trust every app and service in the chain - Understand what files and accounts are accessible - Know how to quickly disconnect or revoke access Only connect these agents if you're comfortable with what they *could* do, not just what you intend them to do. For additional safety guidance, see **[Use Cowork safely](https://support.claude.com/en/articles/13364135-use-cowork-safely)**. ------------------------------------------------------------------------ ## Current limitations The following limitations apply: - **Your desktop must be active.** Dispatch works with the local files and apps on your desktop computer, so your computer needs to be awake and the Claude Desktop app open while Claude works. If you want Claude to keep working while your computer is off, start a cloud session instead. See **[Use Claude Cowork on web, desktop, and mobile](https://support.claude.com/en/articles/15520349)**. - **Computer use has different safety properties than other Cowork tools.** Claude clicks, types, and navigates your screen directly rather than going through connectors or permission-gated file access. For details, see **[Let Claude use your computer in Cowork](https://support.claude.com/en/articles/14128542-computer-use-safety)**. - **One continuous thread.** There's no way to start a new thread or manage multiple threads. All messages live in a single conversation. - **On Linux, tasks that rely on computer use aren't available**, since computer use isn't part of the Linux beta. File, connector, and plugin tasks work as normal. --- ## assign-tasks-to-claude-from-anywhere-in-cowork-c5119e93fb.md # Assign tasks from anywhere in Claude Cowork Copy for LLM **Note:** Claude Cowork is now just 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, with more plans to follow. If you're on a Pro or Max plan and your message box no longer shows "Chat" and "Cowork" options, you have the new experience, and some steps in this article may look different. Learn more in **[Claude Cowork and chat are one Claude](https://support.claude.com/en/articles/16761823)**, or read our **[blog post](https://claude.com/blog/cowork-is-now-claude)**. Claude Cowork gives you one continuous conversation with Claude that you can reach from your phone or your desktop. With Dispatch, you can message Claude from your phone and have it work on your desktop computer, using your local files, connectors, plugins, and apps, then come back to the finished work. **Note:** Dispatch isn't available to new users. If you already use Dispatch, you can keep using it for now, and this article still applies. Dispatch runs your tasks on your desktop, so your computer needs to be awake and the Claude Desktop app open while Claude works. This is different from a cloud session, which runs on Anthropic's servers and keeps working even when your computer is off. For where Cowork runs on each surface, see **[Use Claude Cowork on web, desktop, and mobile](https://support.claude.com/en/articles/15520349)**. This capability is in limited beta for Pro and Max plans on Claude Cowork, and it requires both the Claude Desktop app and the Claude mobile app. Dispatch is only available for some Pro and Max plans, so if you don't see Dispatch in the Cowork side panel, you should **[use Cowork in the cloud](https://support.claude.com/en/articles/15520349)** instead of the pairing flow described here. ------------------------------------------------------------------------ ## Requirements To use this capability, you need: - The most recent version of the **Claude Desktop app** installed and running on your computer (macOS, Windows x64, or Linux). Your computer must be awake and the app must be open for Claude to work on tasks. Download or update at **[claude.com/download](http://claude.com/download)**. - The most recent version of the **Claude mobile app** installed on your phone. Existing mobile app users will need to update to the latest version before using this capability. - **A Pro or Max plan**. - **An active internet connection** on both devices. ------------------------------------------------------------------------ ## How it works Instead of starting a new session for each task, you have a single persistent thread with Claude. This thread doesn't reset. Claude retains context from previous tasks, so you can pick up where you left off. Message Claude from your phone on the way to work, then follow up from your desktop when you sit down. It's the same conversation, same context, wherever you reach it. When you assign a task, Claude figures out what kind of work is needed and spins up the right session. Development tasks run in Claude Code; knowledge work runs in Cowork. These sessions appear in their respective sidebars. You can click into any session for details, or wait for the result in the thread. Claude messages you the outcome (a spreadsheet, a memo, a comparison table, a pull request) rather than showing you every step of the process. You'll get a push notification on your phone when a task is done or when Claude needs your go-ahead. ------------------------------------------------------------------------ ## Get started Follow these steps to get started: 1. Download or update Claude Desktop. 2. Download or update Claude for iOS or Android. 3. Open Cowork on either your phone or your desktop. 4. Click “Dispatch” on the left side panel. 5. You’ll land on a page describing the functionality. Click “Get started”: 6. On the next screen, you can give Claude access to your files and keep your computer awake by toggling those on: 7. Click “Finish setup.” 8. Start messaging Claude within the “Dispatch” section. After completing these steps, your continuous conversation with Claude syncs across both surfaces automatically. ------------------------------------------------------------------------ ## What you can do From your phone, you can hand Claude tasks that use everything on your desktop, including things you can't open on your phone. For example: - Ask Claude to pull data from a local spreadsheet and compile a summary report. - Have Claude search your Slack messages and email, then draft a briefing document. - Request a formatted presentation built from files in your Google Drive. - Tell Claude to organize or process files in a specific folder on your computer. Claude uses the same connectors, plugins, and file access you've already configured in Cowork. You don't need to set anything up separately for mobile. ### Retrieve files and outputs When Claude finishes a task that produces a file, you can access it directly from mobile or find it on your desktop at the location Claude specifies. ### Memory Claude remembers what you've worked on and learns how you work. Context carries across sessions, so you don't have to re-explain your preferences, your projects, or how you like things done. You control what Claude remembers. You can view, edit, and delete your memory at any time. ### Scheduled tasks and routines You can set up tasks that Claude runs automatically on a schedule. Tell Claude once to check your email every morning, pull your metrics every week, or compile a Friday report, and it handles it from there without being asked again. For more on setting up and managing scheduled tasks, see **[Schedule recurring tasks in Cowork](https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-cowork)**. ### Computer use Claude can use the apps on your computer to complete tasks you assign through Dispatch. If you ask Claude to update a spreadsheet in Excel, navigate an internal dashboard, or run your dev tools, Claude can work directly with those apps on your desktop. For details on how computer use works, permissions, and safety guidance, see **[Let Claude use your computer in Cowork](https://support.claude.com/en/articles/14128542-computer-use-safety)**. **Note:** Computer use isn't available in the Linux beta. On a Linux desktop, Dispatch still works with your files, connectors, and plugins, but it can't drive desktop apps through computer use. ------------------------------------------------------------------------ ## Safety considerations From your phone, you can now access everything on your desktop through Claude—including files, connectors, any plugins you've installed, and your apps through computer use. Giving a mobile AI agent remote control of a desktop AI agent creates a chain where instructions from your phone can trigger real actions on your computer: reading, moving, or deleting local files, interacting with connected services, controlling your browser, and using your desktop apps. This is powerful, but it also means mistakes (or malicious content the model encounters along the way) can have real consequences. A manipulated instruction, an unexpected command, or a phishing link opened in your browser could cascade into actions that are difficult or impossible to undo. Before enabling this, make sure you: - Trust every app and service in the chain - Understand what files and accounts are accessible - Know how to quickly disconnect or revoke access Only connect these agents if you're comfortable with what they *could* do, not just what you intend them to do. For additional safety guidance, see **[Use Cowork safely](https://support.claude.com/en/articles/13364135-use-cowork-safely)**. ------------------------------------------------------------------------ ## Current limitations The following limitations apply: - **Your desktop must be active.** Dispatch works with the local files and apps on your desktop computer, so your computer needs to be awake and the Claude Desktop app open while Claude works. If you want Claude to keep working while your computer is off, start a cloud session instead. See **[Use Claude Cowork on web, desktop, and mobile](https://support.claude.com/en/articles/15520349)**. - **Computer use has different safety properties than other Cowork tools.** Claude clicks, types, and navigates your screen directly rather than going through connectors or permission-gated file access. For details, see **[Let Claude use your computer in Cowork](https://support.claude.com/en/articles/14128542-computer-use-safety)**. - **One continuous thread.** There's no way to start a new thread or manage multiple threads. All messages live in a single conversation. - **On Linux, tasks that rely on computer use aren't available**, since computer use isn't part of the Linux beta. File, connector, and plugin tasks work as normal. --- ## assign-tasks-to-claude-from-anywhere-in-cowork.md 4. Assign tasks to Claude from anywhere in Cowork # Assign tasks to Claude from anywhere in Cowork Cowork now gives you one continuous conversation with Claude that you can reach from your phone or your desktop. Assign Claude a task, go do something else, and come back to the finished work. Claude runs on your computer—with access to your local files, connectors, and plugins—and messages you the result when it's done. This capability is available as a research preview in Cowork on Pro and Max plans. It requires both the Claude Desktop app and the Claude mobile app. ------------------------------------------------------------------------ ## Requirements To use this capability, you need: - The most recent version of the **Claude Desktop app** installed and running on your computer (macOS or Windows x64). Your computer must be awake and the app must be open for Claude to work on tasks. Download or update at **[claude.com/download](http://claude.com/download)**. - The most recent version of the **Claude mobile app** installed on your phone. Existing mobile app users will need to update to the latest version before using this capability. - **A Pro or Max plan**. - **An active internet connection** on both devices. ------------------------------------------------------------------------ ## How it works Instead of starting a new session for each task, you have a single persistent thread with Claude. This thread doesn't reset—Claude retains context from previous tasks, so you can pick up where you left off. Message Claude from your phone on the way to work, then follow up from your desktop when you sit down. It's the same conversation, same context, wherever you reach it. When you assign a task, Claude works on your desktop computer using the files, connectors, and plugins you've already set up in Cowork. Claude messages you the outcome—a spreadsheet, a memo, a comparison table—rather than showing you every step of the process. ------------------------------------------------------------------------ ## Get started Follow these steps to get started: 1. Download or update Claude Desktop. 2. Download or update Claude for iOS/Android. 3. Open Cowork on either your phone or your desktop. 4. Click “Dispatch” on the left side panel. 5. You’ll land on a page describing the functionality. Click “Get started”: 6. On the next screen, you can give Claude access to your files and keep your computer awake by toggling those on: 7. Click “Finish setup.” 8. Start messaging Claude within the “Dispatch” section. After completing these steps, your continuous conversation with Claude syncs across both surfaces automatically. ------------------------------------------------------------------------ ## What you can do From your phone, you can hand Claude tasks that use everything on your desktop, including things you can't open on your phone. For example: - Ask Claude to pull data from a local spreadsheet and compile a summary report. - Have Claude search your Slack messages and email, then draft a briefing document. - Request a formatted presentation built from files in your Google Drive. - Tell Claude to organize or process files in a specific folder on your computer. Claude uses the same connectors, plugins, and file access you've already configured in Cowork. You don't need to set anything up separately for mobile. ### Retrieve files and outputs When Claude finishes a task that produces a file, you can access it directly from mobile or find it on your desktop at the location Claude specifies. ------------------------------------------------------------------------ ## Safety considerations From your phone, you can now access everything on your desktop through Claude—including files, connectors, and any plugins you've installed. Be mindful of what access you've granted Claude in Cowork, since this capability extends that access to a mobile surface. Giving a mobile AI agent remote control of a desktop AI agent creates a chain where instructions from your phone can trigger real actions on your computer—including reading, moving, or deleting local files, interacting with connected services, and controlling your browser. This is powerful, but it also means mistakes (or malicious content the model encounters along the way) can have real consequences. A manipulated instruction, an unexpected command, or a phishing link opened in your browser could cascade into actions that are difficult or impossible to undo. Before enabling this, make sure you: - Trust every app and service in the chain - Understand what files and accounts are accessible - Know how to quickly disconnect or revoke access Only connect these agents if you're comfortable with what they *could* do, not just what you intend them to do. For additional safety guidance, see **[Use Cowork safely](../15-Claude-AI-Features/use-cowork-safely.md)**. ------------------------------------------------------------------------ ## Current limitations This is a research preview with the following limitations: - **Your desktop must be active.** Claude works on your desktop computer. If your computer is asleep or the Claude Desktop app is closed, Claude can't work on tasks. - **Claude responds to messages only.** Claude won't reach out proactively—it only works on tasks you assign. - **One continuous thread.** There's no way to start a new thread or manage multiple threads. All messages live in a single conversation. - **No notifications when tasks complete.** There are currently no notifications on mobile or desktop when Claude completes a task. - **No scheduled tasks in this thread.** Scheduled tasks are managed separately. See **[Schedule recurring tasks in Cowork](../15-Claude-AI-Features/schedule-recurring-tasks-in-cowork.md)** for details. --- ## can-i-have-a-claude-account-and-a-console-account-6868f2c91e.md # Can I have a Claude account and a Console account? March 16, 2026 Copy for LLM Yes. You can have a Claude account (free, Pro, Max, Team, or Enterprise) and a Console account (to access the Claude API) with the same email address. These two accounts will operate independently. --- ## can-i-have-a-claude-account-and-a-console-account.md 4. Can I have a Claude account and a Console account? # Can I have a Claude account and a Console account? Yes. You can have a Claude account (free, Pro, Max, Team, or Enterprise) and a Console account (to access the Claude API) with the same email address. These two accounts will operate independently. --- ## can-individuals-with-pro-or-max-plan-accounts-migrate-them-to-team-or-enterprise.md 4. Can individuals with Pro or Max plan accounts migrate them to Team or Enterprise plan organizations? # Can individuals with Pro or Max plan accounts migrate them to Team or Enterprise plan organizations? Individual accounts (free, Pro, and Max) and organization accounts (Team and Enterprise) are separate account types with different features. You cannot migrate an individual account to a Team or Enterprise organization—if you're joining an organization, you'll need to be added as a new member. ## Is there any way to merge my Pro or Max plan account with my Team or Enterprise plan account? No, you cannot merge an individual Pro or Max plan account with a Team or Enterprise plan account, even if both accounts use the same email address. Because the two account types are intended for different use cases and don’t offer the same capabilities, they cannot be combined. ## How can users with multiple accounts manage them? Users with both individual and Team or Enterprise accounts tied to the same email address will be able to toggle between the two by clicking on their initials or name in the lower left corner of the screen: A blue checkmark shows which account you're currently using. Click on the other account to switch to it and access its separate conversations and projects. ## How can I discontinue my individual plan and export my data? If you’d prefer to discontinue your individual account and use only your Team or Enterprise plan account moving forward, start by **[canceling your individual paid plan](https://support.claude.com/en/articles/8325617-how-do-i-cancel-my-paid-claude-subscription)**. Once your subscription lapses and you're finished using the account, you can **[export your data](https://support.claude.com/en/articles/9450526-how-can-i-export-my-claude-data)**. Note that there isn't a way to transfer this data into a Team or Enterprise account. To **[delete your account](how-can-i-delete-my-claude-account.md)**, navigate to **[Settings \> Account](https://claude.ai/settings/account)** and click "Delete." ## Considerations for organizations using SSO Team and Enterprise plan organizations have access to single sign-on (SSO) and domain verification. Owners can: - Restrict usage of any verified domains to accounts added to the Team or Enterprise plan instance. - Prevent employees from creating new individual accounts with company email addresses. See **[Setting up Single Sign-on (SSO)](setting-up-single-sign-on-sso.md#h_5ee916332f)** for more information about domain verification and how it affects individual accounts. --- ## claim-and-migrate-accounts-on-your-domain-1a80070ccf.md # Claim and migrate accounts on your domain Copy for LLM Domain claiming lets Enterprise admins discover, claim, and migrate existing personal Claude accounts (Free, Pro, and Max) on a verified company domain into their Enterprise workspace. This gives your organization a clean path to consolidate accounts on day one of an Enterprise deployment, and allows people using Claude on personal accounts to keep their work. Domain claiming is available for Enterprise plans, whether purchased directly through Anthropic or through the AWS Marketplace, and works the same in both cases. Domain claiming is supported on Claude Enterprise plans only. Team plans can verify a domain and block new personal accounts from being created, but admins can't claim or migrate existing accounts. People on a Team plan can still migrate their own personal accounts voluntarily—see **[Move your personal Claude account to a Team or Enterprise organization](https://support.claude.com/en/articles/9267400)**. ------------------------------------------------------------------------ ## Prerequisites Before you can enable domain claiming, your organization must have all of the following in place: 1. Restrict organization creation on your verified domain. 2. Complete domain verification (DNS). 3. Enforce SSO (not just configured—SSO must be actively enforced). See **[Set up single sign-on (SSO)](https://support.claude.com/en/articles/13132885-set-up-single-sign-on-sso)**. 4. Enable JIT provisioning or SCIM. See **[Set up JIT or SCIM provisioning](https://support.claude.com/en/articles/13133195-set-up-jit-or-scim-provisioning)**. These prerequisites exist to prevent people from being locked out of Claude during the migration process. If SSO is enforced and provisioning is active, everyone on your domain will have a path to sign in after their accounts are migrated. ------------------------------------------------------------------------ ## How domain claiming works ### Review accounts on your domain After verifying your domain, you can view all existing personal accounts (Free, Pro, and Max) on that domain that aren’t already in your organization. For each account, you’ll see the email address, plan type, account creation date, and last active date. You can also export this list as a CSV. Use this view to understand the scope of migration before initiating a claim. Check which accounts are in your identity provider (IdP) and which aren’t—people not in the IdP won’t be able to sign in after migration unless you add them. ### Enable domain capture Navigate to **[Organization settings \> Organization and access](https://claude.ai/admin-settings/organization)**, scroll down to **Security** and toggle **Migrate accounts using your domain** on to enable domain capture. This is an organization-level setting that enforces a policy: no non-Enterprise accounts can exist on your verified domain. **Warning:** Domain capture is a one-way door. Once enabled, it can’t be reversed. The admin UI will display a prominent confirmation before you proceed. Make sure your prerequisites are fully in place and you’ve reviewed the affected accounts before enabling. ### Initiate the claim When you enable domain capture, you’ll walk through a flow that shows you the migration impact: - A preview of all accounts that will be affected (with CSV export) - Which accounts are in your IdP and which aren’t - Warnings about any potential issues Once confirmed, all affected accounts receive notification immediately—both by email and through an in-product banner. The migration window is 30 days from the date you initiate the claim. ### The 30-day migration window The migration deadline is a single date for the claim, not a rolling per-user timer. Every account covered by the claim shares that deadline. If you claim an additional domain later, that claim gets its own 30-day window (see **[Add a domain after you've started a claim](#h_d7ccebb0ac)** below). During this window, each person on the domain can sign in and choose how to migrate: - **Merge and join:** Bring existing chats, projects, files, and memory into a new account within your Enterprise workspace. See the full list: **[What moves when you migrate](https://support.claude.com/en/articles/9267400-move-your-personal-claude-account-to-a-team-or-enterprise-organization#h_4e63ef6e87)**. - **Join fresh:** Start with a clean Enterprise account. ### What happens at the deadline - Any remaining personal accounts that haven’t been migrated are deactivated. - Paid subscriptions (Pro and Max) are automatically canceled with a prorated refund. Any usage credits remaining on the account will also be refunded. - Once all accounts are migrated or deactivated, no personal accounts exist on your domain. - People who don’t choose before the deadline are given a fresh Enterprise account by default and their data will be emailed to them, but their personal account will not be accessible. New accounts created on the domain after domain capture is enabled go directly through SSO and your Enterprise workspace—no personal account is created. ### Add a domain after you've started a claim Each claim covers the domains that were verified on your organization at the moment you initiated it. A domain you verify after starting a claim won't be added to the claim in progress, and accounts associated with that domain aren't notified or migrated as part of it. To migrate accounts on a domain you verified later: 1. Wait for the current claim's 30-day window to end. Only one claim can be in progress at a time. 2. Verify the new domain if you haven't already. See **[Set up single sign-on (SSO)](https://support.claude.com/en/articles/13132885-set-up-single-sign-on-sso)**. 3. Review the accounts on the new domain, then initiate a new claim. This claim has its own 30-day window, and the accounts on the new domain receive the same email and in-product notifications. **Note:** If you're onboarding several domains in phases, verify all of them before you initiate a claim when possible. That way, one claim and one deadline cover every account. Otherwise, each phase needs its own claim, and each claim has to finish its 30-day window before the next one can start. ## What’s not supported - Migrating data into organizations with HIPAA readiness or customer-managed encryption keys (CMEK) turned on. You can still claim your domain, and people on it are notified as usual, but they can only join fresh. Nothing from their personal accounts moves over. Learn more about **[HIPAA-ready Enterprise plans](https://support.claude.com/en/articles/13296973)** and **[customer-managed encryption keys](https://support.claude.com/en/articles/15505325)**. - Claiming Team plan accounts. Only individual accounts (Free, Pro, Max) can be claimed. - Setting a custom migration deadline. The window is always 30 days. - Canceling App Store subscriptions. People who purchased Pro or Max through the Apple App Store need to cancel their subscription themselves through their Apple ID settings. For details, see **[Respond to an Enterprise domain claim on your Claude account](https://support.claude.com/en/articles/14625626)**. ## SSO and provisioning sequencing Domain claiming integrates with your existing SSO and provisioning setup: - **If SSO is already enforced:** After an organization admin enables a claim for all personal Claude accounts using their verified domain, users will see a banner upon logging into their personal accounts and receive an email telling them to migrate. If a user is not added to your organization’s IdP, they will be locked out, so admins should ensure any users who need access are added before enabling a claim. - **SCIM and JIT:** If SCIM is enabled, provisioned accounts are linked to migrated accounts by email match. Don’t enable SCIM and JIT provisioning simultaneously—SCIM takes precedence if both are active. **Important:** To prevent lockouts, make sure all affected users are in your IdP before the migration deadline. Anyone not in the IdP won’t be able to sign in to the Enterprise workspace, and their personal account will be deactivated at the 30-day deadline. Your IT team will need to add them to the IdP. ------------------------------------------------------------------------ ## Frequently asked questions ### What happens if my organization doesn’t have enough seats available for migrated users? If you purchased your Enterprise plan directly through Anthropic, you'll see an error message in organization settings prompting you to **[buy more seats](https://support.claude.com/en/articles/13393991-purchase-and-manage-seats-on-enterprise-plans)**. If you purchased your Enterprise plan through the AWS Marketplace, migrated users will see a message asking them to contact their admin when they try to log in after the migration. --- ## claude-design-admin-guide-for-team-and-enterprise-plans-35227de5bf.md # Claude Design admin guide for Team and Enterprise plans Copy for LLM Claude Design lets your team create on-brand designs, prototypes, and interactive microsites through conversation with Claude. Presentations now have their own tool, Claude Slides. Claude Design is available in beta on Pro, Max, Team, and Enterprise plans. It's on by default on Team plans. On Enterprise plans, it's off by default until an owner turns it on. **Note:** Settings for artifacts, templates (including **Design**), design systems, and sharing live in one place now. Learn more in the **[Artifacts admin guide for Team and Enterprise plans](https://support.claude.com/en/articles/16994751)**. This guide covers standalone Claude Design at **claude.ai/design** and how to roll out Claude Design with a design system in place. Claude Design works best when a **design system** is set up for your organization first. This ensures every project your team creates stays true to your brand, typography, color palette, and component patterns. This guide walks you through enabling Claude Design, setting up the right foundation, and rolling it out to your team. **[Create an artifact with Claude](https://claude.ai/artifacts)** ------------------------------------------------------------------------ ## Turn on Claude Design for your organization Your team can use Claude Design in two places, and each has its own setting. Turning one on doesn't turn on the other. ### Claude Design in conversations and the Artifacts tab To turn on the **Design** template, see the instructions in **[Artifacts admin guide for Team and Enterprise plans](https://support.claude.com/en/articles/16994751)**. ### Standalone Claude Design at claude.ai/design 1. Go to **[Organization settings \> Claude Design](https://claude.ai/admin-settings/claude-design)**. 2. Find the **Enable for your organization** toggle under **Claude Design \[standalone\]** and switch it on. On Enterprise plans, you can control access to standalone Claude Design with **[custom roles](https://support.claude.com/en/articles/13930452)**. Before you turn on broad access, read through the rollout approach below. Turning on Claude Design without a design system in place means your team gets functional but generic output. ------------------------------------------------------------------------ ## The design system: why it comes first The single most important thing you can do before rolling out Claude Design is have an experienced designer set up your organization’s design system. Once in place, every project your team creates automatically reflects your brand. This means your rollout has a natural sequence: design system setup first, then broader access. ### Who should set up the design system For best results, we recommend pulling in designers across both brand and product design. Together they can ensure the design system covers both brand identity and product UI patterns. ### What they’ll do 1. Create your organization in Claude Design (see **[Set up your design system in Claude Design](https://support.claude.com/en/articles/14604397-set-up-your-design-system-in-claude-design)**). 2. Complete the onboarding flow. 3. Upload brand assets (codebases, slide decks, or other design references). 4. Validate that Claude generates designs consistent with your brand. Any member with Claude Design access can create and edit design systems. On the Enterprise plan, you can restrict who can publish design systems, set the organization default, and delete design systems. ------------------------------------------------------------------------ ## Recommended rollout phases A phased rollout lets you validate your design system and build internal expertise before broad adoption. On Enterprise plans, you can phase access to standalone Claude Design using **[custom roles](https://support.claude.com/en/articles/13930452-manage-custom-roles-on-enterprise-plans)**. You can phase access to Claude Design in conversations and the Artifacts tab the same way, with the Design capability (under **Artifacts**). ### Phase 1: Design system setup - **Who:** 2–4 trusted designers and design leads across brand and product design. - **Goal:** Create and validate your organization’s design system, including product templates everyone can use as a starting point. - **Checkpoint:** Review generated output for brand consistency before proceeding. ### Phase 2: Design team onboarding - **Who:** Full design team. - **Goal:** Build familiarity with Claude Design; stress-test the design system across real projects. - **Checkpoint:** Gather feedback on design quality and refine the design system if needed. ### Phase 3: Product and UX onboarding - **Who:** Product managers, UX researchers, and adjacent functions. - **Goal:** Enable faster prototyping and design collaboration beyond the design team. - **Checkpoint:** Observe usage throughout the organization and gather feedback on usability. ### Phase 4: Broader organization - **Who:** Entire organization or specific departments. - **Goal:** Make design creation available widely while maintaining brand consistency. - **Checkpoint:** Observe usage throughout the organization and gather feedback on usability. ### Rollout tips - Announce each phase clearly so people know when their turn is coming. - Consider running a short training session or office hours during early phases. - Establish a feedback channel for design system improvements. - Share examples of creative uses of Claude Design internally to help foster creativity. ------------------------------------------------------------------------ ## What your team can do with Claude Design Once set up, your team can use Claude Design to: - **Create prototypes and mockups:** Describe a UI and get a working interactive prototype. - **Build presentations with Claude Slides:** Make on-brand decks from notes, reports, or an existing conversation, and export them to PowerPoint or PDF. Claude Slides has its own setting in **[Organization settings \> Artifacts](https://claude.ai/admin-settings/artifacts)**. - **Design microsites and landing pages:** Create polished single-page sites. - **Iterate with inline comments:** Annotate designs directly on the canvas and ask Claude to implement changes. - **Hand off to engineering:** Export design intent for use with Claude Code or your existing development workflow. ------------------------------------------------------------------------ ## Preview sandbox isolation Claude Design project previews run inside a sandboxed iframe on a separate content domain that Anthropic operates. These sandboxed iframes help each project preview stay in its own space, separate from others. The code in a preview can't reach your Claude account, your login, or the editor. ​ Access to a preview is controlled by signed tokens—short-lived passes that prove someone's allowed in. Claude re-checks these tokens against your sharing permissions every time someone opens the preview, so when you remove someone's access, they're locked out right away. ------------------------------------------------------------------------ ## Frequently asked questions ### Do all team members need to upload brand assets? No. Once a designer sets up your organization’s design system, all projects created within that organization automatically use it. Team members just start creating. ### Can we have multiple design systems for different brands or sub-teams? Yes. Organizations can have multiple design systems. ### What happens if someone starts using Claude Design before the design system is set up? They’ll get functional designs, but the designs won’t reflect your brand. We strongly recommend completing design system setup first for the best team experience. ### How many users can we onboard at once? There are no strict limits, but we recommend the phased approach outlined above to ensure quality and successful adoption across your organization. ### Can we export or archive generated designs? Claude Design currently supports export to HTML bundles, PPTX, and PDF, hand-off to Claude Code, and sending designs to the partner tools listed in **[Get started with Claude Design](https://support.claude.com/en/articles/14604416)**. --- ## creating-a-new-account-after-deletion-17141e2820.md # Creating a new account after deletion March 16, 2026 Copy for LLM If you receive the following message, "The email you used is either associated with an existing account or an account that was active within the last 30 days," this is due to having a deleted account with multiple attempts to create new accounts with the same email address. If your previous account was disabled for [Usage Policy violations](https://www.anthropic.com/legal/aup), you won't be able to create new accounts with the email address associated with the disabled account, regardless of waiting period. --- ## creating-a-new-account-after-deletion.md 3. Creating a new account after deletion # Creating a new account after deletion If you receive the following message, "The email you used is either associated with an existing account or an account that was active within the last 30 days," this is due to having a deleted account with multiple attempts to create new accounts with the same email address. If your previous account was disabled for [Usage Policy violations](https://www.anthropic.com/legal/aup), you won't be able to create new accounts with the email address associated with the disabled account, regardless of waiting period. --- ## creating-and-managing-workspaces.md 4. Creating and managing Workspaces in the Claude Console # Creating and managing Workspaces in the Claude Console This guide will walk you through the process of creating, editing, and managing Workspaces in your Claude Console organization. ## What are Workspaces? Workspaces are collaborative spaces within Console organizations where teams can separate API resources by use case. ## How to create a new Workspace **Note:** Only Organization Admins can create new Workspaces. 1. Log in to your [Claude Console account](https://platform.claude.com/login). 2. Navigate to the **Workspaces** section by clicking on "Settings" in the top level menu and selecting “Workspaces” from the left side bar ([Settings \> Workspaces](https://platform.claude.com/settings/workspaces)). 3. Click the "Add Workspace" button near the top right of the page. 4. In the modal that appears, enter a name for your new Workspace, and select a color assignment. This color assignment will be used to help visually identify your workspace in the Claude Console. 5. Click "Create" to finalize the new Workspace. Your new Workspace will now appear in the list of Workspaces. **Note:** You are limited to 100 workspaces per organization. ## Editing Workspace Settings 1. From the **Workspaces** list, click on the ellipsis next to the Workspace you want to edit. 2. Select “Edit details." 3. You can modify the following settings: - Workspace Name - Color 4. After making your changes, click "Save" to apply them. **Note:** The default Workspace is not editable and cannot be removed. ## Adding members to a Workspace **Note:** You must add members to your Console organization by following [these instructions](https://support.claude.com/en/articles/13443764-inviting-members-to-the-claude-console) before you can add them to a Workspace. 1. Navigate to the desired Workspace's details page by clicking on it from the Workspaces list. 2. Click on the “Members” tab. 3. Click on “Add to Workspace” near the top right of the page. 4. Choose the individual you’d like to add from the list of your organization’s members. 5. Assign a Workspace role for this member. 6. Confirm your selections by clicking “Add to Workspace." **Note:** Organization Admins are automatically added as Workspace Admin to every Workspace. Organization Billing role holders are automatically granted ability to see cost, usage, and limit values for all Workspaces, but can be upgraded to the Organization Admin role. ## Deleting members from a Workspace Click the trash can icon next to the member to remove them from your Workspace. **Note:** Organization members with Admin and Billing roles are automatically granted permissions on all Workspaces and cannot be removed from Workspaces. ## Managing API Keys in a Workspace 1. Navigate to the desired Workspace's details page by clicking on it from the **Workspaces** list. 2. Click on the "API Keys" tab. 3. To create a new API key for this Workspace: - Click "Create Key" - Give the key a descriptive name - Click "Create Key" 4. To revoke an existing API key: - Find the key in the list - Click the ellipsis next to it - Select "Disable API Key" or “Delete API Key” - **Note:** Deleting an API key is a permanent action and cannot be undone. - Confirm the action **Note:** API keys are tied to the Workspace they're created in and cannot be moved between Workspaces. ## Setting Workspace Rate Limits 1. Navigate to the desired Workspace's details page by clicking on it from the **Workspaces** list. 2. Click on the "Limits" tab. 3. Set a limit for each model tier and limit type by clicking on the pencil icon next to each option. 4. Workspace Spend Limits can be reset to the organization rate limit by clicking the “Refresh” icon next to the rate limit you previously set for the Workspace. **Note:** Anthropic always evaluates all applicable limiters -- at the Workspace and Organization level -- for every request. In other words, if the Workspace limits are unset, Organization limits still apply. ## Setting Workspace Spend Limits or Notifications 1. Navigate to the desired Workspace's details page by clicking on it from the **Workspaces** list. 2. Click on the "Limits" tab. 3. Choose one of the following: - Select “Change Limit” to set a specific spend limit for this Workspace. - **Note:** You can only set a spend limit that is lower than your organization’s limit. If unset, your spend limit defaults to the organization’s limit. - Select “Add notification” to set up an email notification when the Workspace spend reaches a specific amount. ## Viewing Workspace Usage and Costs 1. Navigate to the [Usage or Cost Reports](https://support.claude.com/en/articles/9534590-cost-and-usage-reporting-in-the-claude-console). 2. Choose to view by an individual Workspace, or by “All Workspaces”. ## Archiving a Workspace If you no longer need a Workspace but want to retain its historical data: 1. Navigate to the **Workspaces** page. 2. Click the ellipsis next to the Workspace you would like to archive. 3. Confirm that you want to archive the Workspace. **Note:** Archiving a Workspace will archive all API keys in the Workspace. This action cannot be undone. ## Managing the Default Workspace Every organization has a default Workspace that cannot be renamed, archived, or deleted. To view API keys associated with the default Workspace: 1. Navigate to the **Workspaces** list. 2. Click on "Default" in the list. **Note:** You can view your default Workspace’s limits from the [Limits settings](https://platform.claude.com/settings/limits). --- ## delete-your-claude-account-b6ab085412.md # Delete your Claude account August 19, 2026 Copy for LLM This article shows you how to permanently delete your account on the web and in the Claude mobile apps, and explains what happens to your data when you do. **Important:** Deleting your account is permanent. You'll lose access to your conversations, projects, and other saved data, and you can't recover the account afterward. If you want to keep your data, export it on web or desktop before you delete. Learn more about **[exporting your Claude data](https://support.claude.com/en/articles/9450526-how-can-i-export-my-claude-data)**. ## Before you delete a paid account If you're on a Pro or Max plan: 1. Cancel your subscription from your **[Billing settings](https://claude.ai/settings/billing)**. 2. Wait until the end of your current subscription period. 3. Once the subscription lapses, delete your account using the steps below. For detailed cancellation instructions, including for Claude for iOS and Android, see **[Cancel your Pro or Max subscription](https://support.claude.com/en/articles/8325617)**. ## Delete your account on the web 1. Go to **[claude.ai](https://claude.ai/)** and click your initials or name in the lower left corner. 2. Select "Settings," or navigate directly to **[Settings \> Account](https://claude.ai/settings/account)**. 3. Click "Delete account" and follow the prompts. ## Delete your account on Claude for iOS These steps apply to Claude for iOS, listed on the App Store as Claude by Anthropic. 1. Open the Claude app and tap "Settings." 2. Find the **Account** section and tap "Profile." 3. Tap "Delete account." 4. Tap "Delete" to confirm. ## Delete your account on Claude for Android These steps apply to Claude for Android, listed on Google Play as Claude by Anthropic. 1. Open the Claude app and tap the menu button in the upper left corner. 2. Tap your initials in the lower left corner. 3. Tap "Profile." 4. Under **Account Actions**, tap "Delete Account." 5. Tap "I Understand" to confirm. ## What happens when you delete your account When you delete your account, you’ll no longer have access to your conversations, projects, and account information. Learn more about **[how long Anthropic stores your data](https://privacy.claude.com/en/articles/10023548-how-long-do-you-store-my-data)**. ## When you need to contact support In some scenarios you'll need to contact our team to delete your account. If this applies to you, it'll be noted in your account settings. Learn more about **[how to get support](https://support.claude.com/en/articles/9015913-how-to-get-support)**. If you have multiple accounts associated with the same email address, you'll need to specify which accounts you want to delete when you contact us. --- ## designate-support-contacts-for-human-support-b3b303b2e2.md # Designate support contacts for human support August 6, 2026 Copy for LLM Choose which members of your organization can open tickets with Anthropic's human support team by designating support contacts. Users who aren't configured as support contacts get help from AI support, which can answer many common questions instantly. Available on the Enterprise plan, and configurable by Primary Owners and Owners. ## How support routing works When support contacts are turned on, members of designated groups can reach human support. Everyone else in your organization gets AI support, which handles most questions instantly. When support contacts are turned off, everyone in your organization gets AI support and no one is routed to a human. You can also extend human support to all Admins and Owners by checking **Always include Admins and Owners** when configuring support contacts. ## Default settings at launch When the support contacts setting becomes available, the feature is turned on and **Always include Admins and Owners** is checked. This preserves existing behavior: your Admins and Owners keep human support access without any configuration work, and other users get AI support unless you add them to a designated group. To grant human support access to additional users (such as a central IT team), designate them in a group through organization settings. To remove human support access for Admins and Owners, uncheck **Always include Admins and Owners**. ## Configure support contacts Before configuring support contacts, make sure the groups you want to designate already exist in organization settings. Groups can be synced from your identity provider through SCIM or created manually. For more information, see **[Manage groups and group spend limits on Enterprise plans](https://support.claude.com/en/articles/13799932-manage-groups-and-group-spend-limits-on-enterprise-plans)**. To configure support contacts: 1. Navigate to **[Organization settings \> Organization and access](https://claude.ai/admin-settings/organization)**. 2. Find the **Support contacts** section and toggle the feature on. 3. Select the groups whose members should receive human support. 4. Check or uncheck **Always include Admins and Owners** to control whether your organization’s Admins and Owners can reach human support. 5. Save your changes. To stop routing anyone to human support, turn the **Support contacts** toggle off. All users in your organization will receive AI support only. ## When changes take effect The **Support contacts** setting will be available in organization settings starting on June 1, 2026. Settings configured between June 1 and June 8 don't affect support routing during this window. Organization settings will show a notice that changes are pending until the feature takes effect. On June 8, 2026, this setting will take effect for all Enterprise plan organizations. After this date, users who aren't designated as support contacts can only access AI support. --- ## designated-point-of-contact-for-users-in-the-eu-629e9847a6.md # Designated point of contact for users in the EU May 26, 2026 Copy for LLM Users in the EU can open a support inquiry from this page via the chat tool, which serves as our single point of contact for EU users under the DSA. Follow these **[instructions](https://support.claude.com/en/articles/9015913-how-to-get-support)** to get support. ## European Union monthly active recipients In accordance with our obligations under Article 24(2) of the DSA, Anthropic publishes information on the average ‘monthly active recipients’ of our online services in the European Union, calculated over a six-month period. ​ Anthropic has calculated its average monthly active recipients in the EU for the six-month period ending 31 October 2025, and has concluded that it falls well below the 45 million threshold set out in Article 33(1) of the DSA. ​ Anthropic will continue to monitor the number of average monthly active recipients of its services in the EU and will publish updated information at least every 6 months. --- ## designated-point-of-contact-for-users-in-the-eu.md 3. Designated Point of Contact for Users in the EU # Designated Point of Contact for Users in the EU Users in the EU can open a support inquiry from this page via the chat tool, which serves as our single point of contact for EU users under the DSA. Follow these [instructions](https://support.anthropic.com/en/articles/9015913-how-to-get-support) to get support. ## **European Union Monthly Active Recipients** In accordance with our obligations under Article 24(2) of the DSA, Anthropic publishes information on the average ‘monthly active recipients’ of our online services in the European Union, calculated over a six-month period.\ \ Anthropic has calculated its average monthly active recipients in the EU for the six-month period ending 31 October 2025, and has concluded that it falls well below the 45 million threshold set out in Article 33(1) of the DSA.\ \ Anthropic will continue to monitor the number of average monthly active recipients of its services in the EU and will publish updated information at least every 6 months. --- ## faqs-on-using-claude-for-education-at-your-university-69cf1138d4.md # Use Claude for Education at your university Copy for LLM This guide helps you use Claude for Education through your university-sponsored account. Find resources and answers to frequently asked questions about getting started, optimizing usage, and troubleshooting issues. ------------------------------------------------------------------------ ## What features are included in my university-sponsored education plan? Your university-sponsored Claude for Education account includes: - **Enhanced context window:** Upload hundreds of pages of text for analyzing lengthy academic papers, research documents, and datasets. - **Advanced models:** Access to the newest, most advanced Claude models. - **Projects feature:** Create and organize multiple related conversations with shared knowledge bases. - **Increased usage limits:** More messages per day compared to individual plans. - **Priority access:** Priority access during high-traffic periods. - **File uploads:** Analyze various document types including PDFs, DOCX, CSV, TXT, HTML, and more. **Note:** Your university may have customized certain features or applied specific policies. Check with your university's IT department for institution-specific guidelines. ------------------------------------------------------------------------ ## What can I use Claude for as a student? Claude can be a valuable assistant for numerous academic tasks: #### Research assistance - Generate research questions based on your topic - Help analyze academic papers - Find gaps in your literature review - Suggest methodological approaches #### Writing support - Outline papers and essays - Provide feedback on drafts - Help with citations and bibliographies - Suggest ways to improve clarity and structure #### Study aid - Create practice questions on course material - Explain complex concepts in simpler terms - Generate study guides and flashcards - Provide step-by-step explanations for problem-solving #### Productivity - Summarize notes - Create to-do lists and study schedules - Draft emails to professors or classmates - Generate presentation outlines #### Creative work - Brainstorm ideas for projects - Help develop characters or storylines - Provide feedback on creative writing - Generate metaphors or analogies for concepts **Important:** Follow your university's academic integrity policies when using Claude. While Claude can help you understand material and improve your work, it should not be used to complete assignments that you're expected to do independently. ------------------------------------------------------------------------ ## How do I access Claude on different devices? You can access Claude through multiple platforms to suit your needs: ### Web browser - Visit claude.ai on any web browser. - Sign in with your university email. - Works on both desktop and mobile browsers. ### Desktop application - Download Claude for Desktop for macOS or Windows. - For macOS: Requires macOS 11 (Big Sur) or higher. - For Windows: Requires Windows 10 or higher. - Install by visiting the **[Claude downloads page](https://claude.ai/download)** and following the installation instructions. - Launch from your Applications folder (Mac) or Start menu (Windows). ### Mobile applications - **iOS**: **[Download from the App Store](https://apps.apple.com/us/app/claude-by-anthropic/id6473753684)** (requires iOS 18.0 or later). - **Android**: **[Download from Google Play Store](https://play.google.com/store/apps/details?id=com.anthropic.claude)** (requires Android 8.0 Oreo or later). - Sign in with the same university account you use on the web version. - See our **[Claude Mobile apps section](https://support.claude.com/en/collections/9387080-claude-mobile-apps)** for more information. All platforms synchronize your conversations, allowing you to start on one device and continue on another. Mobile apps offer additional features like photo analysis and voice dictation. ------------------------------------------------------------------------ ## How to use Claude Review the following resources to help you get the most out of your usage with Claude: - **[Upload files to Claude](https://support.claude.com/en/articles/8241126)** - **[What are projects?](https://support.claude.com/en/articles/9517075)** - **[How can I create and manage projects?](https://support.claude.com/en/articles/9519177)** - **[Manage project visibility and sharing](https://support.claude.com/en/articles/9519189)** - **[What are artifacts and how do I use them?](https://support.claude.com/en/articles/9487310)** - **[Usage limit best practices](https://support.claude.com/en/articles/9797557)** - **[Create and edit files with Claude](https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude)** - **[Use connectors to extend Claude's capabilities](https://support.claude.com/en/articles/11176164)** - **[Use Google Workspace connectors](https://support.claude.com/en/articles/10166901)** - **[Understanding Claude's personalization features](https://support.claude.com/en/articles/10185728)** - **[Enable and use web search](https://support.claude.com/en/articles/10684626)** - **[How to use Claude in your preferred language](https://support.claude.com/en/articles/10769299)** - **[When should I use web search, extended thinking, and Research?](https://support.claude.com/en/articles/11095361)** ------------------------------------------------------------------------ ## Troubleshooting ### I'm struggling to log in with SSO Your SSO configuration is managed by the Primary Owner or Owner on your account. Contact your university's dedicated support channel to troubleshoot SSO/login issues. ### I'm seeing a warning message about remaining messages Claude has a usage limit that varies based on message length, file attachments, and conversation length. You'll receive warning messages before reaching the limit. When you see the first warning, consider following these **[usage tips](https://support.claude.com/en/articles/9797557)**. ### I'm seeing an error message about length limit This appears when your prompt exceeds Claude's available context window. When this happens, either: - Shorten your prompt/attachments - Start a new conversation ### I already have a Claude account using my university email When you log in, you can select between your previous account and the new university-sponsored account. You can't migrate data between accounts, but you can **[export data](https://support.claude.com/en/articles/9450526)** from your existing account and upload the conversation data (JSON format) to your new account. ------------------------------------------------------------------------ ## Privacy Review these resources and visit the **[Privacy Center](https://privacy.claude.com/en/)** for information about privacy, data retention, and data handling: - **[Is my data used for model training?](https://privacy.claude.com/en/articles/7996868)** - **[How long do you store my organization’s data?](https://privacy.claude.com/en/articles/7996866)** - **[Can you delete data that I sent via Claude?](https://support.claude.com/en/articles/9796617)** - **[How can I delete or rename a conversation?](https://privacy.claude.com/en/articles/11117329)** - **[Who owns and manages the data of my university account?](https://support.claude.com/en/articles/9265372)** --- ## get-started-with-claude-design-c1ae6368f5.md # Get started with Claude Design Copy for LLM **[Claude Design](https://claude.com/product/design)** lets you create designs, interactive prototypes, one-pagers, and other visual work by chatting with Claude. It's one of the templates you can start an artifact from, so you can use it in any chat, in Claude Code, and from the **Artifacts** tab, with on-canvas editing and your design system included. This guide walks you through creating your first design, iterating on it, and getting the most out of it. Learn more about **[what artifacts are and how to use them](https://support.claude.com/en/articles/9487310)**. Claude Design is available in beta on Pro, Max, Team, and Enterprise plans. It's on by default on Pro, Max, and Team plans. On Enterprise plans, it's off by default until an owner turns it on in **[Organization settings \> Artifacts](https://claude.ai/admin-settings/artifacts)**. The standalone Claude Design experience at claude.ai/design keeps working and has its own separate setting. This guide assumes your organization’s design system has already been set up, so everything you create will automatically use your brand’s colors, typography, and component patterns. If you’re a design lead who needs to set up or modify the design system itself, see **[Set up your design system in Claude Design](https://support.claude.com/en/articles/14604397-set-up-your-design-system-in-claude-design)**. **[Create an artifact with Claude](https://claude.ai/artifacts)** ## Where you can use Claude Design - **In a conversation:** Ask Claude for a design, like "Make a one-pager from this proposal" or "Mock up the onboarding flow we just discussed." Claude builds it beside your conversation, and you refine it there. You can also select **Output** \> **Design** in the message box. - **In the Artifacts tab:** Go to the **Artifacts** tab and pick a Design template. - **In Claude Code:** Ask Claude to turn your idea into a design, or use /design to create, edit, and sync designs, on desktop or in the terminal. - **In the Claude app for iOS and Android:** Ask for a design in any conversation and check back later for the result, then view it full screen in the **Artifacts** tab. To start from a template, edit on the canvas, or change sharing settings, use Claude on web or desktop. - **At claude.ai/design:** The standalone experience keeps working, and your existing projects stay where they are. ------------------------------------------------------------------------ ## How Claude Design works Claude Design pairs a conversation with a canvas. You describe what you want, and Claude generates a working design on the canvas beside the conversation. From there, you iterate—refining through conversation, inline comments, and directly on the canvas until it’s right. The typical flow is: 1. Start a design from a conversation, the Artifacts tab, or claude.ai/design. 2. Attach or import the design system you want Claude to build with. 3. Add any relevant context (screenshots, a codebase). 4. Describe what you want to build. 5. Review what Claude generates on the canvas. 6. Refine through chat, edit directly on the canvas, or leave inline comments. 7. Export or share when you’re happy with the result. ### Move between Claude Design and Claude Code You can move between working in Claude Design and Claude Code while keeping your work synced. Use /design-sync to pull in your design system, so everything you build in Claude Design starts from your existing components. When a design is ready to become software, you can hand it off to Claude Code, which continues from your existing work instead of starting over from a screenshot. From Claude Code, use /design to import a design into your codebase, export your code as a live prototype, or let Claude build the whole thing from start to finish. ------------------------------------------------------------------------ ## Create a new project When you create a project, it automatically inherits your organization’s design system. You don’t need to upload brand assets or configure anything—your brand colors, fonts, and components are already in place. ### Attach or import your design system Bring in one or several design systems from a GitHub repo, design files, raw uploads, or your local codebase using the /design-sync command in Claude Code. Claude builds with your real design system components, checks its own output against your design system, and makes corrections before you see them. On Enterprise plans, admins can reserve publishing, setting the default, and deleting design systems for specific users. Learn more in the **[Artifacts admin guide for Team and Enterprise plans](https://support.claude.com/en/articles/16994751)**. ### Bring over a design system from claude.ai/design Design systems you made at claude.ai/design can move over, so Claude can use them in any chat, including in Claude Code. Learn more about **[setting up your design system](https://support.claude.com/en/articles/14604397)**. ### Add context to your project The more context you give Claude, the better your output will be. You can attach reference material at any point during a project. - **Screenshots, images, or existing assets:** Upload screenshots of existing designs, competitor products, wireframes, or visual inspiration. You can also attach an existing slide deck or document with a design style you want to replicate. Useful for “make it look like this” requests. - **Codebases and existing design files:** Link a code repository so Claude understands your existing components, architecture, and styling patterns. This makes prototypes more production-ready from the start. Import also supports multiple ways to upload existing product design work. ### Write effective prompts You don’t need to be a designer to get great results. Be specific about what you’re building, who it’s for, and what matters most. A good prompt includes the **goal** (what you’re building), the **layout** (how things should be arranged), the **content** (what information to display), and the **audience** (who will use it). Claude will also ask clarifying questions if it needs more information. Here are some examples of prompts that work well: - “Create a dashboard showing monthly revenue with filters for region and product line.” - “Design a mobile app onboarding flow with 4 screens that walks users through our core features.” - “Build a landing page for our new API product with a hero section, code examples, and pricing.” - “Create a form for collecting customer feedback with conditional questions based on category.” - “Design an internal tool for our ops team to review and approve content submissions.” ------------------------------------------------------------------------ ## Refine your design The first generation is a starting point. The real value comes from iterating. ### Using chat Chat is best for broad changes that affect the overall design: - “Make the color scheme darker and more minimal.” - “Rearrange the dashboard so metrics are in the top row and the chart is below.” - “Add a settings panel on the right side.” - “Show me 2–3 alternative layouts for this page.” You can also ask Claude to explain its design decisions, suggest improvements, or review the design for accessibility. ### Using inline comments Inline comments let you click directly on a specific part of the canvas and request a targeted change. This is faster than describing the location in chat. Examples of good inline comments: - “Make this button padding larger.” - “Change this to a dropdown instead of radio buttons.” - “Use the primary brand color here.” - “Make this section collapsible.” **Note:** If your comments aren’t being picked up, paste the feedback directly into the chat instead. This is a known workaround for an intermittent issue where comments can disappear before Claude reads them. ### Edit directly on the canvas Use rich layout controls for quick visual and aesthetic shifts, specifically to drag, resize, and align elements directly. ### When to use chat vs. comments vs. edit directly Use **comments** for targeted, component-level changes (“fix this button,” “adjust this spacing”). Use **chat** for structural changes, new sections, or anything that requires explanation or context. **Edit directly** for quick visual and aesthetic changes. ## Manage versions and revisions If you want to explore a different direction without losing your current work, tell Claude: “Save what we have and try a completely different approach.” Claude will save your current project and confirm where it’s saved, so you can reference earlier iterations in the conversation easily. ------------------------------------------------------------------------ ## Export and share Once your design is ready, you can share it with colleagues or export it for use elsewhere. The right format depends on your use case—whether you’re getting stakeholder feedback, handing off to engineering, or presenting to a group. Use the “Export” button in the upper right corner when viewing your project to choose from the following export formats. - Download as .zip - Export as PDF - Export as PPTX - Export to Google Slides (available only at claude.ai/design) - Export as standalone HTML - Send to the tools you already use: Adobe Experience Manager, Adobe for Creativity, Adobe Journey Optimizer, Base44, Canva, Gamma, HubSpot, Hyperframes, Lovable, Miro, Netlify, Replit, v0, Vercel, and Wix - Handoff to Claude Code - Send to local coding agent - Send to Claude Code Web Designs start private to you. To share one, click "Share" and choose who can open it and what they can do. People you share a design with can view, comment on, or edit it. Learn more about **[sharing artifacts](https://support.claude.com/en/articles/9547008)**. ------------------------------------------------------------------------ ## Usage and pricing Claude Design counts toward the same usage limits as the rest of Claude. Design activity draws from the same pool as the rest of your work with Claude, including Claude Code, so there's no separate Claude Design allowance to track. Complex projects with large codebases or many iterations consume more usage. If you reach your usage limits, Claude Design is unavailable until your limits reset. If you've enabled usage credits, you can keep working after reaching your included limits. Learn more about **[how usage and length limits work](https://support.claude.com/en/articles/11647753-how-do-usage-and-length-limits-work)**. **Note:** Claude Design previously had its own weekly allowance, separate from your other usage limits. All Claude Design activity now counts toward your plan's shared limits. ------------------------------------------------------------------------ ## Tips for best results - **Import a complete design system.** Import a complete design system that includes your styles, fonts, and components. - **Start simple, then layer in complexity.** Begin with the core layout and content, then add interactions, edge cases, and polish. Claude responds well to incremental requests. - **Be specific in your feedback.** “This doesn’t look right” is hard to act on. “Tighten the spacing between form fields to 8px” gives Claude exactly what it needs. - **Reference your design system.** If you know a component exists in your brand’s system, mention it by name: “Use the Primary Button component” or “Apply the Card layout pattern.” - **Think about responsiveness early.** Mention whether your design needs to work on mobile, tablet, and desktop, or just one of those. - **Ask for variations.** If you’re unsure about a direction, ask Claude to show you 2–3 options. Comparing alternatives is much faster than guessing. - **Ask Claude for feedback.** Claude can review your design for accessibility, contrast ratios, information hierarchy, and general usability. Treat it as a design collaborator, not just a generator. ------------------------------------------------------------------------ ## Known limitations Claude Design is now available in beta. A few things to be aware of: - **Comment persistence:** Inline comments occasionally don't appear on the page, but you can still see them by opening the comments view. - **Large codebases:** Consider linking very large repositories from Claude Code to avoid lag or browser issues. To sync a design system, use /design-sync from Claude Code. - **Chat errors:** If you hit a "chat upstream error," try starting a new chat tab within the same project. - **Mobile:** In the Claude app for iOS and Android, you can ask for a design and view it in the Artifacts tab. Editing on the canvas and changing sharing settings need Claude on web or desktop. - **Multi-person editing:** Two or more people editing a design project at the same time is still basic and may not work reliably. - **Design system import:** Design system import is only as good as its source. A messy codebase or an incomplete file will show up in the output. - **Version history:** Claude Design doesn't have version history yet. --- ## how-can-i-access-the-personal-information-that-anthropic-has-on-my-account-73c2e23c20.md # How can I access the personal information that Anthropic has on my account? March 16, 2026 Copy for LLM Please refer to our [Privacy Center](https://privacy.anthropic.com/en/articles/9265372-who-owns-and-manages-the-data-of-my-team) for more information about this. --- ## how-can-i-access-the-personal-information-that-anthropic-has-on-my-account.md 4. How can I access the personal information that Anthropic has on my account? # How can I access the personal information that Anthropic has on my account? Please refer to our [Privacy Center](https://privacy.anthropic.com/en/articles/9265372-who-owns-and-manages-the-data-of-my-team) for more information about this. --- ## how-can-i-contact-support-7f984d641d.md # How to get support Copy for LLM This guide explains how to get support for your Claude or Console account. Different support options are available depending on your plan. Support is provided in writing through the support messenger and email. We don't offer phone support. ## Pro and Max plans, Team and Enterprise plan owners, and Console Admins You have full access to: - All help documentation - Fin, our AI support bot - Further assistance from our Product Support team While we don't offer phone or live chat support, our Product Support team will gladly assist you through our support messenger. **Note for Enterprise admins:** Primary Owners and Owners can configure which members of their organization reach human support by designating support contacts. By default, Admins and Owners keep human support access. For configuration details, see **[Designate support contacts for human support](https://support.claude.com/en/articles/15263885)**. ### Seeking support for Claude 1. Log in to your Claude account. 2. Click your initials or name in the lower left corner and select “Get help” from the menu. 3. In the support messenger: - Search help resources - Chat with Fin, our AI support bot 4. Click “Send us a message” to start chatting with Fin. 5. Click "Accept," then select your issue from the available options. 6. Depending on the selected issue, provide additional details when prompted. 7. If your issue requires additional investigation or input from our Product Support team, Fin will pass your inquiry along. The team's reply appears in this same conversation. You'll see it in the messenger and receive a copy by email at the address on your Claude account, so you don't need to keep this window open. ### Seeking support for the Claude API or Console 1. Log in to your **[Console account](https://platform.claude.com)**. 2. Click your initials or name in the lower left corner of the Console and select “Get help” from the menu. 3. This will open a support messenger in the lower right corner of the Console. 4. In the support messenger: - Search help resources - Chat with Fin, our AI support bot 5. Click “Send us a message” to start chatting with Fin. 6. Click "Accept," then select your issue from the available options. 7. Depending on the selected issue, provide additional details when prompted. 8. If your issue requires additional investigation or input from our Product Support team, Fin will pass your inquiry along. The team's reply appears in this same conversation. You'll see it in the messenger and receive a copy by email at the address on your Claude account, so you don't need to keep this window open. ### Seeking support for any account type from the Help Center Users who are logged in to their Claude or Console accounts will be able to click the icon in the lower right corner of any Help Center page to open the support messenger and start chatting with Fin. ## What happens after you message us Support is asynchronous. After your request reaches our team, a specialist investigates and replies in the same conversation. Response times vary by plan and by the severity of the issue. ### Chat and email are the same conversation - Every reply we send appears in the support messenger and is emailed to the address on your Claude account (the account you were signed in with when you started the conversation). - Replying to that email continues the same conversation. You don't need to return to the chat, and you can close the chat window at any time without missing our reply. - Keep one conversation per issue. Opening a second request for the same problem creates a duplicate that has to be re-triaged, which usually slows the answer down. If you haven't heard back, reply in your existing conversation instead. ### Keep colleagues in the loop - A conversation started in the messenger includes only you. To bring in a colleague, such as the affected user or your IT admin, reply to the conversation from the email thread and cc them. Their replies join the same conversation. - If you're reporting an issue on behalf of someone else, include their work email address, any error messages or screenshots, and when the issue started in your first message. This avoids an extra round of questions. - Enterprise organizations can also **[designate support contacts](https://support.claude.com/en/articles/15263885)**. ## Team and Enterprise plan non-owners, and Console non-Admins You’ll chat with Fin, an AI support agent, to help answer your questions. ### Team plans and Console organizations Human specialist support is not directly available for your account seat type. If Fin can't find a resolution and you need to escalate to our human team of specialists, your account's Primary Owner, Owner, or Console Admin can reach out on your behalf. ### Enterprise plans Primary Owners and Owners can designate support contacts: members who can reach human support without holding an Owner role. If you're a designated support contact, you'll have the option to wait for a human when chatting with Fin. Otherwise, Fin will handle your conversation, and if escalation is needed, your account's Primary Owner, Owner, or a designated support contact can reach out on your behalf. For configuration details, see **[Designate support contacts for human support](https://support.claude.com/en/articles/15263885)**. ## Free Claude users Free Claude users have access to: - All help documentation - Fin, our AI support bot - **[Account deletion](https://support.claude.com/en/articles/9028421)** support in cases where self-serve is unavailable To get support: 1. Log in to your Claude.ai account. 2. Click your initials or name in the lower left corner. 3. Select "Get help." 4. Use the support messenger to: - Search help resources. - Chat with Fin, our AI support bot. ## Unable to log in? If you can't access your account, we can still help with: 1. Account deletion 2. Data exports 3. Subscription support To request assistance: 1. Click the message icon in the lower right corner of the Help Center. 2. Start a conversation. 3. Select "I can't login." ## About subscription support If you're a paid subscriber having trouble accessing your account, our team can: - Help locate login information - Process subscription cancellations - Check refund eligibility **Note:** In order to assist with these tasks, we will need to validate details about your account and the payment method used. ## Designated point of contact for users in the EU Users in the EU can find instructions on how to find the single point of contact for users in the EU under the DSA here: **[Designated point of contact for users in the EU](https://support.claude.com/en/articles/11595103-)**. ## Report compliance concerns - UK and Australian users - Users in the UK can find instructions to report non-compliance with UK OSA duties here: **[Report a concern](https://docs.google.com/forms/d/e/1FAIpQLSfdo76veqg3pHZTh_nI14j1DyRO8coz6ocTa9mEuF5DcYgxuA/viewform)**. This includes reporting related to illegal content safety duties, content reporting obligations, freedom of expression and privacy, or the use of proactive technology by Anthropic in breach of Anthropic’s Terms of Service. - Users in Australia can find instructions to report non-compliance with the DIS Standard and information about the role and functions of the eSafety Commissioner here: **[Report a Concern: Australian DIS Standard compliance](https://support.claude.com/en/articles/12335811-report-a-concern-australian-dis-standard-compliance)**. ------------------------------------------------------------------------ ## Frequently asked questions ### Do you offer phone or video support? No. Support is provided in writing through the messenger and email. Enterprise customers who need a live working session can arrange one through their Anthropic account team. ### Can I close the chat window while I wait? Yes. Replies are delivered to the messenger and to your account email, so you won't miss one. ### Which email address will you use to reply? The email address on the Claude account you were signed in with when you started the conversation. ​ ### I haven't heard back. Should I open another request? No. Reply in your existing conversation, in the messenger or by email, and it moves back into the queue with its history intact. ​ ### I have a business-critical outage. Is there a faster path? Organization owners and admins on qualifying Enterprise plans have prioritized options in the messenger. Platform status is always available on **[our status page](https://status.claude.com)**. --- ## how-can-i-contact-support.md # How to get support This guide explains how to get support for your Claude or Console account. Different support options are available depending on your plan. ## Pro and Max plans, Team and Enterprise plan Owners, and Console Admins You have full access to: - All help documentation - Fin, our AI support bot - Further assistance from our Product Support team **Note:** While we don't offer phone or live chat support, our Product Support team will gladly assist you through our support messenger. ### Seeking support for Claude 1. Log in to your Claude account. 2. Click your initials or name in the lower left corner and select “Get help” from the menu. 3. In the support messenger: - Search help resources - Chat with Fin, our AI support bot 4. Click “Send us a message” to start chatting with Fin. 5. Click "Accept," then select your issue from the available options. 6. Depending on the selected issue, provide additional details when prompted. 7. If your issue requires additional investigation or input from our Product Support team, Fin will pass your inquiry along and someone will respond via email. ### Seeking support for the Claude API or Console 1. Log in to your Console account ([platform.claude.com](http://platform.claude.com)). 2. Click your initials or name in the lower left corner of the Console and select “Get help” from the menu. 3. This will open a support messenger in the lower right corner of the Console. 4. In the support messenger: - Search help resources - Chat with Fin, our AI support bot 5. Click “Send us a message” to start chatting with Fin. 6. Click "Accept," then select your issue from the available options. 7. Depending on the selected issue, provide additional details when prompted. 8. If your issue requires additional investigation or input from our Product Support team, Fin will pass your inquiry along and someone will respond via email. ### Seeking support for any account type from the Help Center Users who are logged in to their Claude or Console accounts will be able to click the icon in the lower right corner of any Help Center page to open the support messenger and start chatting with Fin. **Important:** For Console users, this applies specifically to those logged in via [platform.claude.com](http://platform.claude.com). If you’re logged in via [console.anthropic.com](http://console.anthropic.com), you will be prompted to visit [platform.claude.com](http://platform.claude.com) to authenticate before sending a message in the Help Center support messenger. ## Team and Enterprise plan non-Owners, and Console non-Admins You’ll chat with Fin, an AI support agent, to help answer your questions. Human specialist support is not directly available for your account seat type. If Fin can't find a resolution and you need to escalate to our human team of specialists, your account's Primary Owner, Owner, or Console Admin can reach out on your behalf. ## Enterprise plan Owners If you are the Primary Owner or Owner of a Claude for Work Enterprise plan, you can also submit a request through the [Enterprise Support form](https://claude.ai/support/enterprise). **Note:** You must be logged in to your Owner account to access this form. ## Free Claude users Free Claude.ai users have access to: - All help documentation - Fin, our AI support bot - [Account deletion](how-can-i-delete-my-claude-account.md) support in cases where self-serve is unavailable To get support: 1. Log in to your Claude.ai account. 2. Click your initials or name in the lower left corner. 3. Select "Get help." 4. Use the support messenger to: - Search help resources. - Chat with Fin, our AI support bot. ## Unable to log in? If you can't access your account, we can still help with: 1. Account deletion 2. Data exports 3. Subscription support To request assistance: 1. Click the message icon in the lower right corner of the Help Center. 2. Start a conversation. 3. Select "I can't login." ## About subscription support If you're a paid subscriber having trouble accessing your account, our team can: - Help locate login information - Process subscription cancellations - Check refund eligibility **Note:** In order to assist with these tasks, we will need to validate details about your account and the payment method used. ## Designated point of contact for users in the EU Users in the EU can find instructions on how to find the single point of contact for users in the EU under the DSA [here](designated-point-of-contact-for-users-in-the-eu.md). ## Report compliance concerns - UK and Australian users - Users in the UK can find instructions to report non-compliance with UK OSA duties [here](https://docs.google.com/forms/d/e/1FAIpQLSfdo76veqg3pHZTh_nI14j1DyRO8coz6ocTa9mEuF5DcYgxuA/viewform?usp=dialog). This includes reporting related to illegal content safety duties, content reporting obligations, freedom of expression and privacy, or the use of proactive technology by Anthropic in breach of Anthropic’s Terms of Service. - Users in Australia can find instructions to report non-compliance with the DIS Standard and information about the role and functions of the eSafety Commissioner [here](../19-Reference/report-a-concern-australian-dis-standard-compliance.md). --- ## how-can-i-delete-my-claude-account-71ba175b00.md # Delete your Claude account August 19, 2026 Copy for LLM This article shows you how to permanently delete your account on the web and in the Claude mobile apps, and explains what happens to your data when you do. **Important:** Deleting your account is permanent. You'll lose access to your conversations, projects, and other saved data, and you can't recover the account afterward. If you want to keep your data, export it on web or desktop before you delete. Learn more about **[exporting your Claude data](https://support.claude.com/en/articles/9450526-how-can-i-export-my-claude-data)**. ## Before you delete a paid account If you're on a Pro or Max plan: 1. Cancel your subscription from your **[Billing settings](https://claude.ai/settings/billing)**. 2. Wait until the end of your current subscription period. 3. Once the subscription lapses, delete your account using the steps below. For detailed cancellation instructions, including for Claude for iOS and Android, see **[Cancel your Pro or Max subscription](https://support.claude.com/en/articles/8325617)**. ## Delete your account on the web 1. Go to **[claude.ai](https://claude.ai/)** and click your initials or name in the lower left corner. 2. Select "Settings," or navigate directly to **[Settings \> Account](https://claude.ai/settings/account)**. 3. Click "Delete account" and follow the prompts. ## Delete your account on Claude for iOS These steps apply to Claude for iOS, listed on the App Store as Claude by Anthropic. 1. Open the Claude app and tap "Settings." 2. Find the **Account** section and tap "Profile." 3. Tap "Delete account." 4. Tap "Delete" to confirm. ## Delete your account on Claude for Android These steps apply to Claude for Android, listed on Google Play as Claude by Anthropic. 1. Open the Claude app and tap the menu button in the upper left corner. 2. Tap your initials in the lower left corner. 3. Tap "Profile." 4. Under **Account Actions**, tap "Delete Account." 5. Tap "I Understand" to confirm. ## What happens when you delete your account When you delete your account, you’ll no longer have access to your conversations, projects, and account information. Learn more about **[how long Anthropic stores your data](https://privacy.claude.com/en/articles/10023548-how-long-do-you-store-my-data)**. ## When you need to contact support In some scenarios you'll need to contact our team to delete your account. If this applies to you, it'll be noted in your account settings. Learn more about **[how to get support](https://support.claude.com/en/articles/9015913-how-to-get-support)**. If you have multiple accounts associated with the same email address, you'll need to specify which accounts you want to delete when you contact us. --- ## how-can-i-delete-my-claude-account.md # How can I delete my Claude account? Once you are logged in, click your initials or name in the lower left corner and select "Settings." Navigate to [Settings \> Account](https://claude.ai/settings/account). ## Considerations for paid Claude accounts Before deleting Claude accounts with paid subscriptions (Pro or Max plans): 1. Cancel your subscription from your [Billing settings](https://claude.ai/settings/billing). 2. Wait until the end of your current subscription period. 3. Once the subscription lapses, proceed with account deletion. Click "Delete Account" and follow the prompts. **Please note that deleting your account is permanent** and you will no longer have access to saved chats. If you wish to keep your data, we recommend exporting it before deletion by following the steps listed here: [How can I export my Claude data?](https://support.claude.com/en/articles/9450526-how-can-i-export-my-claude-data) If you have multiple accounts associated with the same email address, you'll need to specify which accounts you want to delete when making your request. There are some scenarios where you will need to [contact our team](https://support.claude.com/en/articles/9015913-how-to-get-support) to delete your account. If this is the case, it will be noted in your account: --- ## how-can-i-delete-my-claude-console-account-fa188d88f6.md # How can I delete my Claude Console account? March 16, 2026 Copy for LLM Only Console Admins can request deletion. See [Claude Console Roles and Permissions](https://support.claude.com/en/articles/10186004-claude-console-roles-and-permissions) for a full overview of your role's capabilities. This article explains how a Claude Console Admin can delete their organization via Console settings. Note that deletion impacts all members of a Console organization. ## Before deletion - Confirm which specific Console organization needs to be deleted. - Deletion affects all users within the organization, so ensure they are notified prior to deletion. - Back up any necessary data as this action cannot be reversed after seven days. ## How to delete your Console organization 1. Log in to your Console Admin account. 2. Navigate to [Settings \> Organization](https://platform.claude.com/settings/organization). 3. Click the red “Delete organization” button. 4. A **Delete \[your org name\]** modal will appear; click “Acknowledge & continue” to move forward. 5. To confirm the deletion, type “delete \[your org name\]” as indicated in the modal to make the button clickable, then click “Delete this organization.” 6. You will see an “Organization deleted” confirmation in the upper right corner of your screen. ## Frequently Asked Questions ### I accidentally deleted my Console organization – what should I do? If you followed the steps above to delete your Console organization but want to revert this action, our Support team can restore your account data within seven days of deletion. Please [contact Support](https://support.claude.com/en/articles/9015913-how-to-get-support) for further assistance. ### I have an outstanding balance; how can I delete my Console organization? If you have an outstanding balance, you will see a message during the deletion flow that prompts you to pay the balance first by routing you to [Settings \> Billing](https://platform.claude.com/settings/billing). You must pay this outstanding balance before you’re able to move forward with the deletion process. ### I’m seeing a message about contacting the Support team when I try to delete my Console organization. There are some scenarios where you will need to contact our team to delete your account. If this is the case, it will be noted when you try to delete your organization: If you are seeing this message, this indicates that your Console organization cannot be deleted via the self-service pathway. --- ## how-can-i-delete-my-claude-console-account.md 4. How can I delete my Claude Console account? # How can I delete my Claude Console account? Only Console Admins can request deletion. See [Claude Console Roles and Permissions](https://support.claude.com/en/articles/10186004-claude-console-roles-and-permissions) for a full overview of your role's capabilities. This article explains how a Claude Console Admin can delete their organization via Console settings. Note that deletion impacts all members of a Console organization. ## Before deletion - Confirm which specific Console organization needs to be deleted. - Deletion affects all users within the organization, so ensure they are notified prior to deletion. - Back up any necessary data as this action cannot be reversed after seven days. ## How to delete your Console organization 1. Log in to your Console Admin account. 2. Navigate to [Settings \> Organization](https://platform.claude.com/settings/organization). 3. Click the red “Delete organization” button. 4. A **Delete \[your org name\]** modal will appear; click “Acknowledge & continue” to move forward. 5. To confirm the deletion, type “delete \[your org name\]” as indicated in the modal to make the button clickable, then click “Delete this organization.” 6. You will see an “Organization deleted” confirmation in the upper right corner of your screen. ## Frequently Asked Questions ### I accidentally deleted my Console organization – what should I do? If you followed the steps above to delete your Console organization but want to revert this action, our Support team can restore your account data within seven days of deletion. Please [contact Support](https://support.claude.com/en/articles/9015913-how-to-get-support) for further assistance. ### I have an outstanding balance; how can I delete my Console organization? If you have an outstanding balance, you will see a message during the deletion flow that prompts you to pay the balance first by routing you to [Settings \> Billing](https://platform.claude.com/settings/billing). You must pay this outstanding balance before you’re able to move forward with the deletion process. ### I’m seeing a message about contacting the Support team when I try to delete my Console organization. There are some scenarios where you will need to contact our team to delete your account. If this is the case, it will be noted when you try to delete your organization: If you are seeing this message, this indicates that your Console organization cannot be deleted via the self-service pathway. --- ## how-can-i-export-my-claude-ai-data.md # How can I export my Claude data? Data exports are available to individual Claude users (free, Pro, and Max) with active accounts. Data exports include conversation data and the user data for your account. Individual Claude users can export user information and chat history from [Settings \> Privacy](https://claude.ai/settings/data-privacy-controls) on the web app or Claude Desktop (it's not possible to run an export from Claude for iOS or Android). Follow these steps to export your data: 1. Click on your initials in the lower left corner of your account. 2. Select "Settings" from the menu. 3. Navigate to the "Privacy" section. 4. Click the "Export data" button. Once the export has been processed, you will receive a download link via email. Please note: - There may be a small delay while the export is generated. - The email will be sent to the address associated with your account. - You must be signed in to your account to download your data using this link. - The download link will expire 24 hours after delivery. - If your link expires, you can always request a new one by repeating the export process. ## Can I import or migrate this data to another Claude account? We do not support migrating data between separate accounts at this time. --- ## how-do-i-change-the-email-address-associated-with-my-account-410aeb888a.md # How do I change the email address associated with my account? March 16, 2026 Copy for LLM It's not possible to change the email address associated with your Claude account at this time. When creating an account, please make sure you use an email you'll have long-term access to. If you need to use Claude with a different email address, do the following: ### 1. If you have a paid plan (Pro or Max), follow these steps to cancel it - Log in to your Claude account. - Click on your initials or name in the bottom left corner. - Navigate to [Settings \> Billing](https://claude.ai/settings/billing). - Find the **Cancellation** section and click "Cancel." Your cancellation will take effect at the end of your current billing period and you can continue using your paid plan until your billing period ends. **Note:** To avoid charges for the next billing period, cancel at least 24 hours before your next billing date. If you lost access to the email address you used and can't log in to your account, please contact our Support team from an email address you can access and 'cc' the email in question on your response. Confirm that you want to cancel the subscription associated with the copied email address so our team can assist. ### 2. Unlink your phone number from the account If you want to use the same phone number to verify your new Claude account, you should also request that we unlink it from the old account when you 'cc' that email address. ### 3. Delete the old account After cancelling your previous subscription and unlinking your phone number, you can delete your account by navigating to [Settings \> Account](https://claude.ai/settings/account), clicking "Delete Account," and following the prompts. **Please note that deleting your account is permanent** and you will no longer have access to saved chats. If you wish to keep your data, we recommend exporting it before deletion by following the steps in [How can I export my Claude data?](https://support.claude.com/en/articles/9450526-how-can-i-export-my-claude-data) If you see "Contact support" instead of a "Delete account" button, you'll need to [reach out to our Support team](https://support.claude.com/en/articles/9015913-how-to-get-support) to request assistance with deletion. --- ## how-do-i-change-the-email-address-associated-with-my-account.md 4. How do I change the email address associated with my account? # How do I change the email address associated with my account? It's not possible to change the email address associated with your Claude account at this time. When creating an account, please make sure you use an email you'll have long-term access to. If you need to use Claude with a different email address, do the following: ### 1. If you have a paid plan (Pro or Max), follow these steps to cancel it - Log in to your Claude account. - Click on your initials or name in the bottom left corner. - Navigate to [Settings \> Billing](https://claude.ai/settings/billing). - Find the **Cancellation** section and click "Cancel." Your cancellation will take effect at the end of your current billing period and you can continue using your paid plan until your billing period ends. **Note:** To avoid charges for the next billing period, cancel at least 24 hours before your next billing date. If you lost access to the email address you used and can't log in to your account, please contact our Support team from an email address you can access and 'cc' the email in question on your response. Confirm that you want to cancel the subscription associated with the copied email address so our team can assist. ### 2. Unlink your phone number from the account If you want to use the same phone number to verify your new Claude account, you should also request that we unlink it from the old account when you 'cc' that email address. ### 3. Delete the old account After cancelling your previous subscription and unlinking your phone number, you can delete your account by navigating to [Settings \> Account](https://claude.ai/settings/account), clicking "Delete Account," and following the prompts. **Please note that deleting your account is permanent** and you will no longer have access to saved chats. If you wish to keep your data, we recommend exporting it before deletion by following the steps in [How can I export my Claude data?](https://support.claude.com/en/articles/9450526-how-can-i-export-my-claude-data) \ If you see "Contact support" instead of a "Delete account" button, you'll need to [reach out to our Support team](https://support.claude.com/en/articles/9015913-how-to-get-support) to request assistance with deletion. --- ## how-do-i-sign-up-for-claude-pro-on-claude-for-android-b2d9c46ee9.md # How do I sign up for Claude Pro on Claude for Android? March 16, 2026 Copy for LLM To sign up for Claude Pro using the Claude app for Android, open the app on your device and click on your initials in the upper right corner. From your settings page, click on “Upgrade to Pro” and follow the payment instructions to complete your in-app purchase. --- ## how-do-i-sign-up-for-claude-pro-on-claude-for-android.md 4. How do I sign up for Claude Pro on Claude for Android? # How do I sign up for Claude Pro on Claude for Android? To sign up for Claude Pro using the Claude app for Android, open the app on your device and click on your initials in the upper right corner. From your settings page, click on “Upgrade to Pro” and follow the payment instructions to complete your in-app purchase. --- ## how-do-i-sign-up-for-claude-pro-on-the-claude-app-for-ios-22fcc2091f.md # How do I sign up for Claude Pro on the Claude app for iOS? March 16, 2026 Copy for LLM To sign up for Claude Pro using the Claude app for iOS, open the app on your device and click on your initials in the upper right corner. From your settings page, click on “Upgrade to Pro” and follow the payment instructions to complete your in-app purchase. --- ## how-do-i-sign-up-for-claude-pro-on-the-claude-app-for-ios.md 4. How do I sign up for Claude Pro on the Claude app for iOS? # How do I sign up for Claude Pro on the Claude app for iOS? To sign up for Claude Pro using the Claude app for iOS, open the app on your device and click on your initials in the upper right corner. From your settings page, click on “Upgrade to Pro” and follow the payment instructions to complete your in-app purchase. --- ## how-do-i-sign-up-for-the-max-plan-522e7bd583.md # How do I sign up for the Max plan? July 13, 2026 Copy for LLM 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 will be upgraded to Max immediately, with billing adjusted on a prorated basis for the remainder of your current billing cycle. 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-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 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 3. Select "Upgrade to Max" 4. Choose your preferred usage tier (5x or 20x) 5. Confirm your upgrade Your Pro plan will be upgraded to Max immediately, with billing adjusted on a prorated basis for the remainder of your current billing cycle. **Note:** 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. ## 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-how-do-i-cancel-my-paid-claude-subscription) at any time if you choose not to continue. --- ## how-do-i-sign-up-for-the-pro-plan-d331ddbfbf.md # How do I sign up for the Pro plan? August 6, 2026 Copy for LLM This article applies to individual consumers signing up for paid Pro 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)**. ## Instructions for new users 1. Navigate to Claude (**[claude.ai](https://claude.ai)**) in a web browser. 2. Enter your email address and click “Continue with email” or click “Continue with Google” if applicable. 3. Follow the Google prompts, or use the emailed login link to access your new Claude account. 4. Click on your initials or name in the lower left corner and select “Settings” from the menu. 5. Navigate to **[Settings \> Billing](https://claude.ai/settings/billing)** and click the “Upgrade plan” button. 6. After landing on **[the upgrade page](https://claude.ai/upgrade)**, click “Get Pro plan.” 7. Choose between monthly and annual billing periods. 8. Enter your payment information and click “Subscribe.” ## Instructions for existing free users 1. Log in to your free 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)** and click the “Upgrade plan” button. 4. After landing on **[the upgrade page](https://claude.ai/upgrade)**, click “Get Pro plan.” 5. Choose between monthly and annual billing periods. 6. Enter your payment information and click “Subscribe.” ## How does subscription renewal work for Pro plans? After subscribing for a Pro plan, your subscription will be set to automatically renew at the end of each billing period (monthly or annual) by default. This ensures uninterrupted access to Pro features. However, you have the flexibility to **[cancel your paid plan](https://support.claude.com/en/articles/8325617-how-do-i-cancel-my-paid-claude-subscription)** at any time if you choose not to continue. ## I am outside of your supported locations; can I subscribe to the Pro plan? No. Paid plans are only available for users physically located in one of our **[supported locations](https://support.claude.com/en/articles/8461763-where-can-i-access-claude)**, and we require a phone number from a supported location to create an account. ## Is there still a free version of Claude? Yes. You can still access the free version of Claude without subscribing for a paid plan. Note that like Pro, the free version of Claude is only available to customers physically located in one of our **[supported regions](https://support.claude.com/en/articles/8461763-where-can-i-access-claude)**. --- ## how-do-i-sign-up-for-the-pro-plan.md # How do I sign up for the Pro plan? This article applies to individual consumers signing up for paid Pro 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. Navigate to Claude ([claude.ai](http://claude.ai)) in a web browser. 2. Enter your email address and click “Continue with email” or click “Continue with Google” if applicable. 3. Follow the Google prompts, or use the emailed login link to access your new Claude account. 4. Click on your initials or name in the lower left corner and select “Settings” from the menu. 5. Navigate to [Settings \> Billing](http://claude.ai/settings/billing) and click the “Upgrade plan” button. 6. After landing on [the upgrade page](https://claude.ai/upgrade), click “Get Pro plan.” 7. Choose between monthly and annual billing periods. 8. Enter your payment information and click “Subscribe.” ## Instructions for existing free users 1. Log in to your free 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](http://claude.ai/settings/billing) and click the “Upgrade plan” button. 4. After landing on [the upgrade page](https://claude.ai/upgrade), click “Get Pro plan.” 5. Choose between monthly and annual billing periods. 6. Enter your payment information and click “Subscribe.” ## How does subscription renewal work for Pro plans? After subscribing for a Pro plan, your subscription will be set to automatically renew at the end of each billing period (monthly or annual) by default. This ensures uninterrupted access to Pro features. However, you have the flexibility to [cancel your paid plan](https://support.claude.com/en/articles/8325617-how-do-i-cancel-my-paid-claude-subscription) at any time if you choose not to continue. ## I am outside of your supported locations; can I subscribe to the Pro plan? No. Paid plans are only available for users physically located in one of our [supported locations](https://support.claude.com/en/articles/8461763-where-can-i-access-claude), and we require a phone number from a supported location to create an account. ## Is there still a free version of Claude? Yes. You can still access the free version of Claude without subscribing for a paid plan. Note that like Pro, the free version of Claude is only available to customers physically located in one of our [supported regions](https://support.claude.com/en/articles/8461763-where-can-i-access-claude). --- ## how-do-i-view-and-sign-your-data-processing-addendum-dpa-58e61fcc5d.md # How do I view and sign your Data Processing Addendum (DPA)? March 16, 2026 Copy for LLM *This article is about our commercial products (e.g. Claude for Work, Claude API). For our consumer products (e.g. Claude Free, Claude Pro), see [here](https://privacy.claude.com/en/collections/10663362-consumers).* Anthropic’s DPA with Standard Contractual Clauses (SCCs) is automatically incorporated into our [Commercial Terms of Service](https://www.anthropic.com/legal/commercial-terms), and can be viewed [here](https://www.anthropic.com/legal/data-processing-addendum). When you accept Anthropic’s Commercial Terms of Service, you also accept our DPA. **Important note for third-party platform users:** If you access Claude via a third-party platform or service provider, your use of Claude in those cases is governed by the third-party platform's terms of service. --- ## how-do-i-view-and-sign-your-data-processing-addendum-dpa.md 3. How do I view and sign your Data Processing Addendum (DPA)? # How do I view and sign your Data Processing Addendum (DPA)? *This article is about our commercial products (e.g. Claude for Work, Claude API). For our consumer products (e.g. Claude Free, Claude Pro), see [here](https://privacy.claude.com/en/collections/10663362-consumers).* Anthropic’s DPA with Standard Contractual Clauses (SCCs) is automatically incorporated into our [Commercial Terms of Service](https://www.anthropic.com/legal/commercial-terms), and can be viewed [here](https://www.anthropic.com/legal/data-processing-addendum). When you accept Anthropic’s Commercial Terms of Service, you also accept our DPA. **Important note for third-party platform users:** If you access Claude via a third-party platform or service provider, your use of Claude in those cases is governed by the third-party platform's terms of service. --- ## how-to-get-support-57c428239c.md # How to get support Copy for LLM This guide explains how to get support for your Claude or Console account. Different support options are available depending on your plan. Support is provided in writing through the support messenger and email. We don't offer phone support. ## Pro and Max plans, Team and Enterprise plan owners, and Console Admins You have full access to: - All help documentation - Fin, our AI support bot - Further assistance from our Product Support team While we don't offer phone or live chat support, our Product Support team will gladly assist you through our support messenger. **Note for Enterprise admins:** Primary Owners and Owners can configure which members of their organization reach human support by designating support contacts. By default, Admins and Owners keep human support access. For configuration details, see **[Designate support contacts for human support](https://support.claude.com/en/articles/15263885)**. ### Seeking support for Claude 1. Log in to your Claude account. 2. Click your initials or name in the lower left corner and select “Get help” from the menu. 3. In the support messenger: - Search help resources - Chat with Fin, our AI support bot 4. Click “Send us a message” to start chatting with Fin. 5. Click "Accept," then select your issue from the available options. 6. Depending on the selected issue, provide additional details when prompted. 7. If your issue requires additional investigation or input from our Product Support team, Fin will pass your inquiry along. The team's reply appears in this same conversation. You'll see it in the messenger and receive a copy by email at the address on your Claude account, so you don't need to keep this window open. ### Seeking support for the Claude API or Console 1. Log in to your **[Console account](https://platform.claude.com)**. 2. Click your initials or name in the lower left corner of the Console and select “Get help” from the menu. 3. This will open a support messenger in the lower right corner of the Console. 4. In the support messenger: - Search help resources - Chat with Fin, our AI support bot 5. Click “Send us a message” to start chatting with Fin. 6. Click "Accept," then select your issue from the available options. 7. Depending on the selected issue, provide additional details when prompted. 8. If your issue requires additional investigation or input from our Product Support team, Fin will pass your inquiry along. The team's reply appears in this same conversation. You'll see it in the messenger and receive a copy by email at the address on your Claude account, so you don't need to keep this window open. ### Seeking support for any account type from the Help Center Users who are logged in to their Claude or Console accounts will be able to click the icon in the lower right corner of any Help Center page to open the support messenger and start chatting with Fin. ## What happens after you message us Support is asynchronous. After your request reaches our team, a specialist investigates and replies in the same conversation. Response times vary by plan and by the severity of the issue. ### Chat and email are the same conversation - Every reply we send appears in the support messenger and is emailed to the address on your Claude account (the account you were signed in with when you started the conversation). - Replying to that email continues the same conversation. You don't need to return to the chat, and you can close the chat window at any time without missing our reply. - Keep one conversation per issue. Opening a second request for the same problem creates a duplicate that has to be re-triaged, which usually slows the answer down. If you haven't heard back, reply in your existing conversation instead. ### Keep colleagues in the loop - A conversation started in the messenger includes only you. To bring in a colleague, such as the affected user or your IT admin, reply to the conversation from the email thread and cc them. Their replies join the same conversation. - If you're reporting an issue on behalf of someone else, include their work email address, any error messages or screenshots, and when the issue started in your first message. This avoids an extra round of questions. - Enterprise organizations can also **[designate support contacts](https://support.claude.com/en/articles/15263885)**. ## Team and Enterprise plan non-owners, and Console non-Admins You’ll chat with Fin, an AI support agent, to help answer your questions. ### Team plans and Console organizations Human specialist support is not directly available for your account seat type. If Fin can't find a resolution and you need to escalate to our human team of specialists, your account's Primary Owner, Owner, or Console Admin can reach out on your behalf. ### Enterprise plans Primary Owners and Owners can designate support contacts: members who can reach human support without holding an Owner role. If you're a designated support contact, you'll have the option to wait for a human when chatting with Fin. Otherwise, Fin will handle your conversation, and if escalation is needed, your account's Primary Owner, Owner, or a designated support contact can reach out on your behalf. For configuration details, see **[Designate support contacts for human support](https://support.claude.com/en/articles/15263885)**. ## Free Claude users Free Claude users have access to: - All help documentation - Fin, our AI support bot - **[Account deletion](https://support.claude.com/en/articles/9028421)** support in cases where self-serve is unavailable To get support: 1. Log in to your Claude.ai account. 2. Click your initials or name in the lower left corner. 3. Select "Get help." 4. Use the support messenger to: - Search help resources. - Chat with Fin, our AI support bot. ## Unable to log in? If you can't access your account, we can still help with: 1. Account deletion 2. Data exports 3. Subscription support To request assistance: 1. Click the message icon in the lower right corner of the Help Center. 2. Start a conversation. 3. Select "I can't login." ## About subscription support If you're a paid subscriber having trouble accessing your account, our team can: - Help locate login information - Process subscription cancellations - Check refund eligibility **Note:** In order to assist with these tasks, we will need to validate details about your account and the payment method used. ## Designated point of contact for users in the EU Users in the EU can find instructions on how to find the single point of contact for users in the EU under the DSA here: **[Designated point of contact for users in the EU](https://support.claude.com/en/articles/11595103-)**. ## Report compliance concerns - UK and Australian users - Users in the UK can find instructions to report non-compliance with UK OSA duties here: **[Report a concern](https://docs.google.com/forms/d/e/1FAIpQLSfdo76veqg3pHZTh_nI14j1DyRO8coz6ocTa9mEuF5DcYgxuA/viewform)**. This includes reporting related to illegal content safety duties, content reporting obligations, freedom of expression and privacy, or the use of proactive technology by Anthropic in breach of Anthropic’s Terms of Service. - Users in Australia can find instructions to report non-compliance with the DIS Standard and information about the role and functions of the eSafety Commissioner here: **[Report a Concern: Australian DIS Standard compliance](https://support.claude.com/en/articles/12335811-report-a-concern-australian-dis-standard-compliance)**. ------------------------------------------------------------------------ ## Frequently asked questions ### Do you offer phone or video support? No. Support is provided in writing through the messenger and email. Enterprise customers who need a live working session can arrange one through their Anthropic account team. ### Can I close the chat window while I wait? Yes. Replies are delivered to the messenger and to your account email, so you won't miss one. ### Which email address will you use to reply? The email address on the Claude account you were signed in with when you started the conversation. ​ ### I haven't heard back. Should I open another request? No. Reply in your existing conversation, in the messenger or by email, and it moves back into the queue with its history intact. ​ ### I have a business-critical outage. Is there a faster path? Organization owners and admins on qualifying Enterprise plans have prioritized options in the messenger. Platform status is always available on **[our status page](https://status.claude.com)**. --- ## how-to-get-support-for-claude-for-government-cb7c5e780a.md # How to get support for Claude for Government Copy for LLM **Please note:** This page is hosted outside of Claude for Government's FedRAMP boundary. Don't share sensitive information with our AI support bot. This article explains how Claude for Government Admins can contact Anthropic Support. We've designed a specialized process to ensure your sensitive information remains secure while providing you with the help you need. ## How to get started Claude for Government Desktop Org Admins or Tenant Admins can click "Support" at the bottom of the Claude for Government admin portal. This will open a help center article with a messenger icon in the lower right corner. Click "Send us a message" to initiate the support process. **Note:** Only Claude for Government Desktop Org Admins and Tenant Admins can access this prioritized support path. If you have a different role and need to contact Support, please have an Org Admin or Tenant Admin submit the request on your behalf. --- ## how-to-get-support-for-claude-for-government.md 4. How to get support for Claude for Government # How to get support for Claude for Government **Please note:** This page is hosted outside of Claude for Government's FedRAMP boundary. This article explains how Claude for Government Owners and Primary Owners can contact Anthropic Support. We've designed a specialized process to ensure your sensitive information remains secure while providing you with the help you need. ## How to Get Started 1. Log in to your Owner or Primary Owner Claude for Government account. 2. Click your initials or name in the lower left corner and select “Get help” from the menu. 3. You will be directed to a page describing additional guidelines for our specialized support process. 4. Follow the guidelines described on that page to submit a support inquiry. --- ## i-need-to-add-or-update-my-paid-claude-account-s-tax-or-vat-id-1ff42cd114.md # Add or update your paid Claude account’s tax or VAT ID August 6, 2026 Copy for LLM ## 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](https://support.claude.com/en/articles/12997130-understanding-your-billing-address-and-tax-calculation)** for details on how to view or update your billing address. --- ## i-need-to-add-or-update-my-paid-claude-account-s-tax-or-vat-id.md 4. Add or update your paid Claude account’s tax or VAT ID # Add or update your paid Claude account’s tax or VAT ID ## 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](http://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](http://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](../17-Billing-Plans/understanding-your-billing-address-and-tax-calculation.md) for details on how to view or update your billing address. --- ## important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisi-0545ce214a.md # Important considerations before enabling single sign-on (SSO) and JIT/SCIM provisioning August 4, 2026 Copy for LLM Before setting up SSO for your Claude or Claude Console organization, review this guide to understand key concepts, plan your approach, and complete any prerequisite steps. ## Understanding parent organizations Our single sign-on feature uses the concept of a "parent organization." This is an entity that stores SSO settings that can be shared across multiple Claude or Console organizations. Your plan type determines whether or not you have a parent organization by default: [TABLE] ### Key things to know - **Domain verification is required before you can configure SSO.** Domains are verified at the parent organization level. Once a domain is verified, other parent organizations can't claim it. - **Multiple organizations can be linked to the same parent organization** to share domain verification and SSO configuration. This is useful if you have both Claude (Team/Enterprise plans) and Console organizations. - **Each parent organization can only be linked to one Identity Provider.** This means that every organization linked to a single parent organization must be managed through the same IdP. - **Enabling group mappings** allows you to control which users are provisioned to which organizations under your parent, and with which roles. See **[Configure groups and assign users in your IdP](https://support.claude.com/en/articles/13133195-setting-up-jit-or-scim-provisioning#h_0178209cfa)** for details. - **Parent organizations manage identity and access only**—specifically, domain verification, SSO configuration, and user provisioning. Billing, invoicing, and usage tracking are handled at the individual organization level and aren't affected by parent organization relationships. ### What this means for you You'll need to check the parent organization dynamic depending on your plan: - **If you have a Team or Enterprise plan:** You can proceed directly to the **[Setting up single sign-on (SSO)](https://support.claude.com/en/articles/13132885-setting-up-single-sign-on-sso)** guide. Your parent organization is already in place (or will be created when you enable SSO for Team plans). - **If you have a Claude Console organization and an existing Team or Enterprise plan:** Your Console organization may already be linked to your Team or Enterprise parent organization. Check if you can access **[platform.claude.com/settings/identity](http://platform.claude.com/settings/identity)**. If so, this indicates that the org is linked to the parent organization and SSO is already configured. If not, an Owner on your Team or Enterprise plan can initiate a merge to link your Console organization (see **[Merge organizations](#h_3bad8701c8)** below) to their parent organization and the existing SSO configuration. - **If you have a Claude Console organization without a Team or Enterprise plan:** **[Contact our Sales team](https://claude.com/contact-sales)** to request a parent organization for your Console account. Once we create your parent organization, you'll see the Identity settings page in Claude Console and can proceed with SSO setup. ------------------------------------------------------------------------ ## Merge organizations Team or Enterprise organizations can invite other organizations to join an existing parent organization and share SSO configuration. **Important:** The **Merge Organizations** option is only available on Claude (claude.ai). Console organizations can't initiate a merge; they must be invited by a Team or Enterprise organization. ### Requirements for merging - The Team or Enterprise organization initiating the proposal must have verified domains in their parent organization. - All members in the organization being invited must have email addresses matching those verified domains. - An Admin (Console) or Owner (Claude) for the invited organization needs to approve the merge. - The organization being invited can't already belong to another parent organization. **Note:** If an organization you want to invite doesn't appear in the invite list, it may already belong to its own parent organization with separate verified domains and SSO. **[Contact support](https://support.claude.com/en/articles/9015913-how-to-get-support)** to have it detached from its current parent. Detaching clears that organization's existing domain verification and SSO/SCIM configuration, so confirm its admins are aware before you request it. ### To initiate a merge proposal 1. Navigate to **[Organization settings \> Organization and access](https://claude.ai/admin-settings/organization)**. 2. Click "Invite" under **Merge Organizations**. 3. Select the organization you want to invite and click "Next." 4. Review the member count and click "Invite." 5. The merge proposal will be sent to the invited organization's Admins/Owners, with the email subject "Parent Organization Update: New Member Organization Proposed," and must be approved within 14 days. **Note:** If the person initiating the merge is also an Admin/Owner in the invited organization, only one approval is required. ### To approve a merge proposal Approving a merge takes two steps, one on each side, and completes only after both are done: 1. **Invited organization:** An organization Owner or Primary Owner needs to go to **[claude.ai/settings/join-proposal](https://claude.ai/settings/join-proposal)** to accept. 2. **Parent organization:** An Owner or Admin of an organization already under the parent approves from Organization settings \> Organization and access \> Pending Organizations, or from the link in the "Parent Organization Update: New Member Organization Proposed" email. Once a Console organization is merged, it gains access to the **[Identity and access page](http://platform.claude.com/settings/identity)**, in the Organization settings, to configure SSO and provisioning settings. ------------------------------------------------------------------------ ## Authentication You'll find settings you can use to configure SSO in the **Authentication** section. This is where you configure the primary SSO connection and policies that apply across multiple joined Claude or Console organizations. ------------------------------------------------------------------------ ## Restrict new organization creation Once your organization's domains are verified, owners will see a **Restrict organization creation** toggle under **Security** on the Organization and access page. Toggle this on to prevent users from creating new Claude or Console organizations, including personal accounts, using any of your verified domains. ------------------------------------------------------------------------ ## Provisioning options Once SSO is configured, you can choose how users are provisioned to your organization. [TABLE] **\*Note:** Only Enterprise plan organizations can enable SCIM provisioning; if a Console organization is merged with a Team plan's parent organization, it won't have access to SCIM provisioning. For detailed information on how each provisioning method works, see **[Set up JIT or SCIM provisioning](https://support.claude.com/en/articles/13133195-set-up-jit-or-scim-provisioning)**. ------------------------------------------------------------------------ ## What happens to existing users when SSO is enabled After enabling SSO for your organization, there are two distinct scenarios to consider for users who have individual accounts associated with your verified company domain: ### Users with existing Free/Pro/Team/Max accounts who ARE added to your SSO application These users keep access to their existing Free/Pro/Team/Max accounts. They can toggle between the Team or Enterprise plan account and their previous accounts by clicking the profile icon with their initials in the bottom left corner. ### Users with existing Free/Pro/Team/Max accounts who are NOT added to your SSO application - **If "Require SSO for Claude" is NOT enabled:** These users can still access their existing accounts using the "Continue with email" option. - **If "Require SSO for Claude" IS enabled:** These users will be unable to access their existing Free/Pro/Team/Max accounts. Please note that these accounts are not deleted, but will be inaccessible as users are unable to log in via SSO. ------------------------------------------------------------------------ ## How to view existing Claude / Console accounts associated with your verified domain To view or download information about your verified domains and their usage across Claude organizations: 1. Navigate to the **Organization and access** section in Claude (**[claude.ai/admin-settings/organization](https://claude.ai/admin-settings/organization)**) or the **Identity and access** section in Console (**[platform.claude.com/settings/identity](http://platform.claude.com/settings/identity)**). 2. Click “Domain memberships” in the **Domains** section. 3. Review the information or download details in CSV or JSON format. ------------------------------------------------------------------------ ## Recommended steps before implementing SSO ### Communicate clearly with your team - Notify all employees about the upcoming migration to SSO. - Provide a clear timeline for when the change will occur. - Advise employees who won't be added to the SSO application to save or **[export their conversation history](https://support.claude.com/en/articles/9450526-how-can-i-export-my-claude-data)** if SSO will be enforced. ### Plan for a smooth transition - Schedule the SSO implementation during a time that minimizes disruption. - Ensure your IT team is prepared to support employees with the transition. - Have a clear process in place for granting access to authorized users. - If possible, implement both SSO and provisioning features at the same time. Taking time to test, communicate, and plan before enabling domain verification and SSO will help ensure a successful transition and positive experience for your organization. ------------------------------------------------------------------------ ## Next steps Once you've reviewed these considerations and completed any necessary prerequisite steps (such as merging organizations), proceed to **[Set up single sign-on (SSO)](https://support.claude.com/en/articles/13132885-set-up-single-sign-on-sso)** for detailed implementation instructions. --- ## important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisi.md 3. Important considerations before enabling single sign-on (SSO) and JIT/SCIM provisioning # Important considerations before enabling single sign-on (SSO) and JIT/SCIM provisioning Before setting up SSO for your Claude or Claude Console organization, review this guide to understand key concepts, plan your approach, and complete any prerequisite steps. ## Understanding parent organizations Our single sign-on feature uses the concept of a "parent organization." This is an entity that stores SSO settings that can be shared across multiple Claude or Console organizations. Your plan type determines whether or not you have a parent organization by default: [TABLE] ### Key things to know - **Domain verification is required before you can configure SSO.** Domains are verified at the parent organization level—once verified, other parent organizations cannot claim the same domain. - **Multiple organizations can be linked to the same parent organization** to share domain verification and SSO configuration. This is useful if you have both Claude (Team/Enterprise plans) and Console organizations. - **Each parent organization can only be linked to one Identity Provider.** This means that every organization linked to a single parent organization must be managed through the same IdP. - **Enabling group mappings** allows you to control which users are provisioned to which organizations under your parent, and with which roles. See **[Configure groups and assign users in your IdP](../13-Enterprise-Admin/setting-up-jit-or-scim-provisioning.md#h_0178209cfa)** for details. - **Parent organizations manage identity and access only**—specifically, domain verification, SSO configuration, and user provisioning. Billing, invoicing, and usage tracking are handled at the individual organization level and aren't affected by parent organization relationships. ### What this means for you You will need to check the parent organization dynamic depending on your plan: - **If you have a Team or Enterprise plan:** You can proceed directly to the **[Setting up single sign-on (SSO)](setting-up-single-sign-on-sso.md)** guide. Your parent organization is already in place (or will be created when you enable SSO for Team plans). - **If you have a Claude Console organization and an existing Team or Enterprise plan:** Your Console organization may already be linked to your Team or Enterprise parent organization. Check if you can access **[platform.claude.com/settings/identity](http://platform.claude.com/settings/identity)**. If so, this indicates that the org is linked to the parent organization and SSO is already configured. If not, an Owner on your Team or Enterprise plan can initiate a merge to link your Console organization (see **[Merge organizations](#h_3bad8701c8)** below) to their parent organization and the existing SSO configuration. - **If you have a Claude Console organization without a Team or Enterprise plan:** **[Contact our Sales team](https://claude.com/contact-sales)** to request a parent organization for your Console account. Once we create your parent organization, you will see the Identity settings page in Claude Console and can proceed with SSO setup. ------------------------------------------------------------------------ ## Merge organizations Team or Enterprise organizations can invite other orgs to join an existing parent organization and share SSO configuration. **Important:** The **Merge Organizations** option is only available on Claude (claude.ai). Console organizations cannot initiate a merge—they must be invited by a Team or Enterprise organization. ### Requirements for merging - The Team or Enterprise organization initiating the proposal must have verified domains in their parent organization. - All members in the organization being invited must have email addresses matching those verified domains. - An Admin (Console) or Owner (Claude) for the invited organization needs to approve the merge. ### To initiate a merge proposal 1. Navigate to **[Organization settings \> Identity and access](https://claude.ai/admin-settings/identity)**. 2. Click "Invite" under **Merge Organizations**. 3. Select the organization you want to invite and click "Next." 4. Review the member count and click "Invite." 5. The merge proposal will be sent to the invited organization's Admins/Owners, with the email subject “*Parent Organization Update: New Member Organization Proposed*,” and must be approved within 14 days. **Note:** If the person initiating the merge is also an Admin/Owner in the invited organization, only one approval is required. ### To approve a merge proposal An organization Owner or Primary Owner needs to go to **[claude.ai/settings/join-proposal](https://claude.ai/settings/join-proposal)** to accept the merge. Once a Console organization is merged, it will gain access to the **[Identity and access page](http://platform.claude.com/settings/identity)**, in the Organization settings, to configure SSO and provisioning settings. ------------------------------------------------------------------------ ## Global access settings You'll find settings you can use to configure SSO in the **Global access settings** section. This is where you configure the primary SSO connection and policies that apply across multiple joined Claude or Console organizations. While some settings in this section apply to all Claude and Console organizations that have joined the parent organization, those with a "This org only" label apply only to the specific organization you're currently viewing. This allows you to enable organization-specific features like group mappings. ------------------------------------------------------------------------ ## Restrict new organization creation Once your organization's domains are verified, owners will see a **Restrict organization creation** toggle under **Security** on the Identity and access organization settings page. Toggle this on to prevent users from creating new Claude or Console organizations—including personal accounts—using any of your verified domains. ------------------------------------------------------------------------ ## Provisioning options Once SSO is configured, you can choose how users are provisioned to your organization. [TABLE] **\*Note:** Only Enterprise plan organizations can enable SCIM provisioning; if a Console organization is merged with a Team plan’s parent org, it will not have access to SCIM provisioning. For detailed information on how each provisioning method works, see **[Set up JIT or SCIM provisioning](../13-Enterprise-Admin/set-up-jit-or-scim-provisioning.md)**. ------------------------------------------------------------------------ ## What happens to existing users when SSO is enabled After enabling SSO for your organization, there are two distinct scenarios to consider for users who have individual accounts associated with your verified company domain: ### Users with existing free/Pro/Team/Max accounts who ARE added to your SSO application These users will maintain access to their existing free/Pro/Team/Max accounts. They will have the ability to toggle between the Team or Enterprise plan account and their previous accounts by clicking the profile icon with their initials in the bottom left corner. ### Users with existing free/Pro/Team/Max accounts who are NOT added to your SSO application - **If "Require SSO for Claude" is NOT enabled:** These users can still access their existing accounts using the "Continue with email" option. - **If "Require SSO for Claude" IS enabled:** These users will be unable to access their existing free/Pro/Team/Max accounts. Please note that these accounts are not deleted, but will be inaccessible as users are unable to log in via SSO. ------------------------------------------------------------------------ ## How to view existing Claude / Console accounts associated with your verified domain To view or download information about your verified domains and their usage across Claude organizations: 1. Navigate to the Identity and access section in Claude (**[claude.ai/admin-settings/identity](http://claude.ai/admin-settings/identity)**) or Console (**[platform.claude.com/settings/identity](http://platform.claude.com/settings/identity)**). 2. Click “Domain memberships” in the **Domains** section. 3. Review the information or download details in CSV or JSON format. ------------------------------------------------------------------------ ## Recommended steps before implementing SSO ### Communicate clearly with your team - Notify all employees about the upcoming migration to SSO. - Provide a clear timeline for when the change will occur. - Advise employees who won't be added to the SSO application to save or **[export their conversation history](https://support.claude.com/en/articles/9450526-how-can-i-export-my-claude-data)** if SSO will be enforced. ### Plan for a smooth transition - Schedule the SSO implementation during a time that minimizes disruption. - Ensure your IT team is prepared to support employees with the transition. - Have a clear process in place for granting access to authorized users. - If possible, implement both SSO and provisioning features at the same time. Taking time to test, communicate, and plan before enabling domain capture and SSO will help ensure a successful transition and positive experience for your organization. ------------------------------------------------------------------------ ## Next steps Once you've reviewed these considerations and completed any necessary prerequisite steps (such as merging organizations), proceed to **[Set up single sign-on (SSO)](set-up-single-sign-on-sso.md)** for detailed implementation instructions. --- ## introduction-to-prompt-design-8eae4e058d.md # Introduction to prompt design March 16, 2026 Copy for LLM Claude is trained to be a helpful, honest, and harmless assistant. It is used to “speaking” conversationally and you can instruct it in English. Think of Claude as a newly-hired contractor. It doesn’t have any context about you, your task, or your organization. Give it very specific instructions about exactly what you’d like it to do. For more information on effective prompt design, refer to our **[Claude API Docs](https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/claude-prompting-best-practices)**. --- ## introduction-to-prompt-design.md # Introduction to prompt design Claude is trained to be a helpful, honest, and harmless assistant. It is used to “speaking” conversationally and you can instruct it in English. Think of Claude as a newly-hired contractor. It doesn’t have any context about you, your task, or your organization. Give it very specific instructions about exactly what you’d like it to do. For more information on effective prompt design, refer to our **[Claude API Docs](../10-Prompting-Guides/build-with-claude-prompt-engineering-claude-prompting-best-practices.md)**. --- ## log-in-to-your-claude-account-42e921f4bc.md # Log in to your Claude account May 19, 2026 Copy for LLM When you open Claude on a web browser ([claude.ai](http://claude.ai)), the desktop app, or a mobile app, you will see two different options for logging in to your Claude account. ## Continue with Google Click “Continue with Google” if you want to use your Google account credentials to log in to Claude. This opens a modal where you can enter your Google email address and password. After entering your credentials and clicking “Next,” you will be authenticated into your Claude account. ## Continue with email If you’d prefer to use your email address to log in, enter it in the field pictured above, and click “Continue with email.” This will send you an email with the subject line *“Secure link to log in to Claude.ai”* and a login link. ### Clicking the link on the same device If you requested the login email and clicked the link using the same device, you’ll be automatically redirected to your logged-in Claude account. ### Clicking the link on another device If you requested the login email and clicked the link using a different device (requesting from a web browser and clicking the email link on a phone, for example), then you will still see a “Sign in with Claude.ai” link in the email, but clicking it will generate a verification code. You should enter this code on the original device where you requested the login email to authenticate. ## Authenticating to subscription plans Claude offers subscription plans (Free, Pro, Max, Team, Enterprise) that let subscribers authenticate using OAuth tokens or other methods. Subscription plans can only be used by subscribers, and the usage included in these plans is designed to support ordinary use of native Anthropic applications, including the Claude web, desktop, and mobile applications and Claude Code. The preferred way to access Anthropic services using third-party software, tools, or services (“third-party tools”), including open-source projects, is through API key authentication through Claude Console or a supported cloud provider. Anthropic may at its discretion allow paid subscribers who have enabled **[usage credits](https://support.claude.com/en/articles/12429409-)** to use certain third-party tools to access Anthropic services included in paid subscription plans, but reserves the right to draw use of such third-party tools from usage credits rather than subscription limits. Users are responsible for any usage credit charges incurred this way. Use of third-party tools that misrepresent their identity to Anthropic’s servers, attempt to route third-party traffic against subscription limits, or otherwise violate applicable terms or policies is prohibited and such use may be enforced against. ## Developers If you’re building a product, application, or tool for others, use API key authentication through Claude Console or a supported cloud provider. Applications that misrepresent their identity to Anthropic’s servers, attempt to route third-party traffic against subscription limits, or otherwise violate applicable terms or policies are prohibited and may be enforced against. ------------------------------------------------------------------------ ## Troubleshooting ### I entered my email address but I haven’t received my login email. If you requested a login email but you haven’t received it yet, do the following: - Check your spam and junk folders for emails from @mail.anthropic.com. - Check your server's quarantined emails. - Whitelist @mail.anthropic.com in your email settings. - Try logging in again after a few minutes. **Note:** Business, government, or .edu email users may need to contact their IT department to adjust email security settings. ### I received the email but I'm still having trouble logging in. If you received the login email but can’t log in with the link or code, take note of the error message you’re seeing. If you’re creating an account or logging in for the first time and seeing a message about your phone number, please refer to **[Verifying your phone number](https://support.claude.com/en/articles/8287232-verifying-your-phone-number)**. Otherwise, visit the **[Claude status page](https://status.claude.com/)** to check if there are any known service disruptions or maintenance activities. If the status page shows an ongoing system-wide incident, it's best to wait for service restoration before attempting further troubleshooting. ------------------------------------------------------------------------ ## Frequently asked questions ### How can I set a password for my Claude account? It’s not possible to create a dedicated password for your Claude account at this time. ### Can I use my Claude account across multiple devices? To use your Claude account across multiple devices, enter the same email address you use to log in on your usual device. For example, if you signed up for your Claude account on a web browser, you can access the same account on the Claude mobile apps by entering the same email address when you log in. ### I have multiple accounts – how can I switch between them? If you have both an individual Claude account and a Team or Enterprise plan account tied to the same email address, follow these steps to switch to your other account: 1. Click your initials in the bottom left corner. 2. Select the desired account. 3. Look for the check mark indicating the active account. ### I don’t want to use “Continue with Google” to log in anymore; how can I revoke access to my Google account? If you've previously authenticated using Google, you can follow these steps to unlink your Google account from Claude and use only the emailed login link moving forward: 1. Visit [https://myaccount.google.com/connections](https://myaccount.google.com/connections). 2. Locate “Claude by Anthropic” in the list and click on it. 3. Click "See details." 4. Click the "Stop using Sign in with Google” button. You should also follow these steps if you're experiencing issues with Google login. After clearing your existing connection, try logging in to Claude again using "Continue with Google." ### I used Apple’s Hide My Email feature to create my Claude account – how can I log in on another device? If you signed up for your Claude account using Apple's Hide My Email feature, follow these steps to log in: 1. Use your @privaterelay.appleid.com email address. 2. Click "Continue with email" on Claude, Claude Desktop, or Claude Mobile. 3. A secure login link will be sent to your Apple ID email. 4. Click the “Sign in with Claude.ai” link in the email you received to log in. If you are already logged in to Claude for iOS, you can see the email address you used: 1. Open Claude for iOS. 2. Click your initials in the top right corner. 3. Look for your email address under Settings. --- ## log-in-to-your-console-account-363b800d03.md # Log in to your Console account August 18, 2026 Copy for LLM When you navigate to the **[Claude Console](https://platform.claude.com)**, you will see two different options for logging in to your Console account. ## Continue with Google Click "Continue with Google" if you want to use your Google account credentials to log in to the Console. This opens a modal where you can enter your Google email address and password. After entering your credentials and clicking "Next," you will be authenticated into your Console account. ## Continue with email If you'd prefer to use your email address to log in, enter it in the field pictured above, and click "Continue with email." This will send you an email with the subject line *"Secure link to log in to Claude Console"* and a login link. ### Clicking the link on the same device If you requested the login email and clicked the link using the same device, you'll be automatically redirected to your logged-in Console account. ### Clicking the link on another device If you requested the login email and clicked the link using a different device (requesting from a web browser and clicking the email link on a phone, for example), then you will still see a "Sign in to Claude Console" button in the email, but clicking it will generate a verification code. You should enter this code on the original device where you requested the login email to authenticate. ## Troubleshooting ### I entered my email address but I haven't received my login email. If you requested a login email but you haven't received it yet, do the following: - Check your spam and junk folders for emails from @mail.anthropic.com. - Check your server's quarantined emails. - Whitelist @mail.anthropic.com in your email settings. - Try logging in again after a few minutes. **Note:** Business, government, or .edu email users may need to contact their IT department to adjust email security settings. ### I received the email but I'm still having trouble logging in. If you received the login email but can't log in with the link or code, take note of the error message you're seeing. Visit the [Claude status page](https://status.claude.com/) to check if there are any known service disruptions or maintenance activities. If the status page shows an ongoing system-wide incident, it's best to wait for service restoration before attempting further troubleshooting. ## Frequently Asked Questions ### How can I set a password for my Console account? It's not possible to create a dedicated password for your Console account at this time. ### Does my organization use Single Sign-On (SSO)? If you're a member of an organization that has configured single sign-on for the Console, you'll be redirected to your SSO provider when you attempt to log in. For information about setting up SSO for your organization, see **[Set up single sign-on (SSO)](https://support.claude.com/en/articles/13132885-set-up-single-sign-on-sso)**. ### I have multiple Console accounts – how can I switch between them? If you're a member of multiple Console organizations tied to the same email address, follow these steps to switch to your other account: 1. Click your initials in the bottom left corner to open a menu showing all the accounts tied to your logged-in email address. 2. Select the desired account. 3. Look for the check mark indicating the active account. ### I don't want to use "Continue with Google" to log in anymore; how can I revoke access to my Google account? If you've previously authenticated using Google, you can follow these steps to unlink your Google account from the Console and use only the emailed login link moving forward: 1. Visit **[https://myaccount.google.com/connections](https://myaccount.google.com/connections)**. 2. Locate "Claude by Anthropic" in the list and click on it. 3. Click "See details." 4. Click the "Stop using Sign in with Google" button. ### Can I have both a Claude account and a Console account? Yes, you can have both a Claude account (for using Claude at claude.ai) and a Console account (for accessing the playground and Claude API). These are separate accounts, though you can use the same email address for both. Learn more in **[Can I have a Claude account and a Console account?](https://support.claude.com/en/articles/8987223-can-i-have-a-claude-account-and-a-console-account)** --- ## logging-in-to-your-claude-account-2c1d42f1ab.md # Log in to your Claude account May 19, 2026 Copy for LLM When you open Claude on a web browser ([claude.ai](http://claude.ai)), the desktop app, or a mobile app, you will see two different options for logging in to your Claude account. ## Continue with Google Click “Continue with Google” if you want to use your Google account credentials to log in to Claude. This opens a modal where you can enter your Google email address and password. After entering your credentials and clicking “Next,” you will be authenticated into your Claude account. ## Continue with email If you’d prefer to use your email address to log in, enter it in the field pictured above, and click “Continue with email.” This will send you an email with the subject line *“Secure link to log in to Claude.ai”* and a login link. ### Clicking the link on the same device If you requested the login email and clicked the link using the same device, you’ll be automatically redirected to your logged-in Claude account. ### Clicking the link on another device If you requested the login email and clicked the link using a different device (requesting from a web browser and clicking the email link on a phone, for example), then you will still see a “Sign in with Claude.ai” link in the email, but clicking it will generate a verification code. You should enter this code on the original device where you requested the login email to authenticate. ## Authenticating to subscription plans Claude offers subscription plans (Free, Pro, Max, Team, Enterprise) that let subscribers authenticate using OAuth tokens or other methods. Subscription plans can only be used by subscribers, and the usage included in these plans is designed to support ordinary use of native Anthropic applications, including the Claude web, desktop, and mobile applications and Claude Code. The preferred way to access Anthropic services using third-party software, tools, or services (“third-party tools”), including open-source projects, is through API key authentication through Claude Console or a supported cloud provider. Anthropic may at its discretion allow paid subscribers who have enabled **[usage credits](https://support.claude.com/en/articles/12429409-)** to use certain third-party tools to access Anthropic services included in paid subscription plans, but reserves the right to draw use of such third-party tools from usage credits rather than subscription limits. Users are responsible for any usage credit charges incurred this way. Use of third-party tools that misrepresent their identity to Anthropic’s servers, attempt to route third-party traffic against subscription limits, or otherwise violate applicable terms or policies is prohibited and such use may be enforced against. ## Developers If you’re building a product, application, or tool for others, use API key authentication through Claude Console or a supported cloud provider. Applications that misrepresent their identity to Anthropic’s servers, attempt to route third-party traffic against subscription limits, or otherwise violate applicable terms or policies are prohibited and may be enforced against. ------------------------------------------------------------------------ ## Troubleshooting ### I entered my email address but I haven’t received my login email. If you requested a login email but you haven’t received it yet, do the following: - Check your spam and junk folders for emails from @mail.anthropic.com. - Check your server's quarantined emails. - Whitelist @mail.anthropic.com in your email settings. - Try logging in again after a few minutes. **Note:** Business, government, or .edu email users may need to contact their IT department to adjust email security settings. ### I received the email but I'm still having trouble logging in. If you received the login email but can’t log in with the link or code, take note of the error message you’re seeing. If you’re creating an account or logging in for the first time and seeing a message about your phone number, please refer to **[Verifying your phone number](https://support.claude.com/en/articles/8287232-verifying-your-phone-number)**. Otherwise, visit the **[Claude status page](https://status.claude.com/)** to check if there are any known service disruptions or maintenance activities. If the status page shows an ongoing system-wide incident, it's best to wait for service restoration before attempting further troubleshooting. ------------------------------------------------------------------------ ## Frequently asked questions ### How can I set a password for my Claude account? It’s not possible to create a dedicated password for your Claude account at this time. ### Can I use my Claude account across multiple devices? To use your Claude account across multiple devices, enter the same email address you use to log in on your usual device. For example, if you signed up for your Claude account on a web browser, you can access the same account on the Claude mobile apps by entering the same email address when you log in. ### I have multiple accounts – how can I switch between them? If you have both an individual Claude account and a Team or Enterprise plan account tied to the same email address, follow these steps to switch to your other account: 1. Click your initials in the bottom left corner. 2. Select the desired account. 3. Look for the check mark indicating the active account. ### I don’t want to use “Continue with Google” to log in anymore; how can I revoke access to my Google account? If you've previously authenticated using Google, you can follow these steps to unlink your Google account from Claude and use only the emailed login link moving forward: 1. Visit [https://myaccount.google.com/connections](https://myaccount.google.com/connections). 2. Locate “Claude by Anthropic” in the list and click on it. 3. Click "See details." 4. Click the "Stop using Sign in with Google” button. You should also follow these steps if you're experiencing issues with Google login. After clearing your existing connection, try logging in to Claude again using "Continue with Google." ### I used Apple’s Hide My Email feature to create my Claude account – how can I log in on another device? If you signed up for your Claude account using Apple's Hide My Email feature, follow these steps to log in: 1. Use your @privaterelay.appleid.com email address. 2. Click "Continue with email" on Claude, Claude Desktop, or Claude Mobile. 3. A secure login link will be sent to your Apple ID email. 4. Click the “Sign in with Claude.ai” link in the email you received to log in. If you are already logged in to Claude for iOS, you can see the email address you used: 1. Open Claude for iOS. 2. Click your initials in the top right corner. 3. Look for your email address under Settings. --- ## logging-in-to-your-claude-account.md # Logging in to your Claude account When you open Claude on a web browser ([claude.ai](http://claude.ai)), the desktop app, or a mobile app, you will see two different options for logging in to your Claude account. ## Continue with Google Click “Continue with Google” if you want to use your Google account credentials to log in to Claude. This opens a modal where you can enter your Google email address and password. After entering your credentials and clicking “Next,” you will be authenticated into your Claude account. ## Continue with email If you’d prefer to use your email address to log in, enter it in the field pictured above, and click “Continue with email.” This will send you an email with the subject line *“Secure link to log in to Claude.ai”* and a login link. ### Clicking the link on the same device If you requested the login email and clicked the link using the same device, you’ll be automatically redirected to your logged-in Claude account. ### Clicking the link on another device If you requested the login email and clicked the link using a different device (requesting from a web browser and clicking the email link on a phone, for example), then you will still see a “Sign in with Claude.ai” link in the email, but clicking it will generate a verification code. You should enter this code on the original device where you requested the login email to authenticate. ## Troubleshooting ### I entered my email address but I haven’t received my login email. If you requested a login email but you haven’t received it yet, do the following: - Check your spam and junk folders for emails from @mail.anthropic.com. - Check your server's quarantined emails. - Whitelist @mail.anthropic.com in your email settings. - Try logging in again after a few minutes. **Note:** Business, government, or .edu email users may need to contact their IT department to adjust email security settings. ### I received the email but I'm still having trouble logging in. If you received the login email but can’t log in with the link or code, take note of the error message you’re seeing. If you’re creating an account or logging in for the first time and seeing a message about your phone number, please refer to [Verifying your phone number](https://support.claude.com/en/articles/8287232-verifying-your-phone-number). Otherwise, visit the [Claude status page](https://status.claude.com/) to check if there are any known service disruptions or maintenance activities. If the status page shows an ongoing system-wide incident, it's best to wait for service restoration before attempting further troubleshooting. ## Frequently Asked Questions ### How can I set a password for my Claude account? It’s not possible to create a dedicated password for your Claude account at this time. ### Can I use my Claude account across multiple devices? To use your Claude account across multiple devices, enter the same email address you use to log in on your usual device. For example, if you signed up for your Claude account on a web browser, you can access the same account on the Claude mobile apps by entering the same email address when you log in. ### I have multiple accounts – how can I switch between them? If you have both an individual Claude account and a Team or Enterprise plan account tied to the same email address, follow these steps to switch to your other account: 1. Click your initials in the bottom left corner. 2. Select the desired account. 3. Look for the check mark indicating the active account. ### I don’t want to use “Continue with Google” to log in anymore; how can I revoke access to my Google account? If you've previously authenticated using Google, you can follow these steps to unlink your Google account from Claude and use only the emailed login link moving forward: 1. Visit [https://myaccount.google.com/connections](https://myaccount.google.com/connections). 2. Locate “Claude by Anthropic” in the list and click on it. 3. Click "See details." 4. Click the "Stop using Sign in with Google” button. You should also follow these steps if you're experiencing issues with Google login. After clearing your existing connection, try logging in to Claude again using "Continue with Google." ### I used Apple’s Hide My Email feature to create my Claude account – how can I log in on another device? If you signed up for your Claude account using Apple's Hide My Email feature, follow these steps to log in: 1. Use your @privaterelay.appleid.com email address. 2. Click "Continue with email" on Claude, Claude Desktop, or Claude Mobile. 3. A secure login link will be sent to your Apple ID email. 4. Click the “Sign in with Claude.ai” link in the email you received to log in. If you are already logged in to Claude for iOS, you can see the email address you used: 1. Open Claude for iOS. 2. Click your initials in the top right corner. 3. Look for your email address under Settings. --- ## logging-in-to-your-console-account-23a06981d3.md # Log in to your Console account August 18, 2026 Copy for LLM When you navigate to the **[Claude Console](https://platform.claude.com)**, you will see two different options for logging in to your Console account. ## Continue with Google Click "Continue with Google" if you want to use your Google account credentials to log in to the Console. This opens a modal where you can enter your Google email address and password. After entering your credentials and clicking "Next," you will be authenticated into your Console account. ## Continue with email If you'd prefer to use your email address to log in, enter it in the field pictured above, and click "Continue with email." This will send you an email with the subject line *"Secure link to log in to Claude Console"* and a login link. ### Clicking the link on the same device If you requested the login email and clicked the link using the same device, you'll be automatically redirected to your logged-in Console account. ### Clicking the link on another device If you requested the login email and clicked the link using a different device (requesting from a web browser and clicking the email link on a phone, for example), then you will still see a "Sign in to Claude Console" button in the email, but clicking it will generate a verification code. You should enter this code on the original device where you requested the login email to authenticate. ## Troubleshooting ### I entered my email address but I haven't received my login email. If you requested a login email but you haven't received it yet, do the following: - Check your spam and junk folders for emails from @mail.anthropic.com. - Check your server's quarantined emails. - Whitelist @mail.anthropic.com in your email settings. - Try logging in again after a few minutes. **Note:** Business, government, or .edu email users may need to contact their IT department to adjust email security settings. ### I received the email but I'm still having trouble logging in. If you received the login email but can't log in with the link or code, take note of the error message you're seeing. Visit the [Claude status page](https://status.claude.com/) to check if there are any known service disruptions or maintenance activities. If the status page shows an ongoing system-wide incident, it's best to wait for service restoration before attempting further troubleshooting. ## Frequently Asked Questions ### How can I set a password for my Console account? It's not possible to create a dedicated password for your Console account at this time. ### Does my organization use Single Sign-On (SSO)? If you're a member of an organization that has configured single sign-on for the Console, you'll be redirected to your SSO provider when you attempt to log in. For information about setting up SSO for your organization, see **[Set up single sign-on (SSO)](https://support.claude.com/en/articles/13132885-set-up-single-sign-on-sso)**. ### I have multiple Console accounts – how can I switch between them? If you're a member of multiple Console organizations tied to the same email address, follow these steps to switch to your other account: 1. Click your initials in the bottom left corner to open a menu showing all the accounts tied to your logged-in email address. 2. Select the desired account. 3. Look for the check mark indicating the active account. ### I don't want to use "Continue with Google" to log in anymore; how can I revoke access to my Google account? If you've previously authenticated using Google, you can follow these steps to unlink your Google account from the Console and use only the emailed login link moving forward: 1. Visit **[https://myaccount.google.com/connections](https://myaccount.google.com/connections)**. 2. Locate "Claude by Anthropic" in the list and click on it. 3. Click "See details." 4. Click the "Stop using Sign in with Google" button. ### Can I have both a Claude account and a Console account? Yes, you can have both a Claude account (for using Claude at claude.ai) and a Console account (for accessing the playground and Claude API). These are separate accounts, though you can use the same email address for both. Learn more in **[Can I have a Claude account and a Console account?](https://support.claude.com/en/articles/8987223-can-i-have-a-claude-account-and-a-console-account)** --- ## logging-in-to-your-console-account.md # Logging in to your Console account When you navigate to the [Claude Console](../04-API-Reference/Other/platform-claude-com.md), you will see two different options for logging in to your Console account. ## Continue with Google Click "Continue with Google" if you want to use your Google account credentials to log in to the Console. This opens a modal where you can enter your Google email address and password. After entering your credentials and clicking "Next," you will be authenticated into your Console account. ## Continue with email If you'd prefer to use your email address to log in, enter it in the field pictured above, and click "Continue with email." This will send you an email with the subject line *"Secure link to log in to Claude Console"* and a login link. ### Clicking the link on the same device If you requested the login email and clicked the link using the same device, you'll be automatically redirected to your logged-in Console account. ### Clicking the link on another device If you requested the login email and clicked the link using a different device (requesting from a web browser and clicking the email link on a phone, for example), then you will still see a "Sign in to Claude Console" button in the email, but clicking it will generate a verification code. You should enter this code on the original device where you requested the login email to authenticate. ## Troubleshooting ### I entered my email address but I haven't received my login email. If you requested a login email but you haven't received it yet, do the following: - Check your spam and junk folders for emails from @mail.anthropic.com. - Check your server's quarantined emails. - Whitelist @mail.anthropic.com in your email settings. - Try logging in again after a few minutes. **Note:** Business, government, or .edu email users may need to contact their IT department to adjust email security settings. ### I received the email but I'm still having trouble logging in. If you received the login email but can't log in with the link or code, take note of the error message you're seeing. Visit the [Claude status page](https://status.claude.com/) to check if there are any known service disruptions or maintenance activities. If the status page shows an ongoing system-wide incident, it's best to wait for service restoration before attempting further troubleshooting. ## Frequently Asked Questions ### How can I set a password for my Console account? It's not possible to create a dedicated password for your Console account at this time. ### Does my organization use Single Sign-On (SSO)? If you're a member of an organization that has configured single sign-on for the Console, you'll be redirected to your SSO provider when you attempt to log in. For information about setting up SSO for your organization, see [Set up single sign-on (SSO)](set-up-single-sign-on-sso.md). ### I have multiple Console accounts – how can I switch between them? If you're a member of multiple Console organizations tied to the same email address, follow these steps to switch to your other account: 1. Click your initials in the bottom left corner to open a menu showing all the accounts tied to your logged-in email address. 2. Select the desired account. 3. Look for the check mark indicating the active account. ### I don't want to use "Continue with Google" to log in anymore; how can I revoke access to my Google account? If you've previously authenticated using Google, you can follow these steps to unlink your Google account from the Console and use only the emailed login link moving forward: 1. Visit [https://myaccount.google.com/connections](https://myaccount.google.com/connections). 2. Locate "Claude by Anthropic" in the list and click on it. 3. Click "See details." 4. Click the "Stop using Sign in with Google" button. ### Can I have both a Claude account and a Console account? Yes, you can have both a Claude account (for using Claude at claude.ai) and a Console account (for accessing the Workbench and Claude API). These are separate accounts, though you can use the same email address for both. Learn more in [Can I have a Claude account and a Console account?](can-i-have-a-claude-account-and-a-console-account.md) --- ## move-your-personal-claude-account-to-a-team-or-enterprise-organization-1d5cca0150.md # Move your personal Claude account to a Team or Enterprise organization Updated today Copy for LLM If you're using Claude with a personal account (Free, Pro, or Max) tied to your work email, you may be able to move that account into your organization's Team or Enterprise workspace. There are two paths: you can start a migration yourself (Team and Enterprise) or your admin can claim accounts on your domain (Enterprise only). **Note:** Enterprise organizations that have turned on HIPAA readiness or customer-managed encryption keys (CMEK) can't receive data from a personal account. If your organization uses either, you won't be offered the option to bring your data with you, and a domain claim won't offer to merge your account. You can export your data first if you want a copy. Learn more about **[HIPAA-ready Enterprise plans](https://support.claude.com/en/articles/13296973)** and **[customer-managed encryption keys](https://support.claude.com/en/articles/15505325)**. ------------------------------------------------------------------------ ## What moves when you migrate Both paths move the same content for each person. ### What moves - Chats - Artifacts within chats - Projects, project instructions, and files, including projects created through or used with Cowork - Uploaded files and attachments - Project sync configurations (which Drive folders and repositories a project syncs) - Claude's memory from chats and projects, unless your organization has memory turned off - Claude Code memory and personal settings such as tool settings, notification preferences, and consents, unless your organization account already has its own values set - Claude Design systems and projects migrated since 14 August 2026 ### What doesn't move - Custom skills. There's no migration path for skills. Export any you want to keep before you migrate. - Sign-ins to connected apps and services**.** All authorizations are revoked. You'll reconnect each app from your organization account. - Custom connectors you added yourself. You'll need to add them again in your organization account, and your organization's policy may not allow them. - Published artifacts. Publishing isn't available on Team and Enterprise plans. - Public share links to chats. These stop working permanently. - Pending share invites - Cowork sessions in the desktop app. Desktop sessions and the folders you've connected are stored locally, not in the cloud, so they stay on your computer. Copy anything you want to keep after you migrate. - Cowork cloud sessions (web and mobile). Download any files or outputs you want to keep before you migrate. - Claude Code cloud sessions (web, scheduled tasks, and mobile) - Claude Design systems and projects migrated before 14 August 2026 ### Before you migrate 1. Export any custom skills you want to keep. 2. Save a copy of anything you've published as an artifact, since published artifacts won't be available afterward. 3. Share any content you've sent out as a public link another way, because those links will break. 4. Make a note of the apps you've connected so you can reconnect them. **Note:** After a migration, your chat list can take a little while to fill in. Searching by chat title works right away. The first time Claude searches your past chats in your new organization, it rebuilds its search index, so Claude might not find everything at first. If chats still seem to be missing, sign out, sign back in, and search again. ------------------------------------------------------------------------ ## Voluntary migration Voluntary migration is supported on Team and Enterprise plans. If you have a personal Claude account on the same email address as your organization, you can choose how to handle it when you join a Team or Enterprise organization: - **Keep both accounts:** Your personal account stays active. You can switch between it and your organization account from your account menu. - **Use your organization account only:** You'll see two migration options after selecting this. - **Bring your data with you:** Your personal data moves into the organization's workspace, as described above in **[What moves when you migrate](#h_4e63ef6e87)**. Your personal account closes, and active Pro or Max subscriptions are canceled and refunded depending on how you purchased the plan. - **Delete your data:** Your personal account closes (with a prorated refund if you had a paid subscription), but no content moves into the organization. You start with a clean account. You can choose to download your account data before deleting it. If your organization has turned on HIPAA readiness or CMEK, **Bring your data with you** isn't offered. ### How do refunds work for migrated accounts? What happens to your Pro or Max plan after migrating depends on where you bought it: - **Directly (not through a mobile app):** Your Pro or Max subscription is canceled automatically as part of the move, and you receive a prorated refund for unused time. The refund is issued about 24 hours after your plan is canceled, and depending on your bank, it can take several more business days to appear on your statement. - **Google Play Store:** Your Pro or Max subscription is canceled automatically as part of the move, and you receive a prorated refund for unused time. Refunds for Google Play purchases can take a few days to appear. - **Apple App Store:** Your Pro or Max subscription isn't canceled. Apple doesn't allow third-party cancellation, so you'll need to cancel it yourself through your Apple ID settings. If you don't, Apple keeps charging you after your personal account closes. For cancellation instructions, see **[Cancel your Pro or Max subscription](https://support.claude.com/en/articles/8325617)**. ### How to start a migration Start from your organization account, not your personal account. If you're signed in to your personal account, switch first by clicking your initials or name in the lower left corner and selecting your organization. On a Team plan, you'll be prompted to choose when you accept an invite to your organization. If you don't pick an option right away, you'll see a reminder banner for about seven days. You can also go to **[Settings \> Account \> Close your personal account](https://claude.ai/settings/account)** at any time to initiate the migration. On an Enterprise plan, you won't see a prompt when you join. To start the migration, go to **[Settings \> Account \> Close your personal account](https://claude.ai/settings/account)**. ### If you own both accounts Owning the Team organization doesn't change where you start the migration. If you created the organization from your personal account, you may still be signed in to the personal one, and **Close your personal account** won't appear there. Switch to your organization account first, then go to **[Settings \> Account](https://claude.ai/settings/account)**. **Important:** Bringing your work into a Team or Enterprise workspace is one-way. Once content has been moved, it can't be moved back to a personal account. ### Apple App Store subscribers If you subscribed to the Pro or Max plan through the Apple App Store, **Keep both accounts** is your only option. Apple doesn't allow third-party cancellation of App Store subscriptions, so we can't auto-cancel your iOS plan as part of the migration. If you'd rather move your work into the Team, **[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 migration from the reminder banner or **[Settings \> Account](https://claude.ai/settings/account)**. ------------------------------------------------------------------------ ## Domain claiming Domain claiming is supported on Claude Enterprise plans only. Enterprise admins can claim all existing personal accounts on their organization's verified domain and move them into the Enterprise workspace. If your admin initiates a domain claim, you'll receive an email and in-product notification with a deadline (at least 30 days out) to choose between merging your data into a new Enterprise account or starting fresh. If your organization has turned on HIPAA readiness or CMEK, you'll still get the notification and deadline, but merging isn't offered. Export anything you want to keep before the deadline, then start fresh. For the full walkthrough of your options, deadlines, and what happens to your subscription, see **[Respond to an Enterprise domain claim on your Claude account](https://support.claude.com/en/articles/14625626-respond-to-an-enterprise-domain-claim-on-your-claude-account)**. ------------------------------------------------------------------------ ## Manage personal and organization accounts You may have both a personal account and an organization account tied to the same email address. You can switch between them by clicking your initials or name in the lower left corner of the screen. A blue checkmark shows which account you're currently using. Click the other account to switch to it and access its separate conversations and projects. ------------------------------------------------------------------------ ## Discontinue your personal account manually If you want to close your personal account without moving any of your work into an organization: 1. **[Cancel your individual paid plan](https://support.claude.com/en/articles/8325617-how-do-i-cancel-my-paid-claude-subscription)** if applicable. 2. **[Export your data](https://support.claude.com/en/articles/9450526-how-can-i-export-my-claude-data)** while you still have access. 3. Navigate to **[Settings \> Account](https://claude.ai/settings/account)** and click "Delete" to **[delete your account](https://support.claude.com/en/articles/9028421-how-can-i-delete-my-claude-account)**. --- ## my-prompt-isn-t-giving-me-a-helpful-answer-be93be72e8.md # My prompt isn’t giving me a helpful answer. March 16, 2026 Copy for LLM Claude works best when you give it clear and specific instructions. When crafting your prompt, keep the following principles in mind: - Explain your ask simply and clearly. - Make sure that your prompt contains as much context as possible. Pretend you are giving these instructions to someone with no background knowledge about what you are asking. - Break down complex requests into substeps. - Give Claude feedback: you provide Claude with follow-up instructions, clarifications, or ask it to rewrite an answer. --- ## onelogin-sso-scim-email-mismatch-369f184454.md # OneLogin SSO/SCIM email mismatch March 24, 2026 Copy for LLM Claude uses email as the primary identifier to match SSO logins to provisioned seats. In OneLogin, SCIM provisioning and SAML SSO are configured in separate tabs of the app and can reference different user profile fields, causing a mismatch that blocks access. **Applies to:** Enterprise plans and Console organizations using SCIM provisioning. Team plans don't have SCIM provisioning, so this mismatch scenario doesn't apply—see **[Set up JIT or SCIM provisioning](https://support.claude.com/en/articles/13133195)** for what's available on each plan. ------------------------------------------------------------------------ ## Symptoms People may experience one or more of the following when attempting to access your organization via SSO: - **"Account creation is blocked"** — The person authenticates via SSO but Claude cannot find a matching provisioned account. If your organization has organization creation restricted (recommended), the person is blocked entirely. - **Landing on a free personal account** — If organization creation is not restricted, the person bypasses your organization entirely and creates or lands on a free personal account instead of their provisioned seat. - **"Please confirm your email" mismatch** — The SSO callback shows a different email than the one the person entered at login. - **Claude Code authentication failure** — The Claude Code CLI shows an email mismatch error during the authentication flow. ------------------------------------------------------------------------ ## How this happens OneLogin user profiles contain distinct fields for username and email, which may hold different values. SCIM provisioning parameters and SAML attribute statements are configured independently and can each pull from a different field: [TABLE] A common mismatch: the SCIM parameters tab maps the email attribute to Username (which may be an employee ID or short name) while the SAML attribute statement sends the Email field. Claude requires an **exact string match**. **Common confusion:** OneLogin's SCIM parameters and SAML attribute statements are in different tabs of the same app — **Parameters** for SCIM and **SSO** (or **Parameters** with SAML-specific fields) for SSO. Both must be checked and aligned. ------------------------------------------------------------------------ ## Diagnostic steps ## Step 1 — Confirm the mismatch 1. **Check the SCIM email:** In the OneLogin Admin portal, go to **Applications → \[Claude app\] → Parameters**. Find the field mapped to the email Claude receives. Note the **OneLogin value** column — this shows which user field is sent. 2. **Check the SAML email:** In the same app, go to the **SSO** tab. Click **More Actions → Edit SAML Response** or check the **SAML Attribute Statements** section. Find the attribute for email and note its source field. 3. **Check a specific person:** In **Users → \[User\]**, compare the **Username** and **Email** fields. If they differ, any mapping using one vs. the other will cause a mismatch. ## Step 2 — Identify the scope of the problem - If **most or all** provisioned people share the same email format mismatch, this is a **systemic attribute mapping problem**. The fix is in your IdP's SCIM attribute mapping. - If only **one or two people** are affected, the issue is likely specific to those accounts. Check their profile directly. ## Step 3 — Review user field values 1. Go to **Users → \[Affected User\] → User Info**. 2. Check both the **Username** and **Email** fields. 3. If Username is in a format that doesn't match a valid email, SCIM may be sending an invalid or non-matching value. ------------------------------------------------------------------------ ## Resolution ## Align both mappings to the Email field OneLogin's Email field is the most reliable source for both SCIM and SAML, as it's designed to hold a valid email address. 1. **Update SCIM parameter:** In **Applications → \[Claude app\] → Parameters**, find the row for the email attribute Claude receives. Change the **Value** to **Email** (the OneLogin Email field). 2. **Update SAML attribute statement:** In the **SSO** tab (or **Parameters** for SAML attributes), update the email attribute value to use the same **Email** field. 3. Click "Save." ## Trigger a full re-sync **Critical — Full sync required:** An incremental sync will *not* update existing records after you change an attribute mapping. You must trigger a **full restart** of the provisioning cycle. 1. In the app's **Provisioning** tab, look for a **Re-sync** or **Sync All** option and run it. 2. To reprovision individual people: Go to **Users → \[User\] → Applications**, find the Claude app, and use **Re-provision**. 3. Check the OneLogin provisioning activity log for errors. 4. Verify updated email values appear in the log before asking people to retry login. ------------------------------------------------------------------------ ## Post-fix cleanup After correcting the attribute mapping and completing the full sync: - **Rogue free accounts:** If organization creation was not restricted before the fix, some people may have inadvertently created free personal Claude accounts. Contact **[our Support team](https://support.claude.com/en/articles/9015913)** to have these removed. - **Ghost accounts (wrong-email seats):** The originally provisioned accounts with the incorrect email may still exist in your organization, occupying seats that can never be used. Contact our Support team to deprovision these. - **Seat availability:** If ghost accounts are occupying all contracted seats, new logins will fail with an out-of-seats error even after the mapping is fixed. - **Re-adding affected people:** After ghost accounts are removed, people with the corrected email may need to be re-invited or re-provisioned. - **Prevent future occurrences:** Enable "Restrict organization creation" in your organization's Identity and access settings. ------------------------------------------------------------------------ ## Verification 1. Check a sample of provisioned people—confirm their email in the provisioning log matches the email format that SSO sends. 2. Ask an affected person to clear browser cookies for claude.ai, then log in via SSO. 3. Confirm people aren't creating free accounts. 4. If Claude Code was affected, have the person re-run `claude auth login --enterprise` and confirm the email matches their provisioned seat. ------------------------------------------------------------------------ ## Common issues [TABLE] ------------------------------------------------------------------------ ## When to contact Support Contact **[our Support team](https://support.claude.com/en/articles/9015913)** with your organization's domain, the affected person's email, and screenshots of your attribute mappings when: - SCIM and SSO attributes appear identical but people still cannot access their seats. - You need confirmation of the email Claude recorded during SCIM provisioning for specific people. - You need help cleaning up ghost accounts or rogue free orgs. - People are hitting an out-of-seats error despite available contracted seats. --- ## onelogin-sso-setup-e5d2f18a94.md # OneLogin SSO setup August 6, 2026 Copy for LLM This guide walks through configuring SSO and SCIM for Claude with OneLogin as your identity provider. It applies to Team plans, Enterprise plans, and Console organizations. ## Prerequisites - A Claude Team plan, Enterprise plan, or Console organization with a parent organization (see **[Important considerations before enabling SSO](https://support.claude.com/en/articles/10276682)** for Console parent org requirements) - Owner or Primary Owner role (Team and Enterprise) or Admin role (Console) - OneLogin Super User access - Your domain verified in Claude's Identity and access settings—see **[Set up single sign-on](https://support.claude.com/en/articles/13132885)** for the full setup path including domain verification ## Where to find your configuration values The Audience (Entity ID), ACS URL, and SCIM credentials referenced below are provided in the WorkOS setup flow within your Identity and access settings—not by contacting Support. - **Team and Enterprise plans:** go to **[claude.ai/admin-settings/identity](https://claude.ai/admin-settings/identity)** - **Console organizations:** go to **[platform.claude.com/settings/identity](https://platform.claude.com/settings/identity)** Start the SSO setup flow there and keep it open alongside the OneLogin Admin portal as you work through the steps below. ------------------------------------------------------------------------ ## Step 1 — Create a new application in OneLogin 1. In the OneLogin Admin portal, go to **Applications → Applications → Add App**. 2. Search for "SAML Custom Connector" and select "SAML Custom Connector (Advanced)." 3. Name it "Claude" and click "Save." ## Step 2 — Configure SAML settings 1. In the **Configuration** tab, enter the values from the WorkOS setup flow: **Audience (EntityID)**, **ACS (Consumer) URL**, and **ACS URL Validator** (regex or exact match of the ACS URL). 2. Set **SAML initiator** to **Service Provider**. 3. Set **SAML nameID format** to **Email**. 4. In the **SSO** tab, download the **Issuer URL** metadata and upload it in the WorkOS setup flow when prompted. ## Step 3 — Map attributes 1. In the **Parameters** tab, add a field: **Field name:** email, **Value:** Email (OneLogin's Email field for the person). 2. Ensure this same Email field is used for SCIM provisioning in the next step. ## Step 4 — Enable SCIM provisioning **Note:** SCIM provisioning is available on Enterprise plans and eligible Console organizations only. If you're on a Team plan, skip this step—you can use JIT provisioning instead. See **[Set up JIT or SCIM provisioning](https://support.claude.com/en/articles/13133195)**. 1. In the **Provisioning** tab, enable **Enable provisioning**. 2. Enter the SCIM Base URL and Bearer Token from the WorkOS setup flow. 3. Enable **Create user**, **Delete user**, and **Update user**. 4. In **Entitlements**, map the email attribute to the same OneLogin field as SAML. 5. Click "Save." **Critical:** SAML and SCIM must send the same email value. If people experience login failures after provisioning, see **[OneLogin SSO/SCIM email mismatch](https://support.claude.com/en/articles/13917861)**. ## Step 5 — Assign people In the **Users** tab, assign individual people or use **Rules** to automatically assign based on role or group. ## Step 6 — Verify 1. If you enabled SCIM, check the OneLogin provisioning activity log to confirm people were created in Claude. 2. Have a test user complete SSO login and verify they land in your organization's workspace. ------------------------------------------------------------------------ ## Need help? See **[Set up single sign-on](https://support.claude.com/en/articles/13132885)** for the full end-to-end flow including domain verification and choosing a provisioning approach. If you run into issues, contact **[our Support team](https://support.claude.com/en/articles/9015913)** with your OneLogin domain and a screenshot of your SAML configuration. --- ## public-sector-faqs-5b0a044ad5.md # Public Sector FAQs March 25, 2026 Copy for LLM ## 1. Products and features ### What products are available to Public Sector customers? Select your product based on both your technical/functional requirements, and also your compliance/security/deployment environment requirements. Here is a list of options: ### What is Claude for Government (C4G)? Claude for Government is Anthropic's FedRAMP-High authorized product, which is available to both government customers and contractors. Learn more here: **[Offering expanded Claude access across all three branches of the U.S. government](https://www.anthropic.com/news/offering-expanded-claude-access-across-all-three-branches-of-government)** ### How do I access Claude for Government? Submit a request here: **[Contact Sales](https://claude.com/contact-sales)** ### What is the difference between Claude Enterprise and Claude for Government? Claude Enterprise (CE) has robust enterprise-level security features that meet many standards of highly regulated industry and is appropriate for the majority of State and Local government uses. Claude for Government (C4G) is our standalone application that is FedRAMP-High authorized. C4G does not yet include Claude Code or Cowork (though they are on the roadmap to be released this year). ### Does Claude for Government include Claude Code? Not yet; though it’s coming this year. Until then, customers can use Claude Code through Bedrock or Vertex if they need a FedRAMP authorized environment. ### Can I use Claude API in government environments? Yes. Claude API is available via Amazon Bedrock (in AWS GovCloud - FedRAMP High, and in IL5+) and Google Vertex with Assured Workloads (FedRAMP-High). For more information, see our **[Claude Code product page](https://claude.com/product/claude-code)**. ### What models are available in Claude for Government? Our Claude for Government application is updated with our latest commercial model releases. ------------------------------------------------------------------------ ## 2. FedRAMP, Impact Levels, and compliance ### What types of data can be used in Claude? CUl and FIPS 199 High Impact data are authorized in Claude for Government, which is FedRAMP High authorized. Additionally, per our third-party NIST attestation, Claude Enterprise meets compliance requirements for CUl as well. The third-party NIST attestation is available under NDA here: **[\[Anthropic\] 2026 NIST 800-171r3 Attestation Letter](https://trust.anthropic.com/resources?s=zfucqt7j6yandbrsvlk2&name=%5Banthropic%5D-2026-nist-800-171-r-3-attestation-letter)** ITAR data can only be processed in Claude via AWS Bedrock, which is IL5 accredited. For most other government agencies like State and Local handling PHI or PII:, Anthropic offers a HIPAA-ready configuration for Enterprise and API customers, including the ability to sign a Business Associate Agreement (BAA). A couple of key points: - The BAA is available for Enterprise plans and direct API customers—not consumer (Free, Pro, Max) or Team plans. - It requires a Zero Data Retention (ZDR) agreement, meaning Anthropic does not store your inputs or outputs. - Certain features/integrations have limitations under the BAA (e.g., web search is excluded). You can learn more here: - BAA details: **[Business Associate Agreements (BAA) for Commercial Customers](https://support.claude.com/en/articles/8114513-business-associate-agreements-baa-for-commercial-customers)** - Certifications overview (HIPAA, SOC 2, ISO 27001): **[What Certifications has Anthropic obtained?](https://support.claude.com/en/articles/10015870-what-certifications-has-anthropic-obtained)** - **[Trust Portal](https://trust.anthropic.com)** ### What is Claude's FedRAMP authorization level? Claude for Government (C4G), and Claude via Amazon Bedrock in AWS GovCloud and Google Vertex with Assured Workloads are all FedRAMP-High. Learn more here: **[Claude in Amazon Bedrock: Approved for use in FedRAMP High and DoD IL4/5 workloads](https://www.anthropic.com/news/claude-in-amazon-bedrock-fedramp-high)** ### Are Claude's models themselves FedRAMP authorized? FedRAMP and DoD Impact Levels are certifications for cloud services (IaaS, PaaS, SaaS). AI models are software components, not cloud services. Claude models deploy within authorized environments, and customers maintain their compliance posture through the hosting platform. ### How can I get access to your FedRAMP authorization information and other associated documentation? Please submit a request for the package directly to FedRAMP using this **[FedRAMP Package Access Request Form](https://www.fedramp.gov/resources/documents/Agency_Package_Request_Form.pdf)**. ### Can I use Claude for CUI (Controlled Unclassified Information)? Yes. Claude Enterprise has received a third-party NIST attestation for use of CUI data. Alternatively, CUI data can be processed in a FedRAMP High environment via Claude for Government, Bedrock, or Vertex. The third-party NIST attestation is available under NDA here: **[\[Anthropic\] 2026 NIST 800-171r3 Attestation Letter](https://trust.anthropic.com/resources?s=zfucqt7j6yandbrsvlk2&name=%5Banthropic%5D-2026-nist-800-171-r-3-attestation-letter)** ### Can I use Claude in IL6/Secret environments? Yes. Claude is available in the AWS Secret region (IL6) via Amazon Bedrock. ### If a customer purchases Claude Enterprise via AWS Marketplace, is that FedRAMP? No. At present, our only product offering on AWS Marketplace is Claude Enterprise which is not FedRAMP authorized. Customers requiring FedRAMP compliance must use Claude for Government (C4G) or access Claude models through FedRAMP-authorized CSPs (Bedrock GovCloud or Vertex Assured Workloads). Learn more here: **[Claude in Amazon Bedrock: Approved for use in FedRAMP High and DoD IL4/5 workloads](https://www.anthropic.com/news/claude-in-amazon-bedrock-fedramp-high)** ------------------------------------------------------------------------ ## 3. Cloud service providers and deployment ### How do I deploy Claude in Amazon Bedrock on AWS GovCloud / GCP Vertex in Assured Workloads? Work with your AWS / GCP account teams. Claude is available as a managed service through Bedrock/Vertex. These links can help to get you started: - **[Access Amazon Bedrock foundation models in AWS GovCloud (US)](https://docs.aws.amazon.com/bedrock/latest/userguide/model-access.html#model-access-govcloud)** - **[Claude on Vertex AI](https://platform.claude.com/docs/en/build-with-claude/claude-on-vertex-ai)** ### What is the pricing and commitment information for Claude on Vertex/Bedrock? Contact AWS directly for pricing and commitment requirements. Usage is typically pay-per-token through standard Bedrock pricing. Learn more here: **[Claude in Amazon Bedrock: Approved for use in FedRAMP High and DoD IL4/5 workloads](https://www.anthropic.com/news/claude-in-amazon-bedrock-fedramp-high)** **AWS Bedrock: [Amazon Bedrock pricing](https://aws.amazon.com/bedrock/pricing/)** **Google Cloud Vertex AI:** **[Cost of building and deploying AI models in Vertex AI](https://cloud.google.com/vertex-ai/generative-ai/pricing)** ------------------------------------------------------------------------ ## 4. Pricing and procurement ### What is the \$1/month government offer and who qualifies? The \$1/month offer is specifically for federal, judicial, and legislative agencies for C4G only. It does not extend to defense contractors, FFRDCs, or state/local governments, which receive standard pricing. ### Can we purchase directly from Anthropic or only through Carahsoft? Both options are available. Anthropic can sell directly, and/or resell / distribute via Carahsoft to specific government customers. ### How much does Claude cost? C4G is \$60/seat/month with usage limits and no additional consumption charges. Claude Enterprise is \$20/seat/month with additional charges for token consumption (PAYG). Other pricing plans are available here: **[Team and Enterprise plan pricing](https://claude.com/pricing#team-&-enterprise)** Learn more here: **[Offering expanded Claude access across all three branches of the U.S. government](https://www.anthropic.com/news/offering-expanded-claude-access-across-all-three-branches-of-government)** --- ## public-sector-faqs.md # Public Sector FAQs ## 1. Products and features ### What products are available to Public Sector customers? Select your product based on both your technical/functional requirements, and also your compliance/security/deployment environment requirements. Here is a list of options: [TABLE] ### What is Claude for Government (C4G)? Claude for Government is Anthropic's FedRAMP-High authorized product. Learn more here: **[Offering expanded Claude access across all three branches of the U.S. government](../19-Reference/offering-expanded-claude-access-across-all-three-branches-of-government-anthropi.md)** ### How do I access Claude for Government? Contact **[\[email protected\]](/cdn-cgi/l/email-protection#b5c5c0d7c6d0d6f5d4dbc1ddc7dac5dcd69bd6dad8)** or purchase through **[Carahsoft](https://carahsoft.com/anthropic/solutions)**. ### What is the difference between Claude Enterprise and Claude for Government? Claude Enterprise (CE) does not have FedRAMP authorization. Claude for Government (C4G) is FedRAMP-High authorized for mission-related federal work. C4G is not at feature parity with commercial Claude plans. ### Does Claude for Government include Claude Code? No. Customers purchase C4G separately and purchase API credits through Bedrock or Vertex for use with Claude Code in a FedRAMP authorized environment. ### Can I use Claude API in government environments? Yes. Claude API is available via Amazon Bedrock (in AWS GovCloud - FedRAMP High, and in IL6+) and Google Vertex with Assured Workloads (FedRAMP-High). For more information, see our **[Claude Code product page](https://claude.com/product/claude-code)**. ------------------------------------------------------------------------ ## 2. FedRAMP, Impact Levels, and compliance ### When should I use a FedRAMP authorized version? Customers should use Claude in FedRAMP when processing the following types of data: federal customer data, personally identifiable information (PII), controlled unclassified information (CUI), protected health information (PHI), mission-critical data (including ITAR/EAR), and federal contract information (FCI). ### What is Claude's FedRAMP authorization level? Claude for Government (C4G), and Claude via Amazon Bedrock in AWS GovCloud and Google Vertex with Assured Workloads are all FedRAMP-High. Learn more here: **[Claude in Amazon Bedrock: Approved for use in FedRAMP High and DoD IL4/5 workloads](../19-Reference/claude-in-amazon-bedrock-approved-for-use-in-fedramp-high-and-dod-il4-5-workload.md)** ### Are Claude's models themselves FedRAMP authorized? FedRAMP and DoD Impact Levels are certifications for cloud services (IaaS, PaaS, SaaS). AI models are software components, not cloud services. Claude models deploy within authorized environments, and customers maintain their compliance posture through the hosting platform. ### How can I get access to your FedRAMP authorization information and other associated documentation? Please submit a request for the package directly to FedRAMP using this **[FedRAMP Package Access Request Form](https://www.fedramp.gov/resources/documents/Agency_Package_Request_Form.pdf)**. ### Can I use Claude for CUI (Controlled Unclassified Information)? Yes, via AWS Bedrock GovCloud (IL5) or through the Claude for Government (C4G) FedRAMP-High environment. ### Can I use Claude in IL6/Secret environments? Yes. Claude is available in the AWS Secret region (IL6) via Amazon Bedrock. ### Is Claude CMMC compliant? CMMC is a certification of business practices protecting CUI data, not a certification of your tech stack. CMMC does require FedRAMP-Moderate (or higher) tools when dealing with CUI. Claude for Government meets this requirement. ### If a customer purchases Claude Enterprise via AWS Marketplace, is that FedRAMP? No. Claude Enterprise has no USG authorizations. Customers requiring FedRAMP compliance must use Claude for Government (C4G) or access Claude models through FedRAMP-authorized CSPs (Bedrock GovCloud or Vertex Assured Workloads). Learn more here: **[Claude in Amazon Bedrock: Approved for use in FedRAMP High and DoD IL4/5 workloads](../19-Reference/claude-in-amazon-bedrock-approved-for-use-in-fedramp-high-and-dod-il4-5-workload.md)** ------------------------------------------------------------------------ ## 3. Cloud service providers and deployment ### How do I deploy Claude in AWS Bedrock GovCloud? Work with your AWS account team to enable Claude models in your GovCloud environment. Claude is available as a managed service through Bedrock. Contact your AWS representative for setup guidance. ### What is the pricing and commitment information for Claude on Bedrock? Contact AWS directly for pricing and commitment requirements. Usage is typically pay-per-token through standard Bedrock pricing. Learn more here: **[Claude in Amazon Bedrock: Approved for use in FedRAMP High and DoD IL4/5 workloads](../19-Reference/claude-in-amazon-bedrock-approved-for-use-in-fedramp-high-and-dod-il4-5-workload.md)** ------------------------------------------------------------------------ ## 4. Pricing and procurement ### What is the \$1/month government offer and who qualifies? The \$1/month offer is specifically for federal, judicial, and legislative agencies for C4G only. It does not extend to defense contractors, FFRDCs, or state/local governments, which receive standard pricing. ### Can we purchase Claude through GSA? Yes. Claude is available through the GSA OneGov agreement and is resold via Carahsoft (carahsoft.com/anthropic/solutions). ### Can we purchase directly from Anthropic or only through Carahsoft? Both options are available. Anthropic can sell C4G directly, and it is also resold via Carahsoft. ### How much does Claude Code cost for government customers? Claude Code pricing is separate from C4G. Customers purchase Claude Code seats and separately purchase API credits through their chosen CSP (Bedrock or Vertex). Learn more here: **[Offering expanded Claude access across all three branches of the U.S. government](../19-Reference/offering-expanded-claude-access-across-all-three-branches-of-government-anthropi.md)** --- ## respond-to-an-enterprise-domain-claim-on-your-claude-account-8ab08c5da5.md # Respond to an Enterprise domain claim on your Claude account August 17, 2026 Copy for LLM If your organization has set up Claude Enterprise, they may claim your existing personal Claude account (Free, Pro, or Max) and move it into their workspace. This article explains what to expect and what your options are. **Note:** If your admin hasn't claimed your domain yet and you're exploring your options, see **[Move your personal Claude account to a Team or Enterprise organization](https://support.claude.com/en/articles/9267400-move-your-personal-claude-account-to-a-team-or-enterprise-organization)**. ## What it means when your domain is claimed Your organization’s admin has initiated a process called domain claiming. This means all personal Claude accounts tied to your company’s email domain (for example, *@yourcompany.com*) are being migrated into the organization’s Enterprise workspace. You’ll receive an email and an in-product notification letting you know that your account has been claimed, along with a deadline to choose what happens to your data. This deadline is at least 30 days from the date your admin initiates the claim. ## Your two options **Note:** If your organization has turned on HIPAA readiness or customer-managed encryption keys (CMEK), the merge and join option isn't available. Your only option is to join fresh. Export your data before the deadline if you want a copy. Your subscription is still canceled and refunded as described below. Learn more about **[HIPAA-ready Enterprise plans](https://support.claude.com/en/articles/13296973)** and **[customer-managed encryption keys](https://support.claude.com/en/articles/15505325)**. ### Merge and join Bring your existing data into a new account within your organization's Enterprise workspace. Some things don't move. Most importantly, custom skills and your connected apps stay behind. For the full list of what does and doesn’t move to your new account, see **[What moves when you migrate](https://support.claude.com/en/articles/9267400-move-your-personal-claude-account-to-a-team-or-enterprise-organization#h_4e63ef6e87)**. After the merge, your personal account is deactivated. **This can’t be undone**—once you merge, your data lives in your Enterprise account and your personal account no longer exists. ### Join fresh Start with a clean Enterprise account. None of your personal account data transfers. Before your deadline, you can **[export your data](https://support.claude.com/en/articles/9450526-how-can-i-export-my-claude-data)** if you want to keep a copy. Navigate to **[Settings \> Account](https://claude.ai/settings/account)** to request a data export. Note that exported data can’t be imported into your Enterprise account—it’s for your personal records only. ## What happens if you don’t choose **If you don’t make a choice before the deadline, you’ll get a fresh Enterprise account by default.** You won’t be able to access your personal account after the deadline. Sign in before the deadline to make your choice. ## What happens to your paid subscription If you have a Pro or Max subscription, it will be automatically canceled when you migrate or when the deadline passes. You’ll receive a prorated refund for any unused time. **Apple App Store subscriptions:** If you purchased your Pro or Max plan through the Apple App Store, we can’t cancel or refund it directly. You’ll need to cancel it yourself through your Apple ID settings: 1. Open the Settings app on your iPhone or iPad. 2. Tap your name at the top, then tap "Subscriptions." 3. Find your Claude subscription and tap "Cancel Subscription." If you don’t cancel your App Store subscription, Apple will continue to charge you even though your personal account has been deactivated. ## How to sign in after migration After migration, you’ll sign in to Claude using your organization’s single sign-on (SSO) provider. Go to claude.ai and sign in with your work email—you’ll be redirected to your company’s login page. **Can’t sign in?** You may not be set up in your company’s identity provider yet. Contact your IT admin for help. If you chose to merge, your conversations, projects, and files will be waiting in your new Enterprise account. ------------------------------------------------------------------------ ## Frequently asked questions ### Can I undo a merge? No. Merging is permanent. Once your personal account data is transferred to your Enterprise account, it can’t be moved back to a personal account. ### Can I keep my personal account and also join the Enterprise workspace? No. Once your domain is claimed, personal accounts on that domain can’t coexist with the Enterprise workspace. You’ll need to choose merge or join fresh. ### What if I use my personal email, not my work email? Domain claiming only affects accounts tied to your organization’s verified domain (your work email). If you have a separate Claude account on a personal email address (like Gmail or Yahoo), that account isn’t affected. ### Will my organization be able to see my old conversations? Data migrated from your personal account into an Enterprise organization will be accessible via the same mechanism as all other organization data. For more information, see **[Who owns and manages the data of my team?](https://support.claude.com/en/articles/9265372-who-owns-and-manages-the-data-of-my-team)** ### What if I’m not in my company’s identity provider? If you’re not in your organization’s IdP, you won’t be able to sign in to the Enterprise workspace after migration. Contact your IT admin to make sure you’re added before the deadline. You should still choose to merge or join fresh before the deadline so your preference is recorded. ### I have both a personal account and an existing Enterprise account. What happens? You can migrate your personal account to an existing Enterprise account; data from the individual account will be added to the Enterprise account. If the individual and Enterprise accounts have conflicting settings, the migrated account will use the Enterprise organization’s settings. --- ## set-up-single-sign-on-sso-890b8ba246.md # Set up single sign-on (SSO) Copy for LLM Single sign-on is available for Team plans, Enterprise plans, and Console organizations. This guide covers the steps to configure SSO for Team and Enterprise plans, and Claude Console organizations. ## Step 1: Review prerequisites and important considerations Before proceeding with SSO setup, complete the following: **Review the considerations guide:** Read **[Important considerations before enabling single sign-on (SSO) and JIT/SCIM provisioning](https://support.claude.com/en/articles/10276682-important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisioning)** to understand parent organizations, determine your setup path, and complete any prerequisite steps such as merging organizations. **Confirm you have the required role:** - For Team or Enterprise plans: You must be an Owner or Primary Owner - For Claude Console: You must be an Admin **Confirm you have access to the following:** - DNS settings for your company's email address domain - Your company's SSO Identity Provider (IdP) used to log in to third-party applications (e.g., Okta, Google Workspace, etc.) Please contact your organization's IT Administrator if you do not have permissions to manage Claude or company DNS settings. **Note:** WorkOS is Anthropic's provider for domain verification and SSO setup. More details can be found in **[Anthropic's Subprocessor List](https://trust.anthropic.com/subprocessors)**. You will be taken through a WorkOS setup flow when configuring SSO and provisioning features—find your Identity Provider in their **[Integration documentation](https://workos.com/docs/integrations)**. ------------------------------------------------------------------------ ## Step 2: Verify your domain(s) Domain verification proves that you own your company's domain. Once verified, you can configure SSO for accounts with your company's domain. You can verify multiple domains for a single organization, but all domains must be managed through a single IdP. We don't support verifying domains from separate IdPs within the same organization. **Note:** Verifying your domain by itself will not impact existing users' ability to access our products. End users’ access is only affected once SSO is set up and explicitly enforced. 1. Navigate to your **Organization and access** settings in Claude (**[claude.ai/admin-settings/organization](https://claude.ai/admin-settings/organization)**) or your **Identity and access** settings in Console (**[platform.claude.com/settings/identity](https://platform.claude.com/settings/identity)**) – note this page will only appear on Console if you've worked with Sales to enable SSO or completed a merge proposal. 2. In the **Domains** section, click “Add or edit domains.” 3. Enter the domain(s) you want to verify in the **Update organization email domains** modal and click the “+” button: 4. Click “Save” when you’re finished adding domains. 5. The domain(s) you added will now appear in the **Domains** section; click “Verify” to the right of the domain(s) to begin the verification process. 6. Enter your domain in the text box and click “Continue”: 7. The setup screen displays a TXT record. **Copy the full Value using the copy button**—it begins with `anthropic-domain-verification-` and is longer than what's visible in the box. In your DNS provider, add a TXT record to your domain and **Value** set to the copied string. The domain must match exactly what you entered in the previous step, including any subdomains. Add it alongside any existing TXT records; don't replace them. The value is case-sensitive, so paste it exactly. Please refer to your DNS provider's documentation on this topic. 1. **Important:** Save the TXT value before leaving the setup screen. Once the domain shows as Pending, the admin console doesn't display the value again. If you lose it, you'll need to remove and re-add the domain, which generates a new value. 8. Wait 10 minutes for your DNS change to propagate. - **Note:** *DNS changes can take 24-48 hours to propagate globally.* 9. When you see the green "Verified" badge, you can close the instructions page. 10. If your domain shows as "Pending," use the "Refresh" button. ### If your domain stays Pending Clicking "Refresh" re-checks your DNS; it won't show Verified until the published TXT record exactly matches the expected value. If it stays Pending after DNS has propagated, check the following: - **The record exists at the root.** Look up your domain's TXT records with a tool such as **[DNSChecker](https://dnschecker.org/#TXT)** and confirm a record beginning with `anthropic-domain-verification-` appears for `yourdomain.com` (not `www.yourdomain.com` or another subdomain). If it doesn't appear, the record may have been added at the wrong host or hasn't propagated yet. - **The value matches exactly.** The check is case-sensitive and requires the full string including the `anthropic-domain-verification-…=` prefix. A single character difference will keep it Pending. - **You haven't removed and re-added the domain.** Each re-add generates a new verification value. If you re-added the domain after publishing the TXT record, the published value no longer matches—you'll need to update the DNS record with the new value. If the record is correct and propagated but the status still shows Pending, contact Support. **Note:** Once your domain is verified, you'll see a **Restrict organization creation** toggle under **Security** on the Organization and access organization settings page. Enable this if you want to prevent users from creating new Claude or Console organizations—including personal accounts—using your verified domains. ------------------------------------------------------------------------ ## Step 3: Set up SSO with your Identity Provider 1. Navigate to your **Organization and access** settings in Claude (**[claude.ai/admin-settings/organization](https://claude.ai/admin-settings/organization)**) or your **Identity and access** settings in Console (**[platform.claude.com/settings/identity](https://platform.claude.com/settings/identity)**). 2. In the **Authentication** section, click “Setup SSO” (or “Manage SSO”). 3. Follow the setup guide provided for your Identity Provider (see below for additional guides). 4. At the end of these steps, you’ll be prompted to Test Single Sign-on to confirm there are no errors and the configuration is successful. 5. Once complete, navigate back to the **Organization and access** settings page for further configuration options. **Important:** SSO enforcement might result in users being unable to log in if they are not correctly assigned to the Anthropic app in the IdP. If you have more than one Claude/Console org connected to your “parent org,” you will want to consider creating a unique IdP Group for each. For more information, see **[enable group mappings](https://support.claude.com/en/articles/13133195-setting-up-jit-or-scim-provisioning#h_adee31eeba)**. For IdP-specific setup instructions, see: - **[Okta SAML](https://workos.com/docs/integrations/okta-saml)** - **[Entra ID SAML (formerly Azure AD)](https://workos.com/docs/integrations/entra-id-saml)** - **[Google SAML](https://workos.com/docs/integrations/google-saml)** - **[OneLogin SAML](https://workos.com/docs/integrations/onelogin-saml)** - **[JumpCloud SAML](https://workos.com/docs/integrations/jumpcloud-saml)** - **[Duo SAML](https://workos.com/docs/integrations/duo-saml/4-enter-duo-saml-settings-in-your-workos-dashboard)** ------------------------------------------------------------------------ ## Step 4: Choose to require SSO You can now choose to toggle on **Require SSO for Console** and/or **Require SSO for Claude,** on the **Organization and access** page, under the **Authentication** section: When SSO is required, users must use the “Continue with SSO” option to log in to their Claude/Console accounts. When SSO is not required, they will have the option to choose “Continue with SSO” or “Continue with email.” Before you decide, review **[What happens to existing users when SSO is enabled](https://support.claude.com/en/articles/10276682-important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisioning#h_644f467167)**. ------------------------------------------------------------------------ ## Step 5: Choose your provisioning approach Once SSO is enabled, you need to decide how users will be added to your organization by choosing an option within the **User provisioning** section of your **Organization and access** settings. **Invite only** is the default. Users are added and removed directly in your Claude or Console settings. Please see **[Manage members on Team and Enterprise plans](https://support.claude.com/en/articles/13133750-managing-members-on-team-and-enterprise-plans)**. **Just-in-Time (JIT) provisioning** can be enabled to automatically provision users when they first log in. By default, users assigned to your Anthropic IdP app first login, they will receive the User role. This is the simplest automated option and requires no additional configuration beyond selecting "Just-in-Time (JIT)" as your provisioning mode. ### Enable group mappings - when to configure additional provisioning features For more control over provisioning, see **[Set up JIT or SCIM provisioning](https://support.claude.com/en/articles/13133195-setting-up-jit-or-scim-provisioning)**. You'll want to review this guide if you need to: - Automatically assign roles or seat tiers based on IdP group membership. - Use SCIM directory sync for automatic provisioning and deprovisioning. - Manage access across multiple organizations (e.g., if you have both a Team/Enterprise organization and a Console organization linked to the same parent and need to control which users are provisioned to each). **Note:** We don't currently support IdP-initiated login for Claude Console organizations that share SSO settings with a Team or Enterprise plan organization. Users will be redirected to claude.ai with IdP-initiated login. As a workaround, if possible in your IdP, create a bookmark called "Claude Console" that links to platform.claude.com/login?sso=true to redirect users to Console for SP-initiated login. ------------------------------------------------------------------------ ## Updating your SSO certificate When your Identity Provider's X.509 signing certificate expires or is rotated, you'll need to update it in Claude or Console to maintain SSO functionality. 1. Navigate to your settings: - For Team and Enterprise plans: **[claude.ai/admin-settings/organization](https://claude.ai/admin-settings/organization)** - For Claude Console: **[platform.claude.com/settings/identity](https://platform.claude.com/settings/organization)** 2. In the **Authentication** section, click “Manage SSO.” 3. Find the **Metadata configuration** section and click “Edit.” 4. Update your certificate information and save your changes. 5. Click "Test sign-in" on the same page to confirm everything is working. **Important:** If **Require SSO** is turned on and your certificate has already expired, no one in your organization can sign in to update it, because every sign-in option routes through SSO. **[Contact Support](https://support.claude.com/en/articles/9015913)** from an Owner’s or Primary Owner’s email address and we’ll help you regain access so an Owner can update the certificate. To avoid this, note your certificate’s expiry date in your Identity Provider and rotate it ahead of time. ------------------------------------------------------------------------ ## Turning off SSO You can toggle **Require SSO for Claude** or **Require SSO for Console** off at any time. This will make SSO optional for all users. To fully disconnect SSO, click “Manage SSO” then “Reset connection.” This will end all users’ sessions and require them to sign back in via email login link. ## Locked out of admin access? If none of your Owners or Admins can sign in (for example, after a certificate expiry, an Identity Provider change, or a group mapping that removed your administrators), contact Support from an Owner’s or Primary Owner’s email address. We’ll verify your ownership of the organization and help you regain access so you can correct the configuration. --- ## set-up-single-sign-on-sso.md # Set up single sign-on (SSO) Single sign-on is available for Team plans, Enterprise plans, and Console organizations. This guide covers the steps to configure SSO for Team and Enterprise plans, and Claude Console organizations. ## Step 1: Review prerequisites and important considerations Before proceeding with SSO setup, complete the following: **Review the considerations guide:** Read **[Important considerations before enabling single sign-on (SSO) and JIT/SCIM provisioning](important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisi.md)** to understand parent organizations, determine your setup path, and complete any prerequisite steps such as merging organizations. **Confirm you have the required role:** - For Team or Enterprise plans: You must be an Owner or Primary Owner - For Claude Console: You must be an Admin **Confirm you have access to the following:** - DNS settings for your company's email address domain - Your company's SSO Identity Provider (IdP) used to log in to third-party applications (e.g., Okta, Google Workspace, etc.) Please contact your organization's IT Administrator if you do not have permissions to manage Claude or company DNS settings. **Note:** WorkOS is Anthropic's provider for domain verification and SSO setup. More details can be found in **[Anthropic's Subprocessor List](https://trust.anthropic.com/subprocessors)**. You will be taken through a WorkOS setup flow when configuring SSO and provisioning features – find your Identity Provider in their **[Integration documentation](https://workos.com/docs/integrations)**. ------------------------------------------------------------------------ ## Step 2: Verify your domain(s) Domain verification proves that you own your company's domain. Once verified, you can configure SSO for accounts with your company's domain. You can verify multiple domains for a single organization, but all domains must be managed through a single IdP. We don't support verifying domains from separate IdPs within the same organization. **Note:** Verifying your domain by itself will not impact existing users' ability to access our products. End users’ access is only affected once SSO is set up and explicitly enforced. 1. Navigate to your “Identity and access” settings in Claude (**[claude.ai/admin-settings/identity](http://claude.ai/admin-settings/identity)**) or Console (**[platform.claude.com/settings/identity](http://platform.claude.com/settings/identity)**) – note this page will only appear on Console if you've worked with Sales to enable SSO or completed a merge proposal. 2. In the **Domains** section, click “Add or edit domains.” 3. Enter the domain(s) you want to verify in the **Update organization email domains modal** and click the “+” button: 4. Click “Save” when you’re finished adding domains. 5. The domain(s) you added will now appear in the **Domains** section; click “Verify” to the right of the domain(s) to begin the verification process. 6. Enter your domain in the text box and click “Continue”: 7. This will generate a TXT record. Follow the instructions to add this TXT record to your domain provider. - If using a subdomain (e.g., subdomain.yourcompany.com), set your TXT record on that subdomain (e.g., \_acme-challenge.subdomain.yourco. mpany.com). 8. Wait 10 minutes for your DNS change to propagate. - *Note: DNS changes can take 24-48 hours to propagate globally.* 9. When you see the green "Verified" badge, you can close the instructions page. 10. If your domain shows as "Pending," use the "Refresh" button. **Note:** Once your domain is verified, you'll see a **Restrict organization creation** toggle under **Security** on the Identity and access organization settings page. Enable this if you want to prevent users from creating new Claude or Console organizations—including personal accounts—using your verified domains. ------------------------------------------------------------------------ ## Step 3: Set up SSO with your Identity Provider 1. Navigate to your Identity and access settings in Claude (**[claude.ai/admin-settings/identity](http://claude.ai/admin-settings/identity)**) or Console (**[platform.claude.com/settings/identity](http://platform.claude.com/settings/identit)**) 2. In the **Global access settings** section, click “Setup SSO” (or “Manage”). 3. Follow the setup guide provided for your Identity Provider (see below for additional guides). 4. At the end of these steps, you’ll be prompted to Test Single Sign-on to confirm there are no errors and the configuration is successful. 5. Once complete, navigate back to the Identity and access settings page for further configuration options. **Important:** SSO enforcement might result in users being unable to log in if they are not correctly assigned to the Anthropic app in the IdP. If you have more than one Claude/Console org connected to your “parent org,” you will want to consider creating a unique IdP Group for each. For more information, see **[enable group mappings](../13-Enterprise-Admin/setting-up-jit-or-scim-provisioning.md#h_adee31eeba)**. For IdP-specific setup instructions, see: - **[Okta SAML](https://workos.com/docs/integrations/okta-saml)** - **[Entra ID SAML (formerly Azure AD)](https://workos.com/docs/integrations/entra-id-saml)** - **[Google SAML](https://workos.com/docs/integrations/google-saml)** - **[OneLogin SAML](https://workos.com/docs/integrations/onelogin-saml)** - **[JumpCloud SAML](https://workos.com/docs/integrations/jumpcloud-saml)** - **[Duo SAML](https://workos.com/docs/integrations/duo-saml/4-enter-duo-saml-settings-in-your-workos-dashboard)** ------------------------------------------------------------------------ ## Step 4: Choose to require SSO You can now choose to toggle on **Require SSO for Console** and/or **Require SSO for Claude,** on the Identity and access page, under the **Global access settings** section: When SSO is required, users must use the “Continue with SSO” option to access Claude/Console. When SSO is not required, they will have the option to choose “Continue with SSO” or “Continue with email.” Before you decide, review **[What happens to existing users when SSO is enabled](important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisi.md#h_644f467167)**. ------------------------------------------------------------------------ ## Step 5: Choose your provisioning approach Once SSO is enabled, you need to decide how users will be added to your organization. This is controlled by the **Provisioning mode** setting in the **Global access settings** section of your Identity and access settings. **Invite only** is the default. Users are added and removed directly in your Claude or Console settings. Please see **[Manage members on Team and Enterprise plans](../17-Billing-Plans/managing-members-on-team-and-enterprise-plans.md)**. **JIT (Just-in-Time) provisioning** can be enabled to automatically provision users when they first log in. By default, users assigned to your Anthropic IdP app first login, they will receive the User role. This is the simplest automated option and requires no additional configuration beyond selecting "Approve automatically (JIT)" as your provisioning mode. ### Enable group mappings - when to configure additional provisioning features For more control over provisioning, see **[Set up JIT or SCIM provisioning](../13-Enterprise-Admin/setting-up-jit-or-scim-provisioning.md)**. You'll want to review this guide if you need to: - Automatically assign roles or seat tiers based on IdP group membership. - Use SCIM directory sync for automatic provisioning and deprovisioning. - Manage access across multiple organizations (e.g., if you have both a Team/Enterprise organization and a Console organization linked to the same parent and need to control which users are provisioned to each). **Note:** We don't currently support IdP-initiated login for Claude Console organizations that share SSO settings with a Team or Enterprise plan organization. Users will be redirected to claude.ai with IdP-initiated login. As a workaround, if possible in your IdP, create a bookmark called "Claude Console" that links to platform.claude.com/login?sso=true to redirect users to Console for SP-initiated login. ------------------------------------------------------------------------ ## Updating your SSO certificate When your Identity Provider's X.509 signing certificate expires or is rotated, you'll need to update it in Claude or Console to maintain SSO functionality. 1. Navigate to your Identity and access settings: - For Team and Enterprise plans: **[claude.ai/admin-settings/identity](http://claude.ai/admin-settings/identity)** - For Claude Console: **[platform.claude.com/settings/identity](http://platform.claude.com/settings/identity)** 2. In the **Global access settings** section, click “Manage SSO.” 3. Select “Metadata Config.” 4. Click “Edit.” 5. Update your certificate information and save your changes. 6. Click "Test sign-in" on the same page to confirm everything is working. ------------------------------------------------------------------------ ## Turning off SSO You can toggle **Require SSO for Claude** or **Require SSO for Console** off at any time. This will make SSO optional for all users. To fully disconnect SSO, click “Manage SSO” then “Reset.” This will end all users’ sessions and require them to sign back in via email login link. --- ## set-up-your-design-system-in-claude-design-3ce3683e53.md # Set up your design system in Claude Design Copy for LLM A design system captures your colors, typography, components, and layout patterns, so Claude applies them to every new design and deck. Claude extracts them from the assets you provide, like codebases, slide decks, or other design references. Design systems are available in beta on Pro, Max, Team, and Enterprise plans. They're on by default on Pro, Max, and Team plans. On Enterprise plans, they're off until an owner turns on **Design systems** in **[Organization settings \> Artifacts](https://claude.ai/admin-settings/artifacts)**. Standalone Claude Design at claude.ai/design has its own separate setting. This guide is for the designer or brand owner who will set up the design system. On Team and Enterprise plans, you only need to do this once, and everyone's work picks it up after that. ## Before you start - On Team and Enterprise plans, **Design systems** needs to be on for your organization, and an owner may limit who can publish or set the default. - You’ll need at least one of the following as source material: - A codebase with your design system or component library - A slide deck or document that reflects your visual identity - Brand guideline assets (logos, color palettes, typography specs) ------------------------------------------------------------------------ ## Create a design system ### From a chat Ask Claude to build a design system from your connected apps, uploaded files, Figma files, decks, logos, and fonts. This works best for brand design systems with fonts, colors, and guidelines. ### From Claude Code If your design system already exists as React components, run /design-sync in Claude Code. It reads your tokens and components directly, and works best for product design systems in code. ### Bring over a design system from claude.ai/design 1. Open the "Design" tab at the bottom of the sidebar. 2. Click "Migrate team design systems" in the banner. Each design system becomes an artifact Claude can use in any chat, including in Claude Code. Migrated design systems may need some cleanup, so each one shows a banner where you can click "Let Claude clean it up," and Claude tidies its guide, tokens, and components. ## Manage your design systems Manage your design systems in **[Settings \> Design systems](https://claude.ai/settings/design-systems)**. On Enterprise plans, admins can reserve publishing, setting the organization default, and deleting design systems for specific users. Learn more in the **[Artifacts admin guide for Team and Enterprise plans](https://support.claude.com/en/articles/16994751)**. ------------------------------------------------------------------------ ## Set up a design system at claude.ai/design These steps use standalone Claude Design. ### Create or switch to your organization 1. Open **[Claude Design](https://claude.ai/design)**. 2. In the lower left corner of the project picker, click the current organization name. 3. Select your organization, or create a new one. 4. Complete the onboarding flow you're redirected to. ### Upload your brand and product assets During onboarding, or afterward from your organization settings, upload the assets that define your brand and product. Claude analyzes them and extracts a reusable design system. - **Codebases:** If your design system lives in code, like a React component library, link or upload the repository. Claude reads the components and styles. - **Prototypes:** Screenshots, web flows, and existing design files. - **Slide decks or documents:** Even a well-designed PowerPoint or PDF that reflects your brand can work. Claude extracts colors, layout patterns, and typographic choices. - **Individual assets:** Logos, color palette files, typography specimens. You only need one source to get started, but more sources give Claude more to work with. ### Review the generated design system After uploading, Claude generates a design system for your organization. This typically includes: - **Color palette:** Primary, secondary, and accent colors extracted from your assets. - **Typography:** Font families, sizes, and weights. - **Components:** Buttons, cards, navigation elements, and other reusable UI patterns. - **Layout patterns:** Spacing, grid systems, and page structures. To validate it, create a test project and check whether the output matches your brand. Try prompts like: - "Create a landing page for \[your product\]." - "Design a dashboard showing \[relevant metrics\]." - "Make a one-pager about \[a topic your team commonly presents on\]." ### Make it available to your team When you're happy with the design system, turn on the "Published" toggle. After publishing, projects created from the Claude Design home screen in your organization use your design system instead of the default. ## Update your design system When your design system changes, you can update it within Claude Design. From your Claude Design organization settings, click the “Open” button next to the design system you want to edit. Click the “Remix” button in the upper right corner to open the chat interface on the left side of the window. From here, you can work with Claude to change your design system. ------------------------------------------------------------------------ ## Tips for best results - **Include real examples, not just specs.** A finished landing page or marketing site tells Claude more about your brand’s feel than a color palette alone. - **Iterate.** If the first extraction doesn’t capture your brand well, try uploading additional or different assets. --- ## setting-up-jit-or-scim-provisioning-to-manage-user-assignments-on-team-or-enterp-f973043c5a.md # Set up JIT or SCIM provisioning Copy for LLM This guide covers how to configure user provisioning and role assignment for your Claude or Claude Console organization. JIT provisioning is available for Team plans, Enterprise plans, and Console organizations. SCIM provisioning is available for Enterprise and Console organizations only. **Before you begin:** This guide assumes you have already completed the steps in **[Set up single sign-on (SSO)](https://support.claude.com/en/articles/13132885-setting-up-single-sign-on-sso)**, including domain verification and SSO configuration with your Identity Provider (IdP), and you have an Admin (Console) or Owner (Claude) role. ------------------------------------------------------------------------ ## Step 1: Choose your provisioning mode Once SSO is configured, you need to decide how users will be provisioned to your organization. This is controlled via the **User provisioning** section in **[Organization settings \> Organization and access](https://claude.ai/admin-settings/organization)**. ### Provisioning options **Invite only** is the default. Users are added and removed directly in Claude or Console settings. **Just-in-time (JIT):** Users assigned to your Anthropic IdP app are automatically provisioned when they first log in. This option is available to all plans. **SCIM directory sync:** Users are automatically provisioned and deprovisioned based on assignments in your IdP, without requiring them to log in first. SCIM is available for Enterprise plans and Console organizations with their own parent organization or joined to an Enterprise parent organization. SCIM is not available for Team plans or Console organizations joined to a Team plan's parent organization. When SCIM directory sync is on, Claude sends each newly provisioned member a welcome email. To turn this off, Owners and Primary Owners can navigate to **Organization settings \> Organization and access \> User provisioning**, find **SCIM directory sync**, and turn off "Send a welcome email to new members." **Note:** Claude doesn't send this welcome email to organizations with additional data-handling or compliance requirements such as customer-managed encryption keys (CMEK), HIPAA, or FERPA, so the setting isn't shown for those organizations. Changes apply to members provisioned after you save, and emails already sent stay delivered. ### Provisioning behavior overview Use this table to help decide which provisioning mode is right for your organization: [TABLE] **Note:** To remove a JIT user permanently, remove them in Claude and unassign them in your IdP. A user you remove only in Claude will be re-added the next time they log in with SSO. Both JIT and SCIM can be combined with **Enable group mappings** to control role or seat tier assignment based on IdP group membership. If you select either of these options for your provisioning mode, **Enable group mappings** will appear within the **User provisioning** section: **Important:** Group mappings set a user’s role type and seat tier only. Users with the Custom role get their permissions from groups in Claude, and those groups sync from your IdP only when your provisioning mode is SCIM directory sync. With JIT, you need to create groups and add users to them manually in **[Organization settings \> Groups](https://claude.ai/admin-settings/groups)**. If you map an IdP group to the Custom role under JIT without doing this, those users have no permissions when they log in. Learn more about **[managing groups on Enterprise plans](https://support.claude.com/en/articles/13799932)**. ### Available roles and seat tiers [TABLE] 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](https://support.claude.com/en/articles/13393991-purchasing-and-managing-seats-on-enterprise-plans)**. ------------------------------------------------------------------------ ## Step 2: Set up SCIM directory sync (if using SCIM) **Note:** Skip this step if you're using Invite only or JIT provisioning. If you chose SCIM as your provisioning mode, you need to establish the connection between your Identity Provider and Anthropic before enabling it. 1. Navigate to your **Organization and access** settings in Claude (**[claude.ai/admin-settings/organization](https://claude.ai/admin-settings/organization)**) or your **Identity and access** settings in Console (**[platform.claude.com/settings/identity](https://platform.claude.com/settings/identity)**) 2. In the **User provisioning** section, click “Setup SCIM” (or “Manage SCIM”)next to **SCIM directory sync**. 3. Follow the WorkOS setup guide to configure SCIM in your Identity Provider. You'll need to copy values from WorkOS into your IdP's Anthropic application. **‼️ When you reach the IdP Group step, pause to review Steps 3 and 4 of this guide, alongside the other guides.** For IdP-specific JIT / SCIM setup instructions, see: - **[Okta SAML](https://workos.com/docs/integrations/okta-saml)** / **[OKTA SCIM](https://workos.com/docs/integrations/okta-scim)** - **[Entra ID SAML](https://workos.com/docs/integrations/entra-id-saml)** / **[Entra ID SCIM](https://workos.com/docs/integrations/entra-id-scim)** - **[Google SAML](https://workos.com/docs/integrations/google-saml)** / **[Directory Sync](https://workos.com/docs/integrations/google-directory-sync)** - **[OneLogin SAML](https://workos.com/docs/integrations/onelogin-saml)** / **[OneLogin SCIM](https://workos.com/docs/integrations/onelogin-scim)** - **[JumpCloud SAML](https://workos.com/docs/integrations/jumpcloud-saml)** / **[JumpCloud SCIM](https://workos.com/docs/integrations/jumpcloud-scim)** - See additional IdPs **[here](https://workos.com/docs/integrations)** Once your IdP is connected, continue to Step 3. ------------------------------------------------------------------------ ## Step 3: Configure provisioning mode and enable group mappings 1. Find the **User provisioning** section of your settings. 2. Select your chosen option: 1. **Invite only**: New members can only join if manually invited by an existing member. SSO access alone won't add them to your org. 2. **Just-in-time (JIT)**: Allow people with SSO access to join when they first log in. Each new member uses one of your available seats. 3. **SCIM directory sync**: Add or remove members automatically as your directory changes. Your org always stays current. 3. If you selected “Just-in-time (JIT)” or “SCIM directory sync,” do NOT click “Save changes” immediately. You must first ensure all users are assigned to your Anthropic application in your IdP. 4. Once you’ve confirmed all users are assigned in your IdP you can either: 1. Click “Save changes” to complete the set up and trigger the initial provisioning, or 2. Toggle on **Enable group mappings** and move to Step 4. **Important**: Saving before users are properly assigned will result in those users being deprovisioned from the organization. Where it's available, the admin console shows a preview of what the sync will change, including how many members will be removed, before it applies. Review it before you confirm, and cancel if the removal count is higher than you expect. Learn more about **[how SCIM sync works](https://support.claude.com/en/articles/14499648-how-scim-sync-works-for-enterprise-organizations)**. ------------------------------------------------------------------------ ## Step 4: Configure groups in your Identity Provider and map groups to roles and seat types 1. Create groups in your IdP for each role you want to assign. Unless you're on the single-seat Enterprise plan, create groups for each seat type as well. 1. While there are no longer naming requirements for these groups, we recommend including something in the group name (e.g., `anthropic-claude-` or `anthropic-console-`) to make them easier to identify. 2. Add users to the groups you created, ensuring at least one user (including yourself) is in a group that will be mapped to an Admin (Console) or Owner (Claude) role. 3. Return to your **Organization and access** or **Identity and access** settings in Claude or Console, and find **User provisioning**. 4. Toggle **Enable group mappings** on (if it’s not already): 5. In the **Enable group mappings** section, click “Add” next to each role and select the corresponding group from your IdP in the dropdown. 1. When using group mappings, you *must* assign all users to a role-based group in order to ensure they’re provisioned an account. Assigning users to seat-tier based groups is optional. 2. You can map an IdP group to the “Custom” role. Users assigned this role have no default permissions; their access is determined entirely by the custom roles assigned to their groups in Claude. If you use JIT, add these users to groups manually in **[Organization settings \> Groups](https://claude.ai/admin-settings/groups)** before they log in, since JIT doesn't sync group memberships from your IdP. 6. **For all plans except single-seat Enterprise:** In the **Assign seat tiers to IdP groups** section (optional), click "Add" next to each seat type and select the corresponding group from your IdP. Users who aren’t in any seat tier group aren’t removed. Existing users keep their current seat type. New users receive the highest seat type that still has an unassigned purchased seat (for example, Premium while unassigned Premium seats remain, then Standard), and are added with no seat if none is available. 1. **For single-seat Enterprise:** Seat type mapping does not apply. All provisioned users are automatically assigned an Enterprise seat, provided one is available in your organization. 7. Verify all necessary groups are mapped to the appropriate roles and seat types. 8. Click “Save changes.” 1. **Note:** Microsoft Entra only pushes SCIM changes every 40 minutes, so there may be a delay before changes appear. You can check which users are synced from your IdP by clicking "Manage SCIM" and viewing the Directory. Those users in the Directory will be provisioned to Claude / Console. **Important:** All users who need access must be assigned to the appropriate groups before you save your group mappings configuration. These users should already be assigned to your Anthropic application in your IdP from when you enabled SSO. ### How the Primary Owner role works with SCIM - Your organization's Primary Owner is exempt from SCIM reconciliation. If the Primary Owner account is not present in the IdP directory, or is not a member of any group mapped to a role, it will be skipped when SCIM syncs. The Primary Owner's membership and role are preserved. - This exemption applies only to the single Primary Owner role. Owner and Admin roles are **not** exempt and **must** be in a group mapped to a role, or they will be removed when SCIM group mappings are enabled. - The Primary Owner role cannot be assigned via SCIM group mappings. It can only be transferred manually from **[Organization settings \> Members](https://claude.ai/admin-settings/members)**. Set your intended Primary Owner before enabling SCIM. - The Primary Owner is not exempt from SSO sign-in enforcement. SSO enforcement is applied by email domain; if the Primary Owner's email is on an enforced domain, they must authenticate through SSO. ------------------------------------------------------------------------ ## Troubleshooting ### Users assigned correctly and showing in the directory but aren’t being added to the Claude as members? Verify you have enough seats purchased and available to add members to your org. 1. Check the number of available seats shown in **[Organization settings \> Organization and access](https://claude.ai/admin-settings/organization)** and purchase additional seats if needed (see our guides for **[Team plans](https://support.claude.com/en/articles/12004354-purchasing-and-managing-seats)** and **[Enterprise plans](https://support.claude.com/en/articles/13393991-purchasing-and-managing-seats-on-enterprise-plans)**). 2. Once you have available seats, go back to the Organization and access page and click “Sync now,” next to **Directory sync (SCIM)**. This will trigger a sync to provision accounts for those users not yet added as members. ### Users aren't being provisioned with the correct role 1. Verify the user is assigned to the correct group in your IdP. 2. Verify the group is mapped to the correct role in your **Organization and access** settings. 3. **For JIT:** The user needs to log out and log back in for role changes to take effect. 4. **For SCIM:** Click "Sync" to prompt an immediate sync, or wait for the automatic sync cycle: ### Users mapped to the Custom role can't access anything after logging in This happens when your provisioning mode is JIT and an IdP group is mapped to the Custom role. JIT assigns the role type but doesn't sync group memberships from your IdP, so these users aren't in any group with a custom role attached and have no permissions. To fix this, do one of the following: 1. Add the affected users to the appropriate groups manually in **[Organization settings \> Groups](https://claude.ai/admin-settings/groups)**. Learn more about **[managing groups on Enterprise plans](https://support.claude.com/en/articles/13799932)**. 2. Switch your provisioning mode to SCIM directory sync, which syncs groups and their memberships from your IdP. Learn more about **[how SCIM sync works](https://support.claude.com/en/articles/14499648)**. ### I lost Admin/Owner access after enabling group mappings This happens when the person configuring group mappings isn't assigned to a group mapped to an Admin or Owner role, causing their permissions to be downgraded to User. To fix this, do one of the following: **Option 1: Have another Admin/Owner reinstate your role** 1. Contact another Admin or Owner of your organization. 2. Ask them to navigate to **[Organization settings \> Organization](https://claude.ai/admin-settings/organization)** (for Claude) or **[Settings \> Members](https://platform.claude.com/settings/members)** (for Console). 3. Have them change your role back to Admin or Owner. **Option 2: Fix via your Identity Provider** 1. In your IdP, assign yourself to a group with the correct prefix that maps to an Admin or Owner role. 2. **For JIT:** Log out and log back in to regain access. 3. **For SCIM:** Ask another Admin or Owner to click "Sync" in the **Organization and access** settings, or wait for the automatic sync cycle. --- ## setting-up-jit-or-scim-provisioning-to-manage-user-assignments-on-team-or-enterp.md # Set up JIT or SCIM provisioning JIT provisioning is available for Team plans, Enterprise plans, and Console organizations. SCIM provisioning is available for Enterprise and Console organizations only. This guide covers how to configure user provisioning and role assignment for your Claude or Claude Console organization. **Before you begin:** This guide assumes you have already completed the steps in **[Set up single sign-on (SSO)](setting-up-single-sign-on-sso.md)**, including domain verification and SSO configuration with your Identity Provider (IdP), and you have an Admin (Console) or Owner (Claude) role. ------------------------------------------------------------------------ ## Step 1: Choose your provisioning mode Once SSO is configured, you need to decide how users will be provisioned to your organization. This is controlled by the **Provisioning mode** setting in **[Organization](https://claude.ai/admin-settings/organization)** **[settings \> Identity and access](https://claude.ai/admin-settings/identity)**. ### Provisioning options **Invite only** is the default. Users are added and removed directly in Claude or Console settings. **Approve automatically (JIT):** Users assigned to your Anthropic IdP app are automatically provisioned when they first log in. This option is available to all plans. **Sync with SCIM:** Users are automatically provisioned and deprovisioned based on assignments in your IdP, without requiring them to log in first. SCIM is available for Enterprise plans and Console organizations with their own parent organization or joined to an Enterprise parent organization. SCIM is not available for Team plans or Console organizations joined to a Team plan's parent organization. ### Provisioning behavior overview Use this table to help decide which provisioning mode is right for your organization: [TABLE] Both JIT and SCIM can be combined with **Enable group mappings** to control role or seat tier assignment based on IdP group membership. If you select either of these options for your provisioning mode, **Enable group mappings** will appear within that section: ### Available roles and seat tiers [TABLE] 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](../17-Billing-Plans/purchasing-and-managing-seats-on-enterprise-plans.md)**. ------------------------------------------------------------------------ ## Step 2: Set up SCIM directory sync (if using SCIM) **Note:** Skip this step if you're using Invite only or JIT provisioning. If you chose SCIM as your provisioning mode, you need to establish the connection between your Identity Provider and Anthropic before enabling it. 1. Navigate to your Identity and access settings in Claude (**[claude.ai/admin-settings/identity](http://claude.ai/admin-settings/identity)**) or Console (**[platform.claude.com/settings/identity](http://platform.claude.com/settings/identit)**) 2. In the **Global access settings** section, click “Setup SCIM” (or “Manage SCIM”) next to **Directory sync (SCIM)**. 3. Follow the WorkOS setup guide to configure SCIM in your Identity Provider. You'll need to copy values from WorkOS into your IdP's Anthropic application. **‼️ When you reach the IdP Group step, pause to review Steps 3 and 4 of this guide, alongside the other guides.** For IdP-specific JIT / SCIM setup instructions, see: - **[Okta SAML](https://workos.com/docs/integrations/okta-saml)** / **[OKTA SCIM](https://workos.com/docs/integrations/okta-scim)** - **[Entra ID SAML](https://workos.com/docs/integrations/entra-id-saml)** / **[Entra ID SCIM](https://workos.com/docs/integrations/entra-id-scim)** - **[Google SAML](https://workos.com/docs/integrations/google-saml)** / **[Directory Sync](https://workos.com/docs/integrations/google-directory-sync)** - **[OneLogin SAML](https://workos.com/docs/integrations/onelogin-saml)** / **[OneLogin SCIM](https://workos.com/docs/integrations/onelogin-scim)** - **[JumpCloud SAML](https://workos.com/docs/integrations/jumpcloud-saml)** / **[JumpCloud SCIM](https://workos.com/docs/integrations/jumpcloud-scim)** - See additional IdPs **[here](https://workos.com/docs/integrations)** Once your IdP is connected, continue to Step 3. ------------------------------------------------------------------------ ## Step 3: Configure provisioning mode and enable group mappings 1. In the **Global access settings** section of your Identity and access settings, find **Provisioning mode**. 2. Select your chosen option from the dropdown: 1. **Invite only**: New members can only join if manually invited by an existing member. SSO access alone won't add them to your org. 2. **Approve automatically (JIT)**: Allow people with SSO access to join when they first log in. Each new member uses one of your available seats. 3. **Sync with SCIM**: Add or remove members automatically as your directory changes. Your org always stays current. 3. If you selected “Approve automatically (JIT)” or “Sync with SCIM,” do NOT click “Save changes” immediately. You must first ensure all users are assigned to your Anthropic application in your IdP. 4. Once you’ve confirmed all users are assigned in your IdP you can either: 1. Click “Save changes” to complete the set up and trigger the initial provisioning, or 2. Toggle on **Enable group mappings** and move to Step 4. **Important**: Saving before users are properly assigned will result in those users being deprovisioned from the organization. ------------------------------------------------------------------------ ## Step 4: Configure groups in your Identity Provider and map groups to roles and seat types 1. Create groups in your IdP for each role you want to assign. Unless you're on the single-seat Enterprise plan, create groups for each seat type as well. 1. While there are no longer naming requirements for these groups, we recommend including something in the group name (e.g., `anthropic-claude-` or `anthropic-console-`) to make them easier to identify. 2. Add users to the groups you created, ensuring at least one user (including yourself) is in a group that will be mapped to an Admin (Console) or Owner (Claude) role. 3. Return to your Identity and access settings in Claude or Console, and find **Provisioning mode**. 4. Toggle **Enable group mappings** on (if it’s not already): 5. In the **Enable group mappings** section, click “Add” next to each role and select the corresponding group from your IdP in the dropdown. 1. **Note:** When using group mappings, you *must* assign all users to a role-based group in order to ensure they’re provisioned an account. Assigning users to seat-tier based groups is optional. 6. **For all plans except single-seat Enterprise:** In the **Assign seat tiers to IdP groups** section (optional), click "Add" next to each seat type and select the corresponding group from your IdP. If a user isn't assigned to a seat type group, they will be assigned to the highest available type by default. 1. **For single-seat Enterprise:** Seat type mapping does not apply. All provisioned users are automatically assigned an Enterprise seat, provided one is available in your organization. 7. Verify all necessary groups are mapped to the appropriate roles and seat types. 8. Click “Save changes.” 1. **Note:** Microsoft Entra only pushes SCIM changes every 40 minutes, so there may be a delay before changes appear. You can check which users are synced from your IdP by clicking "Manage SCIM" and viewing the Directory. Those users in the Directory will be provisioned to Claude / Console. **Important:** All users who need access must be assigned to the appropriate groups before you save your group mappings configuration. These users should already be assigned to your Anthropic application in your IdP from when you enabled SSO. ------------------------------------------------------------------------ ## Troubleshooting ### Users assigned correctly and showing in the directory but aren’t being added to the Claude as members? Verify you have enough seats purchased and available to add members to your org. 1. Check the number of available seats shown in **[Organization](https://claude.ai/admin-settings/organization)** **[settings \> Billing](https://claude.ai/admin-settings/billing)** and purchase additional seats if needed (see our guides for **[Team plans](https://support.claude.com/en/articles/12004354-purchasing-and-managing-seats)** and **[Enterprise plans](../17-Billing-Plans/purchasing-and-managing-seats-on-enterprise-plans.md)**). 2. Once you have available seats, go back to the Identity and access page and click “Sync now,” next to **Directory sync (SCIM)**. This will trigger a sync to provision accounts for those users not yet added as members. ### Users aren't being provisioned with the correct role 1. Verify the user is assigned to the correct group in your IdP. 2. Verify the group is mapped to the correct role in your Identity and access settings. 3. **For JIT:** The user needs to log out and log back in for role changes to take effect. 4. **For SCIM:** Click "Sync Now" to prompt an immediate sync, or wait for the automatic sync cycle. ### I lost Admin/Owner access after enabling group mappings This happens when the person configuring group mappings isn't assigned to a group mapped to an Admin or Owner role, causing their permissions to be downgraded to User. To fix this: **Option 1: Have another Admin/Owner reinstate your role** 1. Contact another Admin or Owner of your organization. 2. Ask them to navigate to **[Organization settings \> Organization](https://claude.ai/admin-settings/organization)** (for Claude) or **[Settings \> Members](https://platform.claude.com/settings/members)** (for Console). 3. Have them change your role back to Admin or Owner. **Option 2: Fix via your Identity Provider** 1. In your IdP, assign yourself to a group with the correct prefix that maps to an Admin or Owner role. 2. **For JIT:** Log out and log back in to regain access. 3. **For SCIM:** Ask another Admin or Owner to click "Sync Now" in the Identity and access settings, or wait for the automatic sync cycle. --- ## setting-up-single-sign-on-on-the-claude-console.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. --- ## setting-up-single-sign-on-sso-3b8067927a.md # Set up single sign-on (SSO) Copy for LLM Single sign-on is available for Team plans, Enterprise plans, and Console organizations. This guide covers the steps to configure SSO for Team and Enterprise plans, and Claude Console organizations. ## Step 1: Review prerequisites and important considerations Before proceeding with SSO setup, complete the following: **Review the considerations guide:** Read **[Important considerations before enabling single sign-on (SSO) and JIT/SCIM provisioning](https://support.claude.com/en/articles/10276682-important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisioning)** to understand parent organizations, determine your setup path, and complete any prerequisite steps such as merging organizations. **Confirm you have the required role:** - For Team or Enterprise plans: You must be an Owner or Primary Owner - For Claude Console: You must be an Admin **Confirm you have access to the following:** - DNS settings for your company's email address domain - Your company's SSO Identity Provider (IdP) used to log in to third-party applications (e.g., Okta, Google Workspace, etc.) Please contact your organization's IT Administrator if you do not have permissions to manage Claude or company DNS settings. **Note:** WorkOS is Anthropic's provider for domain verification and SSO setup. More details can be found in **[Anthropic's Subprocessor List](https://trust.anthropic.com/subprocessors)**. You will be taken through a WorkOS setup flow when configuring SSO and provisioning features—find your Identity Provider in their **[Integration documentation](https://workos.com/docs/integrations)**. ------------------------------------------------------------------------ ## Step 2: Verify your domain(s) Domain verification proves that you own your company's domain. Once verified, you can configure SSO for accounts with your company's domain. You can verify multiple domains for a single organization, but all domains must be managed through a single IdP. We don't support verifying domains from separate IdPs within the same organization. **Note:** Verifying your domain by itself will not impact existing users' ability to access our products. End users’ access is only affected once SSO is set up and explicitly enforced. 1. Navigate to your **Organization and access** settings in Claude (**[claude.ai/admin-settings/organization](https://claude.ai/admin-settings/organization)**) or your **Identity and access** settings in Console (**[platform.claude.com/settings/identity](https://platform.claude.com/settings/identity)**) – note this page will only appear on Console if you've worked with Sales to enable SSO or completed a merge proposal. 2. In the **Domains** section, click “Add or edit domains.” 3. Enter the domain(s) you want to verify in the **Update organization email domains** modal and click the “+” button: 4. Click “Save” when you’re finished adding domains. 5. The domain(s) you added will now appear in the **Domains** section; click “Verify” to the right of the domain(s) to begin the verification process. 6. Enter your domain in the text box and click “Continue”: 7. The setup screen displays a TXT record. **Copy the full Value using the copy button**—it begins with `anthropic-domain-verification-` and is longer than what's visible in the box. In your DNS provider, add a TXT record to your domain and **Value** set to the copied string. The domain must match exactly what you entered in the previous step, including any subdomains. Add it alongside any existing TXT records; don't replace them. The value is case-sensitive, so paste it exactly. Please refer to your DNS provider's documentation on this topic. 1. **Important:** Save the TXT value before leaving the setup screen. Once the domain shows as Pending, the admin console doesn't display the value again. If you lose it, you'll need to remove and re-add the domain, which generates a new value. 8. Wait 10 minutes for your DNS change to propagate. - **Note:** *DNS changes can take 24-48 hours to propagate globally.* 9. When you see the green "Verified" badge, you can close the instructions page. 10. If your domain shows as "Pending," use the "Refresh" button. ### If your domain stays Pending Clicking "Refresh" re-checks your DNS; it won't show Verified until the published TXT record exactly matches the expected value. If it stays Pending after DNS has propagated, check the following: - **The record exists at the root.** Look up your domain's TXT records with a tool such as **[DNSChecker](https://dnschecker.org/#TXT)** and confirm a record beginning with `anthropic-domain-verification-` appears for `yourdomain.com` (not `www.yourdomain.com` or another subdomain). If it doesn't appear, the record may have been added at the wrong host or hasn't propagated yet. - **The value matches exactly.** The check is case-sensitive and requires the full string including the `anthropic-domain-verification-…=` prefix. A single character difference will keep it Pending. - **You haven't removed and re-added the domain.** Each re-add generates a new verification value. If you re-added the domain after publishing the TXT record, the published value no longer matches—you'll need to update the DNS record with the new value. If the record is correct and propagated but the status still shows Pending, contact Support. **Note:** Once your domain is verified, you'll see a **Restrict organization creation** toggle under **Security** on the Organization and access organization settings page. Enable this if you want to prevent users from creating new Claude or Console organizations—including personal accounts—using your verified domains. ------------------------------------------------------------------------ ## Step 3: Set up SSO with your Identity Provider 1. Navigate to your **Organization and access** settings in Claude (**[claude.ai/admin-settings/organization](https://claude.ai/admin-settings/organization)**) or your **Identity and access** settings in Console (**[platform.claude.com/settings/identity](https://platform.claude.com/settings/identity)**). 2. In the **Authentication** section, click “Setup SSO” (or “Manage SSO”). 3. Follow the setup guide provided for your Identity Provider (see below for additional guides). 4. At the end of these steps, you’ll be prompted to Test Single Sign-on to confirm there are no errors and the configuration is successful. 5. Once complete, navigate back to the **Organization and access** settings page for further configuration options. **Important:** SSO enforcement might result in users being unable to log in if they are not correctly assigned to the Anthropic app in the IdP. If you have more than one Claude/Console org connected to your “parent org,” you will want to consider creating a unique IdP Group for each. For more information, see **[enable group mappings](https://support.claude.com/en/articles/13133195-setting-up-jit-or-scim-provisioning#h_adee31eeba)**. For IdP-specific setup instructions, see: - **[Okta SAML](https://workos.com/docs/integrations/okta-saml)** - **[Entra ID SAML (formerly Azure AD)](https://workos.com/docs/integrations/entra-id-saml)** - **[Google SAML](https://workos.com/docs/integrations/google-saml)** - **[OneLogin SAML](https://workos.com/docs/integrations/onelogin-saml)** - **[JumpCloud SAML](https://workos.com/docs/integrations/jumpcloud-saml)** - **[Duo SAML](https://workos.com/docs/integrations/duo-saml/4-enter-duo-saml-settings-in-your-workos-dashboard)** ------------------------------------------------------------------------ ## Step 4: Choose to require SSO You can now choose to toggle on **Require SSO for Console** and/or **Require SSO for Claude,** on the **Organization and access** page, under the **Authentication** section: When SSO is required, users must use the “Continue with SSO” option to log in to their Claude/Console accounts. When SSO is not required, they will have the option to choose “Continue with SSO” or “Continue with email.” Before you decide, review **[What happens to existing users when SSO is enabled](https://support.claude.com/en/articles/10276682-important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisioning#h_644f467167)**. ------------------------------------------------------------------------ ## Step 5: Choose your provisioning approach Once SSO is enabled, you need to decide how users will be added to your organization by choosing an option within the **User provisioning** section of your **Organization and access** settings. **Invite only** is the default. Users are added and removed directly in your Claude or Console settings. Please see **[Manage members on Team and Enterprise plans](https://support.claude.com/en/articles/13133750-managing-members-on-team-and-enterprise-plans)**. **Just-in-Time (JIT) provisioning** can be enabled to automatically provision users when they first log in. By default, users assigned to your Anthropic IdP app first login, they will receive the User role. This is the simplest automated option and requires no additional configuration beyond selecting "Just-in-Time (JIT)" as your provisioning mode. ### Enable group mappings - when to configure additional provisioning features For more control over provisioning, see **[Set up JIT or SCIM provisioning](https://support.claude.com/en/articles/13133195-setting-up-jit-or-scim-provisioning)**. You'll want to review this guide if you need to: - Automatically assign roles or seat tiers based on IdP group membership. - Use SCIM directory sync for automatic provisioning and deprovisioning. - Manage access across multiple organizations (e.g., if you have both a Team/Enterprise organization and a Console organization linked to the same parent and need to control which users are provisioned to each). **Note:** We don't currently support IdP-initiated login for Claude Console organizations that share SSO settings with a Team or Enterprise plan organization. Users will be redirected to claude.ai with IdP-initiated login. As a workaround, if possible in your IdP, create a bookmark called "Claude Console" that links to platform.claude.com/login?sso=true to redirect users to Console for SP-initiated login. ------------------------------------------------------------------------ ## Updating your SSO certificate When your Identity Provider's X.509 signing certificate expires or is rotated, you'll need to update it in Claude or Console to maintain SSO functionality. 1. Navigate to your settings: - For Team and Enterprise plans: **[claude.ai/admin-settings/organization](https://claude.ai/admin-settings/organization)** - For Claude Console: **[platform.claude.com/settings/identity](https://platform.claude.com/settings/organization)** 2. In the **Authentication** section, click “Manage SSO.” 3. Find the **Metadata configuration** section and click “Edit.” 4. Update your certificate information and save your changes. 5. Click "Test sign-in" on the same page to confirm everything is working. **Important:** If **Require SSO** is turned on and your certificate has already expired, no one in your organization can sign in to update it, because every sign-in option routes through SSO. **[Contact Support](https://support.claude.com/en/articles/9015913)** from an Owner’s or Primary Owner’s email address and we’ll help you regain access so an Owner can update the certificate. To avoid this, note your certificate’s expiry date in your Identity Provider and rotate it ahead of time. ------------------------------------------------------------------------ ## Turning off SSO You can toggle **Require SSO for Claude** or **Require SSO for Console** off at any time. This will make SSO optional for all users. To fully disconnect SSO, click “Manage SSO” then “Reset connection.” This will end all users’ sessions and require them to sign back in via email login link. ## Locked out of admin access? If none of your Owners or Admins can sign in (for example, after a certificate expiry, an Identity Provider change, or a group mapping that removed your administrators), contact Support from an Owner’s or Primary Owner’s email address. We’ll verify your ownership of the organization and help you regain access so you can correct the configuration. --- ## setting-up-single-sign-on-sso-for-claude-and-claude-console-d68cfba8d5.md # Set up single sign-on (SSO) Copy for LLM Single sign-on is available for Team plans, Enterprise plans, and Console organizations. This guide covers the steps to configure SSO for Team and Enterprise plans, and Claude Console organizations. ## Step 1: Review prerequisites and important considerations Before proceeding with SSO setup, complete the following: **Review the considerations guide:** Read **[Important considerations before enabling single sign-on (SSO) and JIT/SCIM provisioning](https://support.claude.com/en/articles/10276682-important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisioning)** to understand parent organizations, determine your setup path, and complete any prerequisite steps such as merging organizations. **Confirm you have the required role:** - For Team or Enterprise plans: You must be an Owner or Primary Owner - For Claude Console: You must be an Admin **Confirm you have access to the following:** - DNS settings for your company's email address domain - Your company's SSO Identity Provider (IdP) used to log in to third-party applications (e.g., Okta, Google Workspace, etc.) Please contact your organization's IT Administrator if you do not have permissions to manage Claude or company DNS settings. **Note:** WorkOS is Anthropic's provider for domain verification and SSO setup. More details can be found in **[Anthropic's Subprocessor List](https://trust.anthropic.com/subprocessors)**. You will be taken through a WorkOS setup flow when configuring SSO and provisioning features—find your Identity Provider in their **[Integration documentation](https://workos.com/docs/integrations)**. ------------------------------------------------------------------------ ## Step 2: Verify your domain(s) Domain verification proves that you own your company's domain. Once verified, you can configure SSO for accounts with your company's domain. You can verify multiple domains for a single organization, but all domains must be managed through a single IdP. We don't support verifying domains from separate IdPs within the same organization. **Note:** Verifying your domain by itself will not impact existing users' ability to access our products. End users’ access is only affected once SSO is set up and explicitly enforced. 1. Navigate to your **Organization and access** settings in Claude (**[claude.ai/admin-settings/organization](https://claude.ai/admin-settings/organization)**) or your **Identity and access** settings in Console (**[platform.claude.com/settings/identity](https://platform.claude.com/settings/identity)**) – note this page will only appear on Console if you've worked with Sales to enable SSO or completed a merge proposal. 2. In the **Domains** section, click “Add or edit domains.” 3. Enter the domain(s) you want to verify in the **Update organization email domains** modal and click the “+” button: 4. Click “Save” when you’re finished adding domains. 5. The domain(s) you added will now appear in the **Domains** section; click “Verify” to the right of the domain(s) to begin the verification process. 6. Enter your domain in the text box and click “Continue”: 7. The setup screen displays a TXT record. **Copy the full Value using the copy button**—it begins with `anthropic-domain-verification-` and is longer than what's visible in the box. In your DNS provider, add a TXT record to your domain and **Value** set to the copied string. The domain must match exactly what you entered in the previous step, including any subdomains. Add it alongside any existing TXT records; don't replace them. The value is case-sensitive, so paste it exactly. Please refer to your DNS provider's documentation on this topic. 1. **Important:** Save the TXT value before leaving the setup screen. Once the domain shows as Pending, the admin console doesn't display the value again. If you lose it, you'll need to remove and re-add the domain, which generates a new value. 8. Wait 10 minutes for your DNS change to propagate. - **Note:** *DNS changes can take 24-48 hours to propagate globally.* 9. When you see the green "Verified" badge, you can close the instructions page. 10. If your domain shows as "Pending," use the "Refresh" button. ### If your domain stays Pending Clicking "Refresh" re-checks your DNS; it won't show Verified until the published TXT record exactly matches the expected value. If it stays Pending after DNS has propagated, check the following: - **The record exists at the root.** Look up your domain's TXT records with a tool such as **[DNSChecker](https://dnschecker.org/#TXT)** and confirm a record beginning with `anthropic-domain-verification-` appears for `yourdomain.com` (not `www.yourdomain.com` or another subdomain). If it doesn't appear, the record may have been added at the wrong host or hasn't propagated yet. - **The value matches exactly.** The check is case-sensitive and requires the full string including the `anthropic-domain-verification-…=` prefix. A single character difference will keep it Pending. - **You haven't removed and re-added the domain.** Each re-add generates a new verification value. If you re-added the domain after publishing the TXT record, the published value no longer matches—you'll need to update the DNS record with the new value. If the record is correct and propagated but the status still shows Pending, contact Support. **Note:** Once your domain is verified, you'll see a **Restrict organization creation** toggle under **Security** on the Organization and access organization settings page. Enable this if you want to prevent users from creating new Claude or Console organizations—including personal accounts—using your verified domains. ------------------------------------------------------------------------ ## Step 3: Set up SSO with your Identity Provider 1. Navigate to your **Organization and access** settings in Claude (**[claude.ai/admin-settings/organization](https://claude.ai/admin-settings/organization)**) or your **Identity and access** settings in Console (**[platform.claude.com/settings/identity](https://platform.claude.com/settings/identity)**). 2. In the **Authentication** section, click “Setup SSO” (or “Manage SSO”). 3. Follow the setup guide provided for your Identity Provider (see below for additional guides). 4. At the end of these steps, you’ll be prompted to Test Single Sign-on to confirm there are no errors and the configuration is successful. 5. Once complete, navigate back to the **Organization and access** settings page for further configuration options. **Important:** SSO enforcement might result in users being unable to log in if they are not correctly assigned to the Anthropic app in the IdP. If you have more than one Claude/Console org connected to your “parent org,” you will want to consider creating a unique IdP Group for each. For more information, see **[enable group mappings](https://support.claude.com/en/articles/13133195-setting-up-jit-or-scim-provisioning#h_adee31eeba)**. For IdP-specific setup instructions, see: - **[Okta SAML](https://workos.com/docs/integrations/okta-saml)** - **[Entra ID SAML (formerly Azure AD)](https://workos.com/docs/integrations/entra-id-saml)** - **[Google SAML](https://workos.com/docs/integrations/google-saml)** - **[OneLogin SAML](https://workos.com/docs/integrations/onelogin-saml)** - **[JumpCloud SAML](https://workos.com/docs/integrations/jumpcloud-saml)** - **[Duo SAML](https://workos.com/docs/integrations/duo-saml/4-enter-duo-saml-settings-in-your-workos-dashboard)** ------------------------------------------------------------------------ ## Step 4: Choose to require SSO You can now choose to toggle on **Require SSO for Console** and/or **Require SSO for Claude,** on the **Organization and access** page, under the **Authentication** section: When SSO is required, users must use the “Continue with SSO” option to log in to their Claude/Console accounts. When SSO is not required, they will have the option to choose “Continue with SSO” or “Continue with email.” Before you decide, review **[What happens to existing users when SSO is enabled](https://support.claude.com/en/articles/10276682-important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisioning#h_644f467167)**. ------------------------------------------------------------------------ ## Step 5: Choose your provisioning approach Once SSO is enabled, you need to decide how users will be added to your organization by choosing an option within the **User provisioning** section of your **Organization and access** settings. **Invite only** is the default. Users are added and removed directly in your Claude or Console settings. Please see **[Manage members on Team and Enterprise plans](https://support.claude.com/en/articles/13133750-managing-members-on-team-and-enterprise-plans)**. **Just-in-Time (JIT) provisioning** can be enabled to automatically provision users when they first log in. By default, users assigned to your Anthropic IdP app first login, they will receive the User role. This is the simplest automated option and requires no additional configuration beyond selecting "Just-in-Time (JIT)" as your provisioning mode. ### Enable group mappings - when to configure additional provisioning features For more control over provisioning, see **[Set up JIT or SCIM provisioning](https://support.claude.com/en/articles/13133195-setting-up-jit-or-scim-provisioning)**. You'll want to review this guide if you need to: - Automatically assign roles or seat tiers based on IdP group membership. - Use SCIM directory sync for automatic provisioning and deprovisioning. - Manage access across multiple organizations (e.g., if you have both a Team/Enterprise organization and a Console organization linked to the same parent and need to control which users are provisioned to each). **Note:** We don't currently support IdP-initiated login for Claude Console organizations that share SSO settings with a Team or Enterprise plan organization. Users will be redirected to claude.ai with IdP-initiated login. As a workaround, if possible in your IdP, create a bookmark called "Claude Console" that links to platform.claude.com/login?sso=true to redirect users to Console for SP-initiated login. ------------------------------------------------------------------------ ## Updating your SSO certificate When your Identity Provider's X.509 signing certificate expires or is rotated, you'll need to update it in Claude or Console to maintain SSO functionality. 1. Navigate to your settings: - For Team and Enterprise plans: **[claude.ai/admin-settings/organization](https://claude.ai/admin-settings/organization)** - For Claude Console: **[platform.claude.com/settings/identity](https://platform.claude.com/settings/organization)** 2. In the **Authentication** section, click “Manage SSO.” 3. Find the **Metadata configuration** section and click “Edit.” 4. Update your certificate information and save your changes. 5. Click "Test sign-in" on the same page to confirm everything is working. **Important:** If **Require SSO** is turned on and your certificate has already expired, no one in your organization can sign in to update it, because every sign-in option routes through SSO. **[Contact Support](https://support.claude.com/en/articles/9015913)** from an Owner’s or Primary Owner’s email address and we’ll help you regain access so an Owner can update the certificate. To avoid this, note your certificate’s expiry date in your Identity Provider and rotate it ahead of time. ------------------------------------------------------------------------ ## Turning off SSO You can toggle **Require SSO for Claude** or **Require SSO for Console** off at any time. This will make SSO optional for all users. To fully disconnect SSO, click “Manage SSO” then “Reset connection.” This will end all users’ sessions and require them to sign back in via email login link. ## Locked out of admin access? If none of your Owners or Admins can sign in (for example, after a certificate expiry, an Identity Provider change, or a group mapping that removed your administrators), contact Support from an Owner’s or Primary Owner’s email address. We’ll verify your ownership of the organization and help you regain access so you can correct the configuration. --- ## setting-up-single-sign-on-sso-for-claude-and-claude-console.md # Set up single sign-on (SSO) Single sign-on is available for Team plans, Enterprise plans, and Console organizations. This guide covers the steps to configure SSO for Team and Enterprise plans, and Claude Console organizations. ## Step 1: Review prerequisites and important considerations Before proceeding with SSO setup, complete the following: **Review the considerations guide:** Read **[Important considerations before enabling single sign-on (SSO) and JIT/SCIM provisioning](important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisi.md)** to understand parent organizations, determine your setup path, and complete any prerequisite steps such as merging organizations. **Confirm you have the required role:** - For Team or Enterprise plans: You must be an Owner or Primary Owner - For Claude Console: You must be an Admin **Confirm you have access to the following:** - DNS settings for your company's email address domain - Your company's SSO Identity Provider (IdP) used to log in to third-party applications (e.g., Okta, Google Workspace, etc.) Please contact your organization's IT Administrator if you do not have permissions to manage Claude or company DNS settings. **Note:** WorkOS is Anthropic's provider for domain verification and SSO setup. More details can be found in **[Anthropic's Subprocessor List](https://trust.anthropic.com/subprocessors)**. You will be taken through a WorkOS setup flow when configuring SSO and provisioning features – find your Identity Provider in their **[Integration documentation](https://workos.com/docs/integrations)**. ------------------------------------------------------------------------ ## Step 2: Verify your domain(s) Domain verification proves that you own your company's domain. Once verified, you can configure SSO for accounts with your company's domain. You can verify multiple domains for a single organization, but all domains must be managed through a single IdP. We don't support verifying domains from separate IdPs within the same organization. **Note:** Verifying your domain by itself will not impact existing users' ability to access our products. End users’ access is only affected once SSO is set up and explicitly enforced. 1. Navigate to your “Identity and access” settings in Claude (**[claude.ai/admin-settings/identity](http://claude.ai/admin-settings/identity)**) or Console (**[platform.claude.com/settings/identity](http://platform.claude.com/settings/identity)**) – note this page will only appear on Console if you've worked with Sales to enable SSO or completed a merge proposal. 2. In the **Domains** section, click “Add or edit domains.” 3. Enter the domain(s) you want to verify in the **Update organization email domains modal** and click the “+” button: 4. Click “Save” when you’re finished adding domains. 5. The domain(s) you added will now appear in the **Domains** section; click “Verify” to the right of the domain(s) to begin the verification process. 6. Enter your domain in the text box and click “Continue”: 7. This will generate a TXT record. Follow the instructions to add this TXT record to your domain provider. - If using a subdomain (e.g., subdomain.yourcompany.com), set your TXT record on that subdomain (e.g., \_acme-challenge.subdomain.yourco. mpany.com). 8. Wait 10 minutes for your DNS change to propagate. - *Note: DNS changes can take 24-48 hours to propagate globally.* 9. When you see the green "Verified" badge, you can close the instructions page. 10. If your domain shows as "Pending," use the "Refresh" button. **Note:** Once your domain is verified, you'll see a **Restrict organization creation** toggle under **Security** on the Identity and access organization settings page. Enable this if you want to prevent users from creating new Claude or Console organizations—including personal accounts—using your verified domains. ------------------------------------------------------------------------ ## Step 3: Set up SSO with your Identity Provider 1. Navigate to your Identity and access settings in Claude (**[claude.ai/admin-settings/identity](http://claude.ai/admin-settings/identity)**) or Console (**[platform.claude.com/settings/identity](http://platform.claude.com/settings/identit)**) 2. In the **Global access settings** section, click “Setup SSO” (or “Manage”). 3. Follow the setup guide provided for your Identity Provider (see below for additional guides). 4. At the end of these steps, you’ll be prompted to Test Single Sign-on to confirm there are no errors and the configuration is successful. 5. Once complete, navigate back to the Identity and access settings page for further configuration options. **Important:** SSO enforcement might result in users being unable to log in if they are not correctly assigned to the Anthropic app in the IdP. If you have more than one Claude/Console org connected to your “parent org,” you will want to consider creating a unique IdP Group for each. For more information, see **[enable group mappings](../13-Enterprise-Admin/setting-up-jit-or-scim-provisioning.md#h_adee31eeba)**. For IdP-specific setup instructions, see: - **[Okta SAML](https://workos.com/docs/integrations/okta-saml)** - **[Entra ID SAML (formerly Azure AD)](https://workos.com/docs/integrations/entra-id-saml)** - **[Google SAML](https://workos.com/docs/integrations/google-saml)** - **[OneLogin SAML](https://workos.com/docs/integrations/onelogin-saml)** - **[JumpCloud SAML](https://workos.com/docs/integrations/jumpcloud-saml)** - **[Duo SAML](https://workos.com/docs/integrations/duo-saml/4-enter-duo-saml-settings-in-your-workos-dashboard)** ------------------------------------------------------------------------ ## Step 4: Choose to require SSO You can now choose to toggle on **Require SSO for Console** and/or **Require SSO for Claude,** on the Identity and access page, under the **Global access settings** section: When SSO is required, users must use the “Continue with SSO” option to access Claude/Console. When SSO is not required, they will have the option to choose “Continue with SSO” or “Continue with email.” Before you decide, review **[What happens to existing users when SSO is enabled](important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisi.md#h_644f467167)**. ------------------------------------------------------------------------ ## Step 5: Choose your provisioning approach Once SSO is enabled, you need to decide how users will be added to your organization. This is controlled by the **Provisioning mode** setting in the **Global access settings** section of your Identity and access settings. **Invite only** is the default. Users are added and removed directly in your Claude or Console settings. Please see **[Manage members on Team and Enterprise plans](../17-Billing-Plans/managing-members-on-team-and-enterprise-plans.md)**. **JIT (Just-in-Time) provisioning** can be enabled to automatically provision users when they first log in. By default, users assigned to your Anthropic IdP app first login, they will receive the User role. This is the simplest automated option and requires no additional configuration beyond selecting "Approve automatically (JIT)" as your provisioning mode. ### Enable group mappings - when to configure additional provisioning features For more control over provisioning, see **[Set up JIT or SCIM provisioning](../13-Enterprise-Admin/setting-up-jit-or-scim-provisioning.md)**. You'll want to review this guide if you need to: - Automatically assign roles or seat tiers based on IdP group membership. - Use SCIM directory sync for automatic provisioning and deprovisioning. - Manage access across multiple organizations (e.g., if you have both a Team/Enterprise organization and a Console organization linked to the same parent and need to control which users are provisioned to each). **Note:** We don't currently support IdP-initiated login for Claude Console organizations that share SSO settings with a Team or Enterprise plan organization. Users will be redirected to claude.ai with IdP-initiated login. As a workaround, if possible in your IdP, create a bookmark called "Claude Console" that links to platform.claude.com/login?sso=true to redirect users to Console for SP-initiated login. ------------------------------------------------------------------------ ## Updating your SSO certificate When your Identity Provider's X.509 signing certificate expires or is rotated, you'll need to update it in Claude or Console to maintain SSO functionality. 1. Navigate to your Identity and access settings: - For Team and Enterprise plans: **[claude.ai/admin-settings/identity](http://claude.ai/admin-settings/identity)** - For Claude Console: **[platform.claude.com/settings/identity](http://platform.claude.com/settings/identity)** 2. In the **Global access settings** section, click “Manage SSO.” 3. Select “Metadata Config.” 4. Click “Edit.” 5. Update your certificate information and save your changes. 6. Click "Test sign-in" on the same page to confirm everything is working. ------------------------------------------------------------------------ ## Turning off SSO You can toggle **Require SSO for Claude** or **Require SSO for Console** off at any time. This will make SSO optional for all users. To fully disconnect SSO, click “Manage SSO” then “Reset.” This will end all users’ sessions and require them to sign back in via email login link. --- ## setting-up-single-sign-on-sso.md # Set up single sign-on (SSO) Single sign-on is available for Team plans, Enterprise plans, and Console organizations. This guide covers the steps to configure SSO for Team and Enterprise plans, and Claude Console organizations. ## Step 1: Review prerequisites and important considerations Before proceeding with SSO setup, complete the following: **Review the considerations guide:** Read **[Important considerations before enabling single sign-on (SSO) and JIT/SCIM provisioning](important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisi.md)** to understand parent organizations, determine your setup path, and complete any prerequisite steps such as merging organizations. **Confirm you have the required role:** - For Team or Enterprise plans: You must be an Owner or Primary Owner - For Claude Console: You must be an Admin **Confirm you have access to the following:** - DNS settings for your company's email address domain - Your company's SSO Identity Provider (IdP) used to log in to third-party applications (e.g., Okta, Google Workspace, etc.) Please contact your organization's IT Administrator if you do not have permissions to manage Claude or company DNS settings. **Note:** WorkOS is Anthropic's provider for domain verification and SSO setup. More details can be found in **[Anthropic's Subprocessor List](https://trust.anthropic.com/subprocessors)**. You will be taken through a WorkOS setup flow when configuring SSO and provisioning features – find your Identity Provider in their **[Integration documentation](https://workos.com/docs/integrations)**. ------------------------------------------------------------------------ ## Step 2: Verify your domain(s) Domain verification proves that you own your company's domain. Once verified, you can configure SSO for accounts with your company's domain. You can verify multiple domains for a single organization, but all domains must be managed through a single IdP. We don't support verifying domains from separate IdPs within the same organization. **Note:** Verifying your domain by itself will not impact existing users' ability to access our products. End users’ access is only affected once SSO is set up and explicitly enforced. 1. Navigate to your “Identity and access” settings in Claude (**[claude.ai/admin-settings/identity](http://claude.ai/admin-settings/identity)**) or Console (**[platform.claude.com/settings/identity](http://platform.claude.com/settings/identity)**) – note this page will only appear on Console if you've worked with Sales to enable SSO or completed a merge proposal. 2. In the **Domains** section, click “Add or edit domains.” 3. Enter the domain(s) you want to verify in the **Update organization email domains modal** and click the “+” button: 4. Click “Save” when you’re finished adding domains. 5. The domain(s) you added will now appear in the **Domains** section; click “Verify” to the right of the domain(s) to begin the verification process. 6. Enter your domain in the text box and click “Continue”: 7. This will generate a TXT record. Follow the instructions to add this TXT record to your domain provider. - If using a subdomain (e.g., subdomain.yourcompany.com), set your TXT record on that subdomain (e.g., \_acme-challenge.subdomain.yourco. mpany.com). 8. Wait 10 minutes for your DNS change to propagate. - *Note: DNS changes can take 24-48 hours to propagate globally.* 9. When you see the green "Verified" badge, you can close the instructions page. 10. If your domain shows as "Pending," use the "Refresh" button. **Note:** Once your domain is verified, you'll see a **Restrict organization creation** toggle under **Security** on the Identity and access organization settings page. Enable this if you want to prevent users from creating new Claude or Console organizations—including personal accounts—using your verified domains. ------------------------------------------------------------------------ ## Step 3: Set up SSO with your Identity Provider 1. Navigate to your Identity and access settings in Claude (**[claude.ai/admin-settings/identity](http://claude.ai/admin-settings/identity)**) or Console (**[platform.claude.com/settings/identity](http://platform.claude.com/settings/identit)**) 2. In the **Global access settings** section, click “Setup SSO” (or “Manage”). 3. Follow the setup guide provided for your Identity Provider (see below for additional guides). 4. At the end of these steps, you’ll be prompted to Test Single Sign-on to confirm there are no errors and the configuration is successful. 5. Once complete, navigate back to the Identity and access settings page for further configuration options. **Important:** SSO enforcement might result in users being unable to log in if they are not correctly assigned to the Anthropic app in the IdP. If you have more than one Claude/Console org connected to your “parent org,” you will want to consider creating a unique IdP Group for each. For more information, see **[enable group mappings](../13-Enterprise-Admin/setting-up-jit-or-scim-provisioning.md#h_adee31eeba)**. For IdP-specific setup instructions, see: - **[Okta SAML](https://workos.com/docs/integrations/okta-saml)** - **[Entra ID SAML (formerly Azure AD)](https://workos.com/docs/integrations/entra-id-saml)** - **[Google SAML](https://workos.com/docs/integrations/google-saml)** - **[OneLogin SAML](https://workos.com/docs/integrations/onelogin-saml)** - **[JumpCloud SAML](https://workos.com/docs/integrations/jumpcloud-saml)** - **[Duo SAML](https://workos.com/docs/integrations/duo-saml/4-enter-duo-saml-settings-in-your-workos-dashboard)** ------------------------------------------------------------------------ ## Step 4: Choose to require SSO You can now choose to toggle on **Require SSO for Console** and/or **Require SSO for Claude,** on the Identity and access page, under the **Global access settings** section: When SSO is required, users must use the “Continue with SSO” option to access Claude/Console. When SSO is not required, they will have the option to choose “Continue with SSO” or “Continue with email.” Before you decide, review **[What happens to existing users when SSO is enabled](important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisi.md#h_644f467167)**. ------------------------------------------------------------------------ ## Step 5: Choose your provisioning approach Once SSO is enabled, you need to decide how users will be added to your organization. This is controlled by the **Provisioning mode** setting in the **Global access settings** section of your Identity and access settings. **Invite only** is the default. Users are added and removed directly in your Claude or Console settings. Please see **[Manage members on Team and Enterprise plans](../17-Billing-Plans/managing-members-on-team-and-enterprise-plans.md)**. **JIT (Just-in-Time) provisioning** can be enabled to automatically provision users when they first log in. By default, users assigned to your Anthropic IdP app first login, they will receive the User role. This is the simplest automated option and requires no additional configuration beyond selecting "Approve automatically (JIT)" as your provisioning mode. ### Enable group mappings - when to configure additional provisioning features For more control over provisioning, see **[Set up JIT or SCIM provisioning](../13-Enterprise-Admin/setting-up-jit-or-scim-provisioning.md)**. You'll want to review this guide if you need to: - Automatically assign roles or seat tiers based on IdP group membership. - Use SCIM directory sync for automatic provisioning and deprovisioning. - Manage access across multiple organizations (e.g., if you have both a Team/Enterprise organization and a Console organization linked to the same parent and need to control which users are provisioned to each). **Note:** We don't currently support IdP-initiated login for Claude Console organizations that share SSO settings with a Team or Enterprise plan organization. Users will be redirected to claude.ai with IdP-initiated login. As a workaround, if possible in your IdP, create a bookmark called "Claude Console" that links to platform.claude.com/login?sso=true to redirect users to Console for SP-initiated login. ------------------------------------------------------------------------ ## Updating your SSO certificate When your Identity Provider's X.509 signing certificate expires or is rotated, you'll need to update it in Claude or Console to maintain SSO functionality. 1. Navigate to your Identity and access settings: - For Team and Enterprise plans: **[claude.ai/admin-settings/identity](http://claude.ai/admin-settings/identity)** - For Claude Console: **[platform.claude.com/settings/identity](http://platform.claude.com/settings/identity)** 2. In the **Global access settings** section, click “Manage SSO.” 3. Select “Metadata Config.” 4. Click “Edit.” 5. Update your certificate information and save your changes. 6. Click "Test sign-in" on the same page to confirm everything is working. ------------------------------------------------------------------------ ## Turning off SSO You can toggle **Require SSO for Claude** or **Require SSO for Console** off at any time. This will make SSO optional for all users. To fully disconnect SSO, click “Manage SSO” then “Reset.” This will end all users’ sessions and require them to sign back in via email login link. --- ## sso-login-15e9ee63fa.md # SSO login April 10, 2026 Copy for LLM Claude for Government requires Single Sign-on (SSO) for user authentication. Unlike the commercial Claude Enterprise plan, email based (magic link) login is only available to the Primary Owner during account setup. All other users must authenticate through your organization's identity provider (IdP). Once SSO is configured, the Primary Owner can disable magic link login entirely so that all authentication flows through your IdP. For SSO setup on Claude Enterprise, see **[Set up single sign-on (SSO)](https://support.claude.com/en/articles/13132885-set-up-single-sign-on-sso)**. ## How SSO differs for Claude for Government [TABLE] ## Steps for setting up SSO ### Prerequisites Before you begin, confirm that you have: - **Primary Owner access** — The email address registered as Primary Owner when the license was purchased. - **DNS access** — Ability to create TXT records for your organization's login domain(s). - **IdP admin access** — Permission to create a SAML application in your identity provider (e.g., Entra ID, Okta). ### Step 1: Sign in as Primary Owner 1. Navigate to **[claude.fedstart.com](http://claude.fedstart.com)** 2. Enter the email address registered as Primary Owner. 3. Complete the email-based login using the magic link sent to the Primary Owner’s inbox. 4. After signing in, the Primary Owner will be redirected to the identity settings page at **[claude.fedstart.com/admin-settings/identity](https://claude.fedstart.com/admin-settings/identity)** **Tip**: It often makes sense to appoint someone from your IT team as the Primary Owner, since they will need DNS and IdP access for the remaining steps. ### Step 2: Verify your domain Before configuring your Identity Provider (IdP), you must verify ownership of your login domain. 1. On the identity settings page, locate your domain and select the **"View instructions"** tab. There you’ll be able to see the required DNS challenge record that must be set. 2. Create the displayed TXT record in your domain’s DNS settings. 3. Wait for the DNS propagation. Once the platform detects the record, the domain status will update to “**Verified**.” **Important:** Each domain can only have one identity provider. If multiple organizations share a single login domain, IT administrators from both organizations will be able to modify login settings. Contact **[Anthropic Support](https://claude.fedstart.com/support)** for assistance with multi-organization setups. For more details about multi-organization setups, see our **[SCIM provisioning guide](https://support.claude.com/en/articles/14503643-set-up-scim-in-claude-for-government)**. ### Step 3: Configure your Identity Provider Anthropic acts as the **Service Provider (SP)** in the SAML SSO flow. Your organization’s IdP (e.g., Entra or Okta) acts as the **Identity Provider.** 1. On the identity settings page, locate the **SP Metadata** section. This contains the values your IdP needs: 1. Entity ID (Audience URI) 2. ACS URL (Reply URL) 2. In your IdP, create a new SAML application using these SP metadata values ### Step 4: Configure Anthropic with your IdP details Once your SAML application is set up in your IdP, provide Anthropic with the details it needs to verify SAML assertions. On the identity settings page, enter: - Signing Certificate — The X.509 certificate from your IdP. - IdP Entity ID — Your IdP's entity identifier. - SSO URL — The IdP's SAML sign-on endpoint. - Claims Information — Attribute mappings for user name and email. **Tip:** Using a metadata XML file: Most IdPs let you download a metadata.xml file. Upload it on the identity settings page to auto-fill the Signing Certificate, IdP Entity ID, and SSO URL. Some IdPs (like Entra ID) also include claims information in the metadata file; if present, the system will suggest field mappings automatically. **Troubleshooting attribute mappings** Attribute mapping is where most configuration issues occur. If login fails after setup: 1. Install a SAML debugging extension such as SAML-tracer. 2. Attempt an SSO login and inspect the SAML response. 3. Confirm that the email claim returns an address under your verified domain. Email claims for unverified domains will be rejected. ### Step 5: Test and finalize 1. Log out of Claude for Government. 2. Log back in using your SSO configuration to confirm it works. 3. (Optional) Once SSO login is verified, return to the identity settings page and disable magic link login. **Warning**: Only disable magic link login after you have confirmed that SSO login works. If SSO is misconfigured and the magic link is disabled, the Primary Owner will be unable to access the admin console. Contact Anthropic support if you are locked out. After SSO is configured, any user assigned to the SAML application in your IdP can log in and will be provisioned a seat automatically, provided your organization has available licenses. If no seats are available, users will see an error at login. Contact your Anthropic account representative to add licenses. For more controlled provisioning—including role assignment and multi-organization support—see **[SCIM provisioning](https://support.claude.com/en/articles/14503643-set-up-scim-in-claude-for-government)**. --- ## troubleshooting-claude-code-docs-3f3657ed0f.md # Troubleshooting Fix high CPU or memory usage, hangs, auto-compact thrashing, and search problems in Claude Code, and find the right page for other issues. > ## Documentation Index > > Fetch the complete documentation index at: > > Use this file to discover all available pages before exploring further. This page covers performance, stability, and search problems once Claude Code is running. For other issues, start with the page that matches where you’re stuck: | Symptom | Go to | |:--------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------------------------------------| | `command not found`, install fails, PATH issues, `EACCES`, TLS errors | [Troubleshoot installation and login](/docs/en/troubleshoot-install) | | Login loops, OAuth errors, `403 Forbidden`, “organization disabled”, Bedrock/Vertex/Foundry credentials | [Troubleshoot installation and login](/docs/en/troubleshoot-install#login-and-authentication) | | Settings not applying, hooks not firing, MCP servers not loading | [Debug your configuration](/docs/en/debug-your-config) | | `API Error: 5xx`, `529 Overloaded`, `429`, request validation errors | [Error reference](/docs/en/errors) | | `model not found` or `you may not have access to it` | [Error reference](/docs/en/errors#theres-an-issue-with-the-selected-model) | | VS Code extension not connecting or detecting Claude | [VS Code integration](/docs/en/vs-code#fix-common-issues) | | JetBrains plugin or IDE not detected | [JetBrains integration](/docs/en/jetbrains#troubleshooting) | | High CPU or memory, slow responses, hangs, search not finding files | [Performance and stability](#performance-and-stability) below | If you’re not sure which applies, run `/doctor` inside Claude Code for an automated check of your installation, settings, MCP servers, and context usage. If `claude` won’t start at all, run `claude doctor` from your shell instead. Performance and stability These sections cover issues related to resource usage, responsiveness, and search behavior. High CPU or memory usage Claude Code is designed to work with most development environments, but may consume significant resources when processing large codebases. If you’re experiencing performance issues: 1. Use `/compact` regularly to reduce context size 2. Close and restart Claude Code between major tasks 3. Consider adding large build directories to your `.gitignore` file If memory usage stays high after these steps, run `/heapdump` to write a JavaScript heap snapshot and a memory breakdown to `~/Desktop`. On Linux without a Desktop folder, the files are written to your home directory. The breakdown shows resident set size, JS heap, array buffers, and unaccounted native memory, which helps identify whether the growth is in JavaScript objects or in native code. To inspect retainers, open the `.heapsnapshot` file in Chrome DevTools under Memory → Load. Attach both files when reporting a memory issue on [GitHub](https://github.com/anthropics/claude-code/issues). Auto-compaction stops with a thrashing error If you see `Autocompact is thrashing: the context refilled to the limit...`, automatic compaction succeeded but a file or tool output immediately refilled the context window several times in a row. Claude Code stops retrying to avoid wasting API calls on a loop that isn’t making progress. To recover: 1. Ask Claude to read the oversized file in smaller chunks, such as a specific line range or function, instead of the whole file 2. Run `/compact` with a focus that drops the large output, for example `/compact keep only the plan and the diff` 3. Move the large-file work to a [subagent](/docs/en/sub-agents) so it runs in a separate context window 4. Run `/clear` if the earlier conversation is no longer needed Command hangs or freezes If Claude Code seems unresponsive: 1. Press Ctrl+C to attempt to cancel the current operation 2. If unresponsive, you may need to close the terminal and restart Restarting doesn’t lose your conversation. Run `claude --resume` in the same directory to pick the session back up. Search and discovery issues If the Search tool, `@file` mentions, custom agents, or custom skills aren’t finding files, the bundled `ripgrep` binary may not run on your system. Install your platform’s `ripgrep` package and tell Claude Code to use it instead: - macOS - Ubuntu/Debian - Alpine - Arch - Windows ```python brew install ripgrep ``` ```python sudo apt install ripgrep ``` ```python apk add ripgrep ``` ```python pacman -S ripgrep ``` ```python winget install BurntSushi.ripgrep.MSVC ``` Then set `USE_BUILTIN_RIPGREP=0` in your [environment](/docs/en/env-vars). Slow or incomplete search results on WSL Disk read performance penalties when [working across file systems on WSL](https://learn.microsoft.com/en-us/windows/wsl/filesystems) may result in fewer-than-expected matches when using Claude Code on WSL. Search still functions, but returns fewer results than on a native filesystem. `/doctor` will show Search as OK in this case. **Solutions:** 1. **Submit more specific searches**: reduce the number of files searched by specifying directories or file types: “Search for JWT validation logic in the auth-service package” or “Find use of md5 hash in JS files”. 2. **Move project to Linux filesystem**: if possible, ensure your project is located on the Linux filesystem (`/home/`) rather than the Windows filesystem (`/mnt/c/`). 3. **Use native Windows instead**: consider running Claude Code natively on Windows instead of through WSL, for better file system performance. Get more help If you’re experiencing issues not covered here: 1. Run `/doctor` to check installation health, settings validity, MCP configuration, and context usage in one pass 2. Use the `/feedback` command within Claude Code to report problems directly to Anthropic 3. Check the [GitHub repository](https://github.com/anthropics/claude-code) for known issues 4. Ask Claude directly about its capabilities and features. Claude has built-in access to its documentation. --- ## where-can-i-access-claude-ai.md # Where can I access Claude? You can access Claude in the following locations: - Albania - Algeria - Andorra - Angola - Antigua and Barbuda - Argentina - Armenia - Australia - Austria - Azerbaijan - Bahamas - Bahrain - Bangladesh - Barbados - Belgium - Belize - Benin - Bhutan - Bolivia - Bosnia and Herzegovina - Botswana - Brazil - Brunei - Bulgaria - Burkina Faso - Burundi - Cambodia - Cameroon - Canada - Cabo Verde - Chad - Chile - Colombia - Comoros - Congo (Brazzaville) - Costa Rica - Croatia - Czechia (Czech Republic) - Denmark - Djibouti - Dominica - Dominican Republic - East Timor - Ecuador - Egypt - El Salvador - Equatorial Guinea - Estonia - Eswatini - Fiji - Finland - France - Gabon - Gambia - Georgia - Germany - Ghana - Greece - Grenada - Guatemala - Guinea - Guinea-Bissau - Guyana - Haiti - Herzegovina - Honduras - Hungary - Iceland - India - Indonesia - Iraq - Ireland - Israel - Italy - Côte d'Ivoire - Jamaica - Japan - Jordan - Kazakhstan - Kenya - Kiribati - Kuwait - Kyrgyzstan - Laos - Latvia - Lebanon - Lesotho - Liberia - Liechtenstein - Lithuania - Luxembourg - Madagascar - Malawi - Malaysia - Maldives - Malta - Mariana Islands - Marshall Islands - Mauritania - Mauritius - Mexico - Micronesia - Moldova - Monaco - Mongolia - Montenegro - Morocco - Mozambique - Namibia - Nauru - Nepal - Netherlands - New Zealand - Niger - Nigeria - North Macedonia - Norway - Oman - Pakistan - Palau - Palestine - Panama - Papua New Guinea - Paraguay - Peru - Philippines - Poland - Portugal - Qatar - Republic of Cyprus - Romania - Rwanda - Saint Kitts and Nevis - Saint Lucia - Saint Vincent and the Grenadines - Samoa - San Marino - São Tomé and Príncipe - Saudi Arabia - Senegal - Serbia - Seychelles - Sierra Leone - Singapore - Slovakia - Slovenia - Solomon Islands - South Africa - South Korea - Spain - Sri Lanka - Suriname - Sweden - Switzerland - Taiwan - Tajikistan - Tanzania - Thailand - Togo - Tonga - Trinidad and Tobago - Tunisia - Türkiye (Turkey) - Turkmenistan - Tuvalu - Uganda - Ukraine - United Arab Emirates - United Kingdom - United States - Uruguay - Uzbekistan - Vanuatu - Vatican City - Vietnam - Zambia - Zimbabwe --- ## who-owns-and-manages-the-data-of-my-claude-for-education-account-8e2602e714.md # Who owns and manages the data of my Claude for Education account? March 16, 2026 Copy for LLM This article provides important information about your Claude for Education account associated with your university’s Claude for Education partnership. It includes details about data access and control that were shared with you when your Claude for Education account was set up. *This article is about Claude for Education (a commercial product). For more information about our other commercial products such as Claude for Work and the Anthropic API see [here](https://privacy.anthropic.com/en/articles/9265372-who-owns-and-manages-the-data-of-my-team). For our consumer products such as Claude Free, Pro, Max and when accounts from those plans use Claude Code, see [here](https://privacy.anthropic.com/en/collections/10663362-consumers).* ## Default Settings and Account Management Your university’s organization's designated Primary Owner manages your Claude for Education account and all associated data. On Claude for Education, by default, the following capabilities are disabled by default: - Primary Owner Data Exports - Audit Log - Thumbs Feedback These settings reflect Anthropic’s default approach to Claude for Education, but we understand that universities may have legitimate needs to access data. In these situations, the Primary Owner will need to reach out to [Anthropic support](https://support.anthropic.com/en/articles/9015913-how-to-get-support) to request and enable access. This includes the ability to request access to your user data through data exports, which may contain your conversations with Claude, uploaded files, and usage patterns. Primary Owners can also remove your access to the Claude for Education account if necessary. Your organization determines which Claude services and features you can access in your Claude for Education account and they may choose to limit certain functionality. ## Governing Agreements The use of your Claude for Education plan account is governed by the agreement between Anthropic and your university. Please contact your Claude for Education administrator for details of this agreement. While Anthropic’s [Privacy Policy](https://www.anthropic.com/legal/privacy) describes how we collect, use and share personal information when acting as a data controller in providing the Claude services to your university, please note that the Anthropic [Consumer Terms of Service](https://www.anthropic.com/legal/consumer-terms) and [Privacy Policy](https://www.anthropic.com/legal/privacy) do not apply to the use of the Claude for Education plan where Anthropic acts as the data processor. ​ ## Organizational Policies Your organization may have its own internal policies regarding usage of Claude for Education. Please refer to your university’s policies for guidance. ## Questions If you have any questions about your Claude for Education plan account, we encourage you to contact your university’s administrator(s). --- ## who-owns-and-manages-the-data-of-my-claude-for-education-account.md 3. Who owns and manages the data of my Claude for Education account? # Who owns and manages the data of my Claude for Education account? This article provides important information about your Claude for Education account associated with your university’s Claude for Education partnership. It includes details about data access and control that were shared with you when your Claude for Education account was set up. *This article is about Claude for Education (a commercial product). For more information about our other commercial products such as Claude for Work and the Anthropic API see [here](https://privacy.anthropic.com/en/articles/9265372-who-owns-and-manages-the-data-of-my-team). For our consumer products such as Claude Free, Pro, Max and when accounts from those plans use Claude Code, see [here](https://privacy.anthropic.com/en/collections/10663362-consumers).* ## Default Settings and Account Management Your university’s organization's designated Primary Owner manages your Claude for Education account and all associated data. On Claude for Education, by default, the following capabilities are disabled by default: - Primary Owner Data Exports - Audit Log - Thumbs Feedback These settings reflect Anthropic’s default approach to Claude for Education, but we understand that universities may have legitimate needs to access data. In these situations, the Primary Owner will need to reach out to [Anthropic support](https://support.anthropic.com/en/articles/9015913-how-to-get-support) to request and enable access. This includes the ability to request access to your user data through data exports, which may contain your conversations with Claude, uploaded files, and usage patterns. Primary Owners can also remove your access to the Claude for Education account if necessary. Your organization determines which Claude services and features you can access in your Claude for Education account and they may choose to limit certain functionality. ## Governing Agreements The use of your Claude for Education plan account is governed by the agreement between Anthropic and your university. Please contact your Claude for Education administrator for details of this agreement. While Anthropic’s [Privacy Policy](https://www.anthropic.com/legal/privacy) describes how we collect, use and share personal information when acting as a data controller in providing the Claude services to your university, please note that the Anthropic [Consumer Terms of Service](https://www.anthropic.com/legal/consumer-terms) and [Privacy Policy](https://www.anthropic.com/legal/privacy) do not apply to the use of the Claude for Education plan where Anthropic acts as the data processor.\ ## Organizational Policies Your organization may have its own internal policies regarding usage of Claude for Education. Please refer to your university’s policies for guidance. ## Questions If you have any questions about your Claude for Education plan account, we encourage you to contact your university’s administrator(s). --- ## why-is-a-coupon-or-promotion-not-available-for-my-account-7b91fff5cb.md # Why is a coupon or promotion not available for my account? March 16, 2026 Copy for LLM Coupons and promotions are generally only available to users trying out a paid plan for the first time. A "This promotion is not available for your account" error message means that you are ineligible for the promotion due to being either an active paid subscriber or having been a paid subscriber in the past. Additionally, App Store subscribers (iOS or Android) are unable to take advantage of promotions at this time. If you are interested in transitioning from an App Store subscription to a direct subscription, you'll need to cancel and resubscribe once your current subscription term ends. --- ## why-is-a-coupon-or-promotion-not-available-for-my-account.md 4. Why is a coupon or promotion not available for my account? # Why is a coupon or promotion not available for my account? Coupons and promotions are generally only available to users trying out a paid plan for the first time. A "This promotion is not available for your account" error message means that you are ineligible for the promotion due to being either an active paid subscriber or having been a paid subscriber in the past. Additionally, App Store subscribers (iOS or Android) are unable to take advantage of promotions at this time. If you are interested in transitioning from an App Store subscription to a direct subscription, you'll need to cancel and resubscribe once your current subscription term ends.