# Account & Support > Every page below, concatenated. Each section gives the page title, its upstream source and its path in this repository. --- ## Account management FAQs | Claude Help Center Source: https://support.claude.com/en/articles/13325567-account-management-faqs Path: 21-Account-Support/account-management-faqs.md # Account management FAQs August 6, 2026 ## 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. --- ## Assign a program to custom roles on Enterprise plans | Claude Help Center Source: https://support.claude.com/en/articles/17118092-assign-a-program-to-custom-roles-on-enterprise-plans Path: 21-Account-Support/assign-a-program-to-custom-roles-on-enterprise-plans.md # Assign a program to custom roles on Enterprise plans This article explains how to assign an Anthropic-issued program to users through custom roles on Enterprise plans. Anthropic offers several verification programs, such as the Cyber Verification Program (CVP), or access to models that might not be generally available. 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" or "grant" to your organization. To use the program or grant, you must assign it to a group of people within the organization. In Claude Enterprise, a program applies to members through a custom role: you add the grant to a role, and assign the role to groups of members. Available on Claude Enterprise plans. ## Before you begin - Your organization must already have a grant. You’ll see grants 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. - You need to be an Owner or Primary Owner in a Claude Enterprise organization to assign grants. - Members who should get access need the role type "Custom" on the **Members** page. Owners, Primary Owners, and Admins who keep their built-in role are not covered by custom roles. - If your organization uses SCIM with group mappings, your identity provider (IdP) sets each user’s role type. To get the grant, a user needs to be in an IdP group that’s mapped to the custom role. ## Give members access with a custom role In Claude Enterprise, Programs and Grants are issued to your organization and apply to members through roles. For some programs, Anthropic creates a role for you: you can’t change its grants, but you can assign groups to it. For others, you add the grant to a role of your own. To assign a program or grant to a custom role: 1. Navigate to **[Organization settings \> Roles](https://claude.ai/admin-settings/roles)** on claude.ai or in the Claude Desktop app. 2. Create a new role by selecting “Add role.” Edit an existing role by opening the three-dot menu at the end of its row and selecting “Edit role.” 3. Select the **Details** tab, then enter a **Role name**. Under **Groups**, choose the groups whose members should get access. 4. Select the **Models** tab and scroll to the **Grants** section. 5. Check the box for each grant this role should have, then select “Save.” To check that you’ve successfully given members access to your program: 1. Navigate to **[Organization settings \> Grants](https://claude.ai/admin-settings/grants)**. The section for your grant lists its requirements (for example, data retention or a member cap, depending on the grant). 2. Navigate to **[Organization settings \> Roles](https://claude.ai/admin-settings/roles)**. The role shows **Grant role**. To remove access, clear the box in the **Grants** section in the custom role and save. To remove one person, take them out of the role's groups. ## Where the model appears Users get access to the model through the grant. Once the role has the grant, users whose role type is "Custom" and who are in one of the role’s groups can use the model. A model that comes with a grant isn’t listed on the **Models** page or in a role’s **Add model** list, and you don’t add it there. Owners, Primary Owners, and Admins who keep their built-in role don’t get the model, even if they’re in one of the role’s groups. ## Troubleshooting ### The model doesn’t appear for an Owner, Primary Owner, or Admin Custom roles don’t apply to Owners, Primary Owners, and Admins who keep their built-in role, so a grant on a custom role doesn’t reach them. To check that the grant works, test with a user whose role type is "Custom" and who is in one of the role’s groups. ### The Grants page, or the Grants section in the Models tab of the role, is missing Your organization doesn’t have a grant yet, or your role can’t view it. These pages are only available for Enterprise plans. Contact your Anthropic account team or an Owner of your organization. ### The checkboxes are grey Hovering over a box shows "Only organization owners can change which grants this role has." Ask an Owner or Primary Owner. ### The role says "Granted by Anthropic and managed centrally. These grants are read-only." Anthropic created this role. Assign your groups to it to give them access to your program. ### The role shows "Grant withheld", or the Grants page shows "Action required." The grant isn’t in effect for a role, or is on hold. Open **Grants** and fix the requirements that aren’t met. If there’s nothing to fix, contact your Anthropic account team. ### The grant is over its member cap Some grants have a member cap. The role editor shows a warning message: "This role will exceed the member cap of … for the … grant. Everyone in this role will lose access until the member cap is restored." Reduce the members in the groups of the roles that have this grant. --- ## Assign a program to workspaces in Claude Console | Claude Help Center Source: https://support.claude.com/en/articles/16764810-assign-a-program-to-workspaces-in-claude-console Path: 21-Account-Support/assign-a-program-to-workspaces-in-claude-console.md # Assign a program to workspaces in Claude Console This article explains how to apply grants and enable programs for the Anthropic Console and API. Anthropic offers several verification programs, such as the Cyber Verification Program (CVP), 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” or “grant” to your organization. To use the program or grant, you must assign it to a group of people within the organization. In the Claude Console, a program applies only to the workspaces you assign it to. This article shows you how to assign one. ## 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, your Organization Admin or Owner goes to our **[Verification Portal](https://portal.anthropic.com/)** to see what programs are available. - In the Console, you need to be an organization Admin or Owner. 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. You need to assign each program to the workspaces that should use it. A program only applies to API traffic from workspaces that meet its requirements. Follow these steps: 1. **[Sign in to the Console](../04-API-Reference/Other/playground.md)** as an organization Admin. 2. Go to **[Organization settings \> Programs](https://platform.claude.com/settings/programs)**. 3. 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. 4. Hover over the issue to see which requirement is not met. 5. On the program's page, click the workspace's name in the **Workspaces** table, and check the **Qualifications** panel. Unmet requirements are flagged with remediation steps. ## Assign Programs to a workspace Programs apply only to the workspaces you assign them to. ### 1. Create a new Workspace and add users Some programs can’t be assigned to the default workspace. If your program is one of them, create a dedicated workspace first. 1. **[Sign in to the Console](../04-API-Reference/Other/playground.md)** as an organization Admin. 2. Go to the **Workspaces** page (platform.claude.com/settings/workspaces). 3. Click "Create workspace" (you cannot use the default workspace for accessing the model). The **Create workspace** page opens. 4. Enter a name for your new Workspace, and select a color. The color helps you identify your workspace in the Claude Console. 5. Click "Create workspace." 6. Add the approved users to the new Workspace. **Important:** Some programs have a seat cap. If your organization goes over the cap, assigned workspaces lose access until it’s back under the limit. Learn more about **[creating and managing Workspaces in the Claude Console](../13-Enterprise-Admin/creating-and-managing-workspaces-in-the-claude-console.md)**. **Note:** If support asks for your workspace ID, go to the **Workspaces** page (platform.claude.com/settings/workspaces) and select your workspace. Workspace IDs start with `wrkspc_`. Your organization ID is on the **Organization** page (platform.claude.com/settings/organization). ### 2. Enable access in your organization You add the grant to a workspace in your existing Anthropic organization. For API organizations, access is enabled on a workspace within your existing Anthropic organization. You don’t need a new organization or a separate organization. 1. **[Sign in to the Console](../04-API-Reference/Other/playground.md)** as an organization Admin. 2. Go to the **Programs** page (platform.claude.com/settings/programs), and you’ll see the approved access Grants available for your organization and the model’s codename. 3. On the program's page, click the name of the workspace you set up in Step 1 in the **Workspaces** table. 4. Click “Add grant.” 5. Select the program or grant to attach it to the workspace. 6. Make sure the grant is set to **Active**. After the grant is active, you can use the program through the API with that workspace. If Anthropic sent you setup instructions for your program, follow those next. ## 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. - **You don’t see your program, the Other grants section is empty, or the Programs tab is missing.** Your organization may not have a program yet, or you might not be an organization Admin. Contact your Anthropic account team or your organization Admin. - **The workspace shows as inactive.** On the program's page, click the workspace's name in the **Workspaces** table, and check the **Qualifications** panel for an unmet requirement. - **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. - **You can’t assign the program to a workspace.** Confirm that you’re an organization Admin and that you aren’t selecting the default workspace. Some programs can’t be assigned to the default workspace, so create a dedicated workspace if you need one. - **The API returns a 401 error.** Confirm your SSO session is active (interactive) or your federated token hasn't expired (workload), and that your credential is scoped to the workspace. - **The API returns a 404 error for the model.** Double-check the model string and confirm your request is scoped to the workspace, not the default workspace. --- ## Assign tasks from anywhere in Claude Cowork | Claude Help Center Source: https://support.claude.com/en/articles/13947068-assign-tasks-from-anywhere-in-claude-cowork Path: 21-Account-Support/assign-tasks-from-anywhere-in-claude-cowork.md # Assign tasks from anywhere in Claude Cowork **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, and it’s in beta for Enterprise plans, where an admin turns it on as **Chat and Cowork unified (beta)**. If 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)**. For Enterprise owners, see **[Set up and manage the new unified Claude experience for your Enterprise organization](../13-Enterprise-Admin/set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization.md)**. 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](https://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. --- ## Can I have a Claude account and a Console account? | Claude Help Center Source: https://support.claude.com/en/articles/8987223-can-i-have-a-claude-account-and-a-console-account Path: 21-Account-Support/can-i-have-a-claude-account-and-a-console-account.md # 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. Claude Max and Team plans include monthly credits for the Claude API. To claim your credits, you link a Claude Console organization to your plan. Learn more about **[monthly API credits for Max and Team plans](https://support.claude.com/en/articles/17154008)**. **Tip:** Sign in to the Claude Console with the same email you use for your Claude account. --- ## Move your personal Claude account to a Team or Enterprise organization | Claude Help Center Source: https://support.claude.com/en/articles/9267400-move-your-personal-claude-account-to-a-team-or-enterprise-organization Path: 21-Account-Support/can-individuals-with-pro-or-max-plan-accounts-migrate-them-to-team-or-enterprise-plan.md # Move your personal Claude account to a Team or Enterprise organization 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. If you’ve claimed monthly API credits on your Max plan: - **Moving to a Team organization:** Your Max link ends. A Team Owner or Primary Owner can claim the team’s credits once the Team plan has been active for seven days. - **Moving to an Enterprise organization:** New credits stop. Credits you already have stay usable until they expire. Enterprise plans aren’t eligible for monthly API credits. 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](respond-to-an-enterprise-domain-claim-on-your-claude-account.md)**. ------------------------------------------------------------------------ ## 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](../17-Billing-Plans/how-do-i-cancel-my-paid-claude-subscription.md)** if applicable. 2. **[Export your data](../22-Safety-Policy/how-can-i-export-my-claude-data.md)** 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)**. --- ## Claim and migrate accounts on your domain | Claude Help Center Source: https://support.claude.com/en/articles/14625619-claim-and-migrate-accounts-on-your-domain Path: 21-Account-Support/claim-and-migrate-accounts-on-your-domain.md # Claim and migrate accounts on your domain September 2, 2026 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](can-individuals-with-pro-or-max-plan-accounts-migrate-them-to-team-or-enterprise-plan.md#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 | Claude Help Center Source: https://support.claude.com/en/articles/14604406-claude-design-admin-guide-for-team-and-enterprise-plans Path: 21-Account-Support/claude-design-admin-guide-for-team-and-enterprise-plans.md # Claude Design admin guide for Team and Enterprise plans Updated today 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 on Free, Pro, Max, Team, and Enterprise plans. It's on by default on Team plans. On Enterprise plans, it turns on by default on October 15, 2026, and owners can turn it on before then. **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 how to roll out Claude Design with a design system in place, and what to do before standalone Claude Design at **claude.ai/design** closes. 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)**. **Important:** Standalone Claude Design closes on December 14, 2026. Before then, check that **Artifacts** and **Design systems** are on in **[Organization settings \> Artifacts](https://claude.ai/admin-settings/artifacts)**, so users can move their projects and design systems. On Enterprise plans, **Design systems** is off by default. If your organization has a retention period that covers artifacts, a project or design system that moves, or has already moved, to Claude can be permanently deleted if nobody opens it for that period. Learn more in [**Move from standalone Claude Design to Claude**](../15-Claude-AI-Features/migrate-from-standalone-claude-design-to-claude-claude-help-center.md) and **[Configure custom data retention controls for Enterprise plans](https://support.claude.com/en/articles/10440198)**. 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 On Enterprise plans, you can phase access to standalone Claude Design using **[custom roles](../17-Billing-Plans/manage-custom-roles-on-enterprise-plans.md)**, 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 supports export to HTML bundles, PPTX, PDF, and Google Slides, 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 | Claude Help Center Source: https://support.claude.com/en/articles/12109679-creating-a-new-account-after-deletion Path: 21-Account-Support/creating-a-new-account-after-deletion.md # Creating a new account after deletion March 16, 2026 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. --- ## Cyber Verification Program Security Requirements | Claude Help Center Source: https://support.claude.com/en/articles/17202708 Path: 21-Account-Support/cyber-verification-program-security-requirements-claude-help-center.md # Cyber Verification Program Security Requirements Customer must meet and maintain the following security requirements for each Cyber Verification Program access level that Customer holds (“**Access Level**”). These requirements apply to Approved Users and to Granted Workspaces. ## 1. All Access Levels. 1. **Security Contact.** Customer must provide Anthropic with a named security contact who may receive security and misuse alerts and is able to act on them. 2. **Incident Reporting.** Customer must report suspected breaches or misuse involving the grant to Anthropic within 72 hours, or within 24 hours for a security incident. Reporting can be done at [\[email protected\]](https://support.claude.com/cdn-cgi/l/email-protection#84f7e1e7f1f6edf0fdc4e5eaf0ecf6ebf4ede7aae7ebe9) or your Account team contact. 3. **Cooperation.** Customer must investigate any abuse that Anthropic identifies within 48 hours, work with Anthropic to remediate it, and respond to misuse inquiries within seven (7) days. 4. **Personal Access.** Each Approved User must sign in as themselves. Shared sign-ins, seats, sessions, and workload identities, and browser extensions or proxy tools that expose a session to other people that are not explicitly an Approved User meeting all the requirements below, are not permitted. 5. **Usage Attribution.** User profiles must remain enabled on the Granted Workspace so that requests can be attributed to a named user or workload identity. 6. **Notice of Changes.** Customer must notify Anthropic within thirty (30) days of a material change to its security posture, ownership, headquarters, or security contact. 7. **Ongoing Review.** Anthropic may request that Customer provide evidence of compliance with these Cyber Verification Program Security Requirements. ## 2. Defense Access. 1. **Multi-Factor Authentication.** At the time of Customer’s access to the CVP, all accounts that can sign in to the Granted Workspace, or hold credentials for it, must have multi-factor authentication enabled. By December 15, 2026 (the "Cutoff Date"), all such accounts must use phishing-resistant multi-factor authentication as defined in the CISA fact sheet "Implementing Phishing-Resistant MFA" and with NIST SP 800-63B-4, meaning (i) a FIDO2/WebAuthn security key, (ii) a passkey, on the device or in a password manager, or (iii) a smartcard/PIV, and email magic-link sign-in must be disabled. SMS, voice, emailed codes, authenticator-app codes, and push approvals do not qualify. 2. **Credential Management.** By the Cutoff Date, downloaded, exported, or otherwise long-lived static credentials, including API keys, must not be used to access the model. The following requirements apply to Customer based on the deployment platform(s) through which Customer accesses the model. For each applicable platform, all Approved Users and all workloads must authenticate using short-lived credentials issued and managed by that platform's native identity service. 1. **Anthropic (first-party API and Console).** Static or long-lived API keys are not permitted, including for interactive access to Claude Console, Claude for Enterprise, Claude Code, and other Anthropic application surfaces. 2. **Google Vertex.** Downloaded service account JSON key files are not permitted. 3. **Amazon Web Services (Amazon Bedrock).** IAM user access key pairs (access key ID and secret access key) are not permitted, with the exception of short-term Bedrock API keys that expire within 12 hours or the length of the Bedrock session, whichever is shorter. 4. **Microsoft Azure (Azure AI Foundry).** API keys and exported service principal client secrets or certificates are not permitted. 3. **Interim API Keys.** Until the Cutoff Date, API keys are permitted under a Defense Access grant only if each key is (i) stored in a secrets manager or password manager, (ii) assigned to a single person or workload, (iii) kept out of source code, and (iv) replaced at least every 7 days. Anthropic may limit the lifetime of API keys under a Defense Access grant to 7 days, and may disable API keys on the Granted Workspace from the Cutoff Date. 4. **Approved Users.** There is no default limit on the number of Approved Users at this Access Level. ## 3. Defense Access for Individuals. 1. Individuals are eligible for Defense Access only. Where the grant is held by an individual this section applies 1. **Multi-Factor Authentication.** The individual must sign in to the Anthropic account that holds the grant only through Google or an equivalent identity provider. From the date access is granted, that account must have multi-factor authentication enabled. By December 15, 2026 (the "Cutoff Date"), that account must use phishing-resistant multi-factor authentication, meaning a security key, a passkey, or a smartcard/PIV, and the individual must not use email magic-link sign-in. SMS, voice, emailed codes, authenticator-app codes, and push approvals do not qualify. 2. **Credential Management.** By the Cutoff Date, static or long-lived credentials, including API keys, must not be used to access the model. Claude Code, Claude Console, and claude.ai authenticate through OAuth. Programmatic access for workloads, where offered, must use Workload Identity Federation. Until the Cutoff Date, one API key is permitted only if it is (i) stored in a password manager or local secrets store, (ii) never shared or placed in source code, and (iii) replaced at least every 7 days. Anthropic may limit the lifetime of API keys under the grant to 7 days, and may disable API keys from the Cutoff Date. 3. **Personal Access.** The individual is the only person who may use the access. Shared sign-ins or sessions, and browser extensions or proxy tools that expose the session to others, are not permitted. 4. **Monitoring.** All traffic under the grant is retained and monitored. Zero data retention is not available. 5. Of the All Access Levels requirements, Incident Reporting, Cooperation, and Ongoing Review apply to an individual. ## 4. Red Team Access. 1. **Credential Management.** The following requirements apply to Customer based on the deployment platform(s) through which Customer accesses the model. For each applicable platform, all Approved Users and all workloads must authenticate using short-lived credentials issued and managed by that platform's native identity service. 1. **Anthropic (first-party API and Console).** Static or long-lived API keys are not permitted, including for interactive access to Claude Console, Claude for Enterprise, Claude Code, and other Anthropic application surfaces. 2. **Google Vertex.** Downloaded service account JSON key files are not permitted. 3. **Amazon Web Services (Amazon Bedrock).** IAM user access key pairs (access key ID and secret access key) are not permitted, with the exception of short-term Bedrock API keys that expire within 12 hours or the length of the Bedrock session, whichever is shorter. 4. **Microsoft Azure (Azure AI Foundry).** API keys and exported service principal client secrets or certificates are not permitted. 2. **Multi-Factor Authentication.** At the time of Customer’s access to the CVP, phishing-resistant multi-factor authentication must protect (i) all accounts that can sign in to the Granted Workspace or hold credentials for it, (ii) Approved Users' accounts at Customer's identity provider, (iii) AWS, Google Cloud, or Azure identities that can call the model, (iv) administrative access to anything that issues or stores model credentials, and (v) any virtual desktop or enclave used to meet these requirements. Phishing-resistant multi-factor authentication means (i) a FIDO2/WebAuthn security key, (ii) a passkey, on the device or in a password manager, or (iii) a smartcard/PIV, consistent with the CISA fact sheet "Implementing Phishing-Resistant MFA" and NIST SP 800-63B-4. SMS, voice, emailed codes, authenticator-app codes, and push approvals do not qualify, and email magic-link sign-in must be disabled. 3. **Organization Accounts.** Approved Users must sign in with accounts on Customer's domain. Personal and webmail accounts are not permitted. 4. **Approved Users.** The Granted Workspace is limited to twenty-five (25) Approved Users who personally perform or directly supervise the work for which the grant was approved. Workload identities do not count toward that number. Customer may request additional Approved Users seats in writing (email sufficing). Only named administrators may add members, change roles, or create workload identities or credentials on the Granted Workspace. 5. **Gateways.** If Customer operates a gateway or proxy in front of the model, it must admit only Approved Users or their workload identities, use a short-lived credential of its own, and keep its logs and transcripts restricted to Approved Users and Customer's security, IT-administration, or trust-and-safety teams. 6. **Customer-Operated Credential Systems.** Credentials issued by Customer's own systems must expire within 12 hours, must be issued only after phishing-resistant multi-factor authentication (for people) or a verified workload identity (for services), and must leave no static credential on endpoints, in source code, or in shared stores. The keys and secrets that can issue model credentials must be kept in a secrets manager or key management service with access logging. 7. **Revocation.** Customer must be able to revoke any compromised credential or identity within 24 hours. 8. **Offboarding.** Customer must remove departed or reassigned Approved Users, and their workload identities, from the Granted Workspace within three (3) business days. 9. **Network Egress.** Wherever the model performs offensive or agentic work, outbound traffic must be limited to an allow-list enforced off the host, and must be logged. Workstations used only for interactive prompting may use an on-host allow-list if the agentic work itself runs in a sandbox that cannot change that list. 10. **Managed Devices.** Approved Users must reach the Granted Workspace only from devices that Customer controls that receive automatic or regularly scheduled operating-system updates, not personal devices. 11. **Background Checks.** Every Approved User, including contractors, must have passed an identity check and, where lawful, a criminal-history check. Where local law restricts criminal checks, identity, right-to-work, or employment verification is accepted. Government vetting or a clearance satisfies this requirement. 12. **Incident Procedure.** Customer must maintain a documented procedure for suspected compromise or misuse of the grant that covers credential revocation and seat suspension. 13. **Government Entities.** A FISMA Authority to Operate with an annual independent Inspector General assessment against NIST SP 800-53, or an equivalent national scheme, satisfies the Managed Devices, Background Checks, and Incident Procedure requirements. All other requirements continue to apply. ## 5. Specialized Access. 1. **Multi-Factor Authentication.** At the time of Customer’s access to the CVP, phishing-resistant multi-factor authentication must protect (i) all accounts that can sign in to the Granted Workspace or hold credentials for it, (ii) Approved Users' accounts at Customer's identity provider, (iii) AWS, Google Cloud, or Azure identities that can call the model, (iv) administrative access to anything that issues or stores model credentials, and (v) any virtual desktop or enclave used to meet these requirements. Phishing-resistant multi-factor authentication means (i) a FIDO2/WebAuthn security key, (ii) a passkey, on the device or in a password manager, or (iii) a smartcard/PIV, consistent with the CISA fact sheet "Implementing Phishing-Resistant MFA" and NIST SP 800-63B-4. SMS, voice, emailed codes, authenticator-app codes, and push approvals do not qualify, and email magic-link sign-in must be disabled. 2. **Credential Management.** The following requirements apply to Customer based on the deployment platform(s) through which Customer accesses the model. For each applicable platform, all Approved Users and all workloads must authenticate using short-lived credentials issued and managed by that platform's native identity service. 1. **Anthropic (first-party API and Console).** Static or long-lived API keys are not permitted, including for interactive access to Claude Console, Claude for Enterprise, Claude Code, and other Anthropic application surfaces. 2. **Google Vertex.** Downloaded service account JSON key files are not permitted. 3. **Amazon Web Services (Amazon Bedrock).** IAM user access key pairs (access key ID and secret access key) are not permitted, with the exception of short-term Bedrock API keys that expire within 12 hours or the length of the Bedrock session, whichever is shorter. 4. **Microsoft Azure (Azure AI Foundry).** API keys and exported service principal client secrets or certificates are not permitted. 3. **Single Sign-On and Organization Accounts.** Approved Users must sign in with accounts on Customer's own domain. Approved Users must sign in with organization-domain identities federated through Customer's single sign-on. Personal, webmail, and non-federated accounts are not permitted. 4. **Approved Users.** The Granted Workspace is limited to 25 Approved Users who personally perform or directly supervise the work for which the grant was approved. Workload identities do not count toward that number. Customer may request additional Approved Users seats in writing (email sufficing). Only named administrators may add members, change roles, or create workload identities or credentials on the Granted Workspace. 5. **Gateways.** If Customer operates a gateway or proxy in front of the model, it must admit only Approved Users or their workload identities, use a short-lived credential of its own, and keep its logs and transcripts restricted to Approved Users and Customer's security, IT-administration, or trust-and-safety teams. 6. **Customer-Operated Credential Systems.** Credentials issued by Customer's own systems must expire within 12 hours, must be issued only after phishing-resistant multi-factor authentication (for people) or a verified workload identity (for services), and must leave no static credential on endpoints, in source code, or in shared stores. The keys and secrets that can issue model credentials must be kept in a secrets manager or key management service with access logging. 7. **Revocation.** Customer must be able to revoke any compromised credential or identity within 24 hours. 8. **Offboarding.** Customer must remove departed or reassigned Approved Users, and their workload identities, from the Granted Workspace within 3 business days. 9. **Network Egress.** Wherever the model performs offensive or agentic work, outbound traffic must be limited to an allow-list enforced off the host, and must be logged. Workstations used only for interactive prompting may use an on-host allow-list if the agentic work itself runs in a sandbox that cannot change that list. 10. **Managed Devices and Malware Protection.** Approved Users must reach the Granted Workspace only from devices that Customer controls, not personal devices, and that receive automatic or regularly scheduled operating-system updates. Every device an Approved User uses to reach the Granted Workspace must be managed by Customer and must run application allow-listing or deny-listing in enforce mode, or an endpoint detection and response agent in block or prevent mode. A managed virtual desktop or enclave that meets this standard also qualifies. 11. **Background Checks.** Every Approved User, including contractors, must have passed an identity check and, where lawful, a criminal-history check. Where local law restricts criminal checks, identity, right-to-work, or employment verification is accepted. Government vetting or a clearance satisfies this requirement. 12. **Incident Procedure.** Customer must maintain a documented procedure for suspected compromise or misuse of the grant that covers credential revocation, seat suspension, and notifying Anthropic. 13. **Government Entities.** A FISMA Authority to Operate with an annual independent Inspector General assessment against NIST SP 800-53, or an equivalent national scheme, satisfies the Managed Devices and Malware Protection, Background Checks, and Incident Procedure requirements. All other requirements continue to apply. --- ## Delete your Claude account | Claude Help Center Source: https://support.claude.com/en/articles/9028421 Path: 21-Account-Support/delete-your-claude-account-claude-help-center.md # Delete your Claude account August 19, 2026 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](../22-Safety-Policy/how-can-i-export-my-claude-data.md)**. ## 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](../15-Claude-AI-Features/how-to-get-support.md)**. 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 | Claude Help Center Source: https://support.claude.com/en/articles/15263885 Path: 21-Account-Support/designate-support-contacts-for-human-support-claude-help-center.md # Designate support contacts for human support August 6, 2026 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](../17-Billing-Plans/manage-groups-and-group-spend-limits-on-enterprise-plans.md)**. 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 | Claude Help Center Source: https://support.claude.com/en/articles/11595103-designated-point-of-contact-for-users-in-the-eu Path: 21-Account-Support/designated-point-of-contact-for-users-in-the-eu.md # Designated point of contact for users in the EU May 26, 2026 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](../15-Claude-AI-Features/how-to-get-support.md)** 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. --- ## How can I access the personal information that Anthropic has on my account? | Claude Help Center Source: https://support.claude.com/en/articles/9267387-how-can-i-access-the-personal-information-that-anthropic-has-on-my-account Path: 21-Account-Support/how-can-i-access-the-personal-information-that-anthropic-has-on-my-account.md # How can I access the personal information that Anthropic has on my account? March 16, 2026 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 delete my Claude Console account? | Claude Help Center Source: https://support.claude.com/en/articles/10366376-how-can-i-delete-my-claude-console-account Path: 21-Account-Support/how-can-i-delete-my-claude-console-account.md # How can I delete my Claude Console account? 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. Only Console Admins can request deletion. For a full overview of your role's capabilities, see **[Claude Console roles and permissions](../13-Enterprise-Admin/claude-console-roles-and-permissions.md)**. ## 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. Go to the **Organization** page (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](../15-Claude-AI-Features/how-to-get-support.md)** 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 the **Billing** page (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 do I change the email address associated with my account? | Claude Help Center Source: https://support.claude.com/en/articles/8452276-how-do-i-change-the-email-address-associated-with-my-account Path: 21-Account-Support/how-do-i-change-the-email-address-associated-with-my-account.md # How do I change the email address associated with my account? March 16, 2026 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?](../22-Safety-Policy/how-can-i-export-my-claude-data.md) If you see "Contact support" instead of a "Delete account" button, you'll need to [reach out to our Support team](../15-Claude-AI-Features/how-to-get-support.md) to request assistance with deletion. --- ## How do I sign up for Claude Pro on Claude for Android? | Claude Help Center Source: https://support.claude.com/en/articles/9612892-how-do-i-sign-up-for-claude-pro-on-claude-for-android Path: 21-Account-Support/how-do-i-sign-up-for-claude-pro-on-claude-for-android.md # How do I sign up for Claude Pro on Claude for Android? March 16, 2026 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? | Claude Help Center Source: https://support.claude.com/en/articles/9266495-how-do-i-sign-up-for-claude-pro-on-the-claude-app-for-ios Path: 21-Account-Support/how-do-i-sign-up-for-claude-pro-on-the-claude-app-for-ios.md # How do I sign up for Claude Pro on the Claude app for iOS? March 16, 2026 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 Pro plan? | Claude Help Center Source: https://support.claude.com/en/articles/8325609-how-do-i-sign-up-for-the-pro-plan Path: 21-Account-Support/how-do-i-sign-up-for-the-pro-plan.md # How do I sign up for the Pro plan? August 6, 2026 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](../17-Billing-Plans/how-do-i-cancel-my-paid-claude-subscription.md)** 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](../15-Claude-AI-Features/where-can-i-access-claude.md)**, 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](../15-Claude-AI-Features/where-can-i-access-claude.md)**. --- ## How do I view and sign your Data Processing Addendum (DPA)? | Claude Help Center Source: https://support.claude.com/en/articles/7996862-how-do-i-view-and-sign-your-data-processing-addendum-dpa Path: 21-Account-Support/how-do-i-view-and-sign-your-data-processing-addendum-dpa.md # How do I view and sign your Data Processing Addendum (DPA)? March 16, 2026 *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. --- ## I’m encountering 429 errors, and I’m worried my rate limit is too low. What should I do? | Claude Help Center Source: https://support.claude.com/en/articles/8114527-i-m-encountering-429-errors-and-i-m-worried-my-rate-limit-is-too-low-what-should-i-do Path: 21-Account-Support/i-m-encountering-429-errors-and-i-m-worried-my-rate-limit-is-too-low-what-should-i-do.md # I’m encountering 429 errors, and I’m worried my rate limit is too low. What should I do? Your Claude API organization's rate limit depends on your usage tier. There are three usage tiers: Start, Build, and Scale. Accounts whose limits are managed with their account team are on a separate Custom tier. You can see your tier and current limits on the **Rate limits** page (platform.claude.com/usage/limits) in the Claude Console. If you're seeing 429 errors, you can request higher limits in the Console once you're using at least 50% of your current limits. Refer to the **[Rate limits page in our Claude Platform Docs](../04-API-Reference/Endpoints/rate-limits.md)** for more information. For custom limits, **[contact our Sales team](https://claude.com/contact-sales)**. --- ## Identity verification on Claude | Claude Help Center Source: https://support.claude.com/en/articles/14328960-identity-verification-on-claude Path: 21-Account-Support/identity-verification-on-claude.md # Identity verification on Claude August 11, 2026 Being responsible with powerful technology starts with knowing who is using it. Identity verification helps us prevent abuse, enforce our usage policies, and comply with legal obligations. We are rolling out identity and business verification for a few use cases, and you might see a verification prompt when accessing certain capabilities, as part of our routine platform integrity checks, or other safety and compliance measures. We only use your verification data to confirm who you are and not for any other purposes. ## How are we verifying? We selected Persona Identities as our verification partner based on the strength of their technology, privacy controls, and security safeguards. Follow the steps below to complete your identity or business verification process. ## What you'll need If you are verifying as an individual, have these ready: - **A valid government-issued photo ID**: the physical document, in hand - **A phone with a camera**: you may be asked to take a live selfie with your phone If you are verifying on behalf of an organization, have these ready: - **Identifying information about your organization:** legal name, address, and business registration number - **A valid government-issued photo ID**: the physical document, in hand - **A phone with a camera**: you may be asked to take a live selfie with your phone ## Accepted ID types Original, physical **government-issued** photo IDs from most countries are acceptable. Common examples include: - Passport - Driver's license or state/provincial ID card - National identity card Your ID must be issued by a government, clearly legible, undamaged, not expired, and include a photo of you. **The following are not acceptable:** - Photocopies, screenshots, scans, or photos of a photo - Digital or mobile IDs (such as mobile driver's licenses) - Non-government IDs: student IDs, employee badges, library cards, bank cards - Temporary paper IDs ## How your data is protected We know that identity verification can be a meaningful ask, and we've designed this process to protect your information at every step. - Anthropic is the data controller for your verification data. That means we set the rules for how it's used and how long it's kept. - Our fraud prevention partners are contractually limited in how they can use your data—only to provide and support verification and fraud prevention—and to protect it with industry-standard security controls. - Your ID and selfie are collected and held by Persona, not on Anthropic's systems. Anthropic can access verification records through Persona’s platform when needed—for example, to review an appeal—but we don't copy or store those images ourselves. All data passing through and to Persona is encrypted in transit and at rest. For full details on how we handle personal data, see our **[Privacy Policy](https://www.anthropic.com/legal/privacy)**. ## What we're *not* doing - **We are not using your identity data to train our models.** Verification data is used solely to confirm who you are and to meet our legal and safety obligations. - **We are not collecting more than we need.** We ask for the minimum information required to verify your identity. - **We are not sharing your identity data with anyone else.** Verification data stays between you, Anthropic, and our fraud prevention partners, except where legally required to respond to valid legal processes. Your verification data is never shared with third parties for marketing, advertising, or any purpose unrelated to verification and compliance. ## What if my verification fails? Verification can fail for a number of reasons: a blurry photo, an unreadable document, an expired ID, an incorrect registration number, or a technical issue. If your verification is unsuccessful: 1. **Try again.** You'll have multiple attempts within the verification flow—most failures are resolved by retaking the photo in better lighting, removing or using a different government-issued photo ID. 2. **Check your document.** Make sure your ID is undamaged and clearly legible. 3. **Contact us.** If you've used your attempts and still can't verify, reach out to us via this **[help form](https://claude.com/form/identity-verification-help)** and we'll take a look. **Why did my account get banned after verification?** As part of our safety processes, we may ban an account for a variety of reasons, including repeated violations of our Usage Policy or Terms of Service. If you feel your account has been wrongly banned, please **[fill out the appeal form](https://docs.google.com/forms/d/e/1FAIpQLSdcTocgFJXSJzFJzVc47nxKmjeVhXDfgRaifH3DUZhYarA8vA/viewform?usp=dialog)** with your account information so our Safeguards team can further investigate why your account was disabled. ## Questions? If you have questions about identity verification, your data, or the verification process, reach out to us via this **[help form](https://claude.com/form/identity-verification-help)**. --- ## Important considerations before enabling single sign-on (SSO) and JIT/SCIM provisioning | Claude Help Center Source: https://support.claude.com/en/articles/10276682-important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisioning Path: 21-Account-Support/important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisioning.md # 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 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)](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](https://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. If an organization you want to invite doesn’t appear in the invite list, check the following: - **The list shows a limited number of results at a time.** Search for a distinctive part of the organization’s name. Search matches organization names, not organization IDs. - **Every member needs a verified-domain email address.** If any member has an email address outside your parent organization’s verified domains, the organization doesn’t appear. - **The organization may already belong to another parent organization** with separate verified domains and SSO. **[Contact support](https://support.claude.com/en/articles/9015913)** to have it detached. 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. Search for and select the organization you want to invite, then 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](https://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](https://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](../22-Safety-Policy/how-can-i-export-my-claude-data.md)** 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. --- ## Introduction to prompt design | Claude Help Center Source: https://support.claude.com/en/articles/7996853-introduction-to-prompt-design Path: 21-Account-Support/introduction-to-prompt-design.md # Introduction to prompt design March 16, 2026 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 Console account | Claude Help Center Source: https://support.claude.com/en/articles/13371040-log-in-to-your-console-account Path: 21-Account-Support/log-in-to-your-console-account.md # Log in to your Console account August 18, 2026 When you navigate to the **[Claude Console](../04-API-Reference/Other/playground.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)](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?](can-i-have-a-claude-account-and-a-console-account.md)** --- ## Log in to your Claude account | Claude Help Center Source: https://support.claude.com/en/articles/13189465-logging-in-to-your-claude-account Path: 21-Account-Support/logging-in-to-your-claude-account.md # Log in to your Claude account When you open Claude on a web browser ([claude.ai](https://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](verifying-your-phone-number.md)**. 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. --- ## My prompt isn’t giving me a helpful answer. | Claude Help Center Source: https://support.claude.com/en/articles/7996857-my-prompt-isn-t-giving-me-a-helpful-answer Path: 21-Account-Support/my-prompt-isn-t-giving-me-a-helpful-answer.md # My prompt isn’t giving me a helpful answer. March 16, 2026 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 | Claude Help Center Source: https://support.claude.com/en/articles/13917861-onelogin-sso-scim-email-mismatch Path: 21-Account-Support/onelogin-sso-scim-email-mismatch.md # OneLogin SSO/SCIM email mismatch March 24, 2026 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 | Claude Help Center Source: https://support.claude.com/en/articles/13917899-onelogin-sso-setup Path: 21-Account-Support/onelogin-sso-setup.md # OneLogin SSO setup August 6, 2026 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 | Claude Help Center Source: https://support.claude.com/en/articles/13756069-public-sector-faqs Path: 21-Account-Support/public-sector-faqs.md # Public Sector FAQs March 25, 2026 ## 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](../19-Reference/offering-expanded-claude-access-across-all-three-branches-of-government.md)** ### 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](../15-Claude-AI-Features/product-claude-code-fad1ab4b.md)**. ### 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](../13-Enterprise-Admin/business-associate-agreements-baa-for-commercial-customers.md)** - Certifications overview (HIPAA, SOC 2, ISO 27001): **[What Certifications has Anthropic obtained?](../19-Reference/what-certifications-has-anthropic-obtained.md)** - **[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](../19-Reference/claude-in-amazon-bedrock-fedramp-high.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. 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](../19-Reference/claude-in-amazon-bedrock-fedramp-high.md)** ------------------------------------------------------------------------ ## 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](../04-API-Reference/Guides/build-with-claude-claude-on-vertex-ai.md)** ### 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](../19-Reference/claude-in-amazon-bedrock-fedramp-high.md)** **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](../17-Billing-Plans/pricing.md#team-&-enterprise)** 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.md)** --- ## Cyber Verification Program | Claude Help Center Source: https://support.claude.com/en/articles/14604842-real-time-cyber-safeguards-on-claude-opus-and-sonnet Path: 21-Account-Support/real-time-cyber-safeguards-on-claude-opus-and-sonnet.md # Cyber Verification Program Updated today **Updated October 2026.** The CVP previously covered Claude Opus and Sonnet with a single level of access. We are now offering three access tiers for Claude Opus 5.5, our most capable cyber model yet, Claude Sonnet 5.5, Claude Mythos 5.1, and new models moving forward. For more details, register for our upcoming **[webinar on the Cyber Verification Program](https://claude.com/resources/webinars/inside-the-cyber-verification-program)** on October 14th at 9am PT. ## Overview The Cyber Verification Program (CVP) makes advanced cyber capabilities and reduced blocking classifiers available to qualifying security professionals. Each tier includes access to our most capable models, including Claude Opus 5.5, Claude Sonnet 5.5, Claude Mythos 5.1, and new models moving forward. Our generally available models can still be used by all users for secure code review, threat modeling, patching known issues, finding vulnerabilities in your own source code, and triaging security alerts. However, other cyber security work like malware analysis or exploit validation may be interrupted by our safety classifiers. If you are a cybersecurity professional, and your work is being blocked, apply for the Cyber Verification Program using the instructions below in the “How to Apply” section. ## Access tiers ## How to apply Apply through the **[Verification Portal](https://portal.anthropic.com/programs)**. We aim to send an email notification with our review decision or request for more information within seven business days. Fill out a single application, and we will place you at the highest tier based on the information we receive. Apply once per organization. Individual users within organizations should not apply separately as organization admins can designate seats for the program. Independent researchers, maintainers, and bug bounty hunters apply as individuals. Please note that only Defense access is available for individual applicants at this time. What you'll need: - Details of your organization and the person applying, for verification. See **[identity verification on Claude](identity-verification-on-claude.md)** - A description of your security work - An attestation to the security controls applicable to your desired tier [TABLE] ## Once you're approved - The **[Usage Policy](https://www.anthropic.com/legal/aup)** still applies in full. - You may leverage CVP enabled models for internal use such as running the model over your own code. See the **Building client-facing products** section for more information. - We may review, narrow, or withdraw a grant. ## Building client-facing products Your CVP access covers security work on your organization's own code, products, and infrastructure. Using your CVP access to deliver work to your customers, for example by running the model against a customer's code or systems or by letting customers use something you've built on the model, requires approval. Please submit a separate application for **each service or product you offer**. **Managed services: applications are open.** In a managed service, your own staff use the model to do security work for a customer, on code and systems the customer owns or operates. The customer receives only finished deliverables, such as a findings report or patched code. Your customers never prompt the model, interact with it, or see its raw output. **Products: not open yet.** In a product, your customers use something you built on the model, such as a scanner or a code-review tool, even if they can only trigger or configure it. Products are categorized as follows: - **Constrained products:** Customers use something built on the model but cannot direct it or see its raw output - **Unconstrained products:** Any other customer-facing product, such as one where customers can give the model their own instructions or see its responses as written. While we are not yet reviewing applications for products, you can express interest by selecting “Constrained product” or “Unconstrained product,” then select “Express interest.” We'll contact you when we're accepting product applications, and you'll need to submit a full application then. ### How to apply for a managed service You must be an admin of an organization approved for the Cyber Verification Program. 1. Sign in to the **[Verification Portal](https://portal.anthropic.com/programs/cyber-productization)**, open “Programs,” then choose “Cyber productization.” 2. Select “Register an offering,” then choose “Managed service.” 3. Name the service and describe how it runs, who operates the model, and what your customers receive. Then confirm the six security commitments and give a security contact and the name and title of the company officer who signs off. 4. Accept the Anthropic Cyber Defender Partner Addendum, then select “Submit” for review. 5. To apply for another managed service, go back to the Cyber productization page and repeat steps 2 to 4. ### How to express interest in a constrained or unconstrained product You must be an admin of an organization approved for the Cyber Verification Program. 1. Sign in to the **[Verification Portal](https://portal.anthropic.com/programs/cyber-productization)**, open “Programs,” then choose “Cyber productization.” 2. Select “Register an offering,” then choose “Constrained” or “Unconstrained” product. 3. Describe the product in one line. 4. Add a name and email. 5. Select “Express Interest." Check your answers before you submit: you can't edit or withdraw an application after you send it. You can follow each application's status on the **Cyber productization** page. Don't serve customers through a service until it's approved. Until then, you can keep using your CVP access for work on your own code, products, and infrastructure. ## Security controls and requirements Each access level has its own security requirements. The security requirements for each tier are outlined in detail in the **[CVP Security Requirements Help Center article](cyber-verification-program-security-requirements-claude-help-center.md)**. For existing CVP customers, your current access and corresponding security requirements are not impacted and stay under your current terms. **Defense Access will have until *December 15, 2026* to adopt phishing-resistant multi-factor authentication and to stop using API keys.** Until then, multi-factor authentication of some kind is required, and API keys will expire every seven days. We recommend migrating now to using **[Workload Identity Federation](../04-API-Reference/Other/manage-claude-workload-identity-federation.md)**. ## Provisioning access using your Grants After your application has been approved, the steps to provision access to your Grants vary depending on how you access Claude. [TABLE] ## Existing members If your organization was previously enrolled in Project Glasswing or CVP, you don't need to apply again to join the updated CVP program. Your existing access to the models you use today via Project Glasswing or CVP will keep working under your existing terms, and you'll be transitioned to the relevant new program tier for Claude Opus 5.5, Claude Sonnet 5.5, and Claude Mythos 5.1. The Cyber Verification Program requires data retention, which enables us to monitor for harmful cyber misuse in the program and detect bad actors. Once Enterprise Frontier Safeguards (EFS) is available, eligible organizations will be able to store data in cloud infrastructure they control. To register interest in EFS, fill out **[this form](https://claude.com/form/enterprise-frontier-safeguards)**. In the meantime, organizations with a data retention exemption for Claude Fable or Claude Mythos models can also use CVP with zero data retention (ZDR) on all supported models. Until EFS is available, if your organization has access to Claude Fable or Claude Mythos with ZDR, you can also use CVP with ZDR. ## If you’re not approved for a tier The Cyber Verification Program is designed to get advanced cyber capabilities to defenders as widely as we responsibly can. Access depends on a number of factors, including the work an organization does, our ability to verify who it is, and the security controls it has in place. ### Why might an organization not have access? Eligibility reflects a range of factors, including one or more of the following: 1. **The nature of the work.** The program is built for defense. Organizations whose main business falls outside that scope may not be eligible. 2. **Verification.** We need to be able to confirm who an organization is and what it does. 3. **The environment an organization operates in.** We consider the legal and regulatory environment, the risk that advanced capabilities could be diverted, and the risk that access could be compelled. 4. **Who the work is ultimately for.** The risk that capabilities are passed on or repurposed is higher where an organization primarily serves military, intelligence, or law enforcement customers. We take a more cautious approach in those cases. 5. **The tier applied for.** Requirements rise with the level of access. For Specialized Access, every organization is reviewed in depth in collaboration with the US government. Existing members of Project Glasswing will transition to this tier and don't require reapproval for current models. We continue to work with the US government to expand the number of eligible organizations, both in the US and internationally. ## Frequently asked questions ### Can I apply as an individual? Yes, for Defense Access, on a paid plan. Red Team Access and Specialized Access tiers are for organizations only. ### My organization has a grant, but I'm still blocked Check that your admin has provisioned you access to the relevant CVP grant(s). If using a Claude Console account, ensure you're in the correct Workspace and that the activity falls inside your tier. ### Why is CVP on Amazon Bedrock only available to customers with Enterprise Frontier Safeguards? Amazon Bedrock does not yet support human review of automated safety flags, which CVP requires by default. As a result, on Bedrock, CVP is only available to organizations that have a data retention exemption for Fable 5.1; those customers can also use CVP with ZDR and will be eligible to use CVP with Enterprise Frontier Safeguards once available. We're working to expand CVP to all customers on Bedrock. ### I’m approved, why can’t I access Mythos on my preferred Cloud provider? Access to Mythos on third-party cloud providers will trail approval by approximately five business days. ### How do usage limits for Mythos 5.1 work? On Pro and Max plans, Mythos 5.1 follows the same usage rules as Fable 5.1. - For Pro plans, Mythos 5.1 is available only with usage credits. It doesn’t draw on your plan’s included usage, so you’ll need usage credits turned on to use it. - For Max plans, Mythos 5.1 and Fable share a single allowance of up to 50% of your weekly usage limit, not a separate allowance for each model. This usage also counts toward your plan's regular usage limits. Once the shared allowance is used up, you can keep using Mythos 5.1 or Fable with usage credits (if you have them turned on), or switch to another model. --- ## Respond to an Enterprise domain claim on your Claude account | Claude Help Center Source: https://support.claude.com/en/articles/14625626-respond-to-an-enterprise-domain-claim-on-your-claude-account Path: 21-Account-Support/respond-to-an-enterprise-domain-claim-on-your-claude-account.md # Respond to an Enterprise domain claim on your Claude account August 17, 2026 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](can-individuals-with-pro-or-max-plan-accounts-migrate-them-to-team-or-enterprise-plan.md)**. ## 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](can-individuals-with-pro-or-max-plan-accounts-migrate-them-to-team-or-enterprise-plan.md#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](../22-Safety-Policy/how-can-i-export-my-claude-data.md)** 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?](../13-Enterprise-Admin/who-owns-and-manages-the-data-of-my-team.md)** ### 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 your design system in Claude Design | Claude Help Center Source: https://support.claude.com/en/articles/14604397 Path: 21-Account-Support/set-up-your-design-system-in-claude-design-claude-help-center.md # Set up your design system in Claude Design Updated today 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 "Move team design systems" in the banner. Each design system becomes an artifact Claude can use in any chat, including in Claude Code. Design systems may need some cleanup after you move them, so each one shows a banner where you can click "Let Claude clean it up," and Claude tidies its guide, tokens, and components. If your organization has a retention period that covers artifacts, a design system you moved can be permanently deleted if nobody opens it for that period. Opening a design or deck that uses the design system doesn't count as opening it. ## 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)**. ------------------------------------------------------------------------ ## Use a design system with a keyboard To get into and out of the artifact panel, see **[Use artifacts with a keyboard or screen reader](../15-Claude-AI-Features/use-artifacts-with-a-keyboard-or-screen-reader-claude-help-center.md)**. That article also explains what focus means, what to do on a Mac laptop or in Safari, and how shortcuts are written. A design system opens as a list of sections beside the section you're reading. Return on a section in the list moves into it, Cmd+F6 (Ctrl+F6 on Windows) moves between the list and the section, and Cmd+Z (Ctrl+Z on Windows) undoes a change when you're not in a text box. **Note:** Live component previews in a design system can't be reached with Tab, so they can't be operated from the keyboard. Each component's name and notes can be read. ------------------------------------------------------------------------ ## 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. --- ## Claude Help Center Source: https://support.claude.com/en/articles/10280258-setting-up-single-sign-on-on-the-claude-console Path: 21-Account-Support/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. --- ## Set up single sign-on (SSO) | Claude Help Center Source: https://support.claude.com/en/articles/13132885-setting-up-single-sign-on-sso Path: 21-Account-Support/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-provisioning.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 **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](important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisioning.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 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](../17-Billing-Plans/managing-members-on-team-and-enterprise-plans.md)**. **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. ------------------------------------------------------------------------ ## Update your SSO certificate or client secret When your Identity Provider’s X.509 signing certificate (SAML) or client secret (OpenID Connect) 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/identity)** 2. In the **Authentication** section, click “Manage SSO.” 3. Update the credential for your connection type: 1. **SAML:** Find the **Metadata configuration** section, click “Edit,” and update your certificate information. 2. **OpenID Connect:** Replace the expired client secret with the new one from your Identity Provider. OpenID Connect connections don’t use a certificate. 4. 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 or client secret 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 it. To avoid this, note the expiry date of your certificate or client secret in your Identity Provider and rotate it ahead of time. ------------------------------------------------------------------------ ## Turn 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 or client secret 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. --- ## Verify your phone number | Claude Help Center Source: https://support.claude.com/en/articles/8287232-verifying-your-phone-number Path: 21-Account-Support/verifying-your-phone-number.md # Verify your phone number August 17, 2026 When you first create a Claude account, you’ll be asked to enter your phone number from a **[supported location](../15-Claude-AI-Features/where-can-i-access-claude.md)** to receive a verification code via text message. Once you receive the text message with the code, type it into the box and click "Verify code." This will complete the verification and account creation process and allow you to start chatting with Claude. ## Why do I need to verify my phone number? Verifying your phone number helps us prevent spam and abuse. Your phone number is only used for account verification and not for any other purposes. ## What happens during phone verification? We’ll send a six-digit verification code to your phone number via text message. Enter this code on the verification screen to confirm you have access to that phone number. ## Limitations We only accept phone numbers from our supported locations at this time. Additionally, you cannot use VoIP numbers, Google Voice, phone numbers created using apps, landlines, or other numbers that can’t receive texts to verify your account. ## Frequently asked questions ### What if I don't have a phone number from a supported location? Only users physically located in one of our supported locations can create and use Claude accounts. We also require a phone number from a supported location to create an account, and there isn’t a way to skip this step. ### I don't have a phone that can receive text messages. How can I create an account? You must have a phone number that can receive a verification code via text message to create and use a Claude account. We require phone verification for all new users, and there isn’t a way to skip this step. ### I didn't receive my phone verification code. What should I do? The code may take a few minutes to arrive via text, but if it has been more than five minutes, click "Try again" to reset the modal and reenter your phone number, ensuring that you’re entering the correct one. ### I’m still not receiving the code, or I’m seeing "Error sending code. Double check your phone number." If you aren’t receiving a verification code via text after reentering your phone number, or you’re seeing an error message ("Error sending code. Double check your phone number."), you’ll need to try using a different phone number to verify your account. ### I received the text message with the verification code, but the code isn’t working. The texted verification codes are temporary, so ensure you’re entering the most recent code you received. You can use "Try again" to restart the verification and receive a new code, so you should request one and enter it as soon as you receive it ### Why am I seeing a message stating that my phone number was used too many times? If you see an error stating that your phone number is already in use, this means there are already three other Claude accounts in our system that were verified using that number. We only allow a maximum of three Claude accounts to be verified with the same phone number. If you know which email addresses are associated with these verified accounts, you should log in to one of those accounts and contact our Support team to ask for help unlinking your phone number from it. Once we unlink the number, you’ll be able to use it to verify a different account. Alternatively, you can enter a different phone number that hasn’t been used for verification yet. ### Can I change the phone number associated with my account? There isn’t a way to change your phone number associated with your Claude account once it has been verified. Please ensure you verify your account using a phone number you'll have access to long-term. --- ## What is the Life Sciences Verification Program? | Claude Help Center Source: https://support.claude.com/en/articles/16975617 Path: 21-Account-Support/what-is-the-life-sciences-verification-program-claude-help-center.md # What is the Life Sciences Verification Program? This article explains what the Life Sciences Verification Program (LSVP) is, supported use cases, and how to apply. This program is currently in beta. During the beta, LSVP runs on Anthropic's first-party products only: Claude Enterprise plans, Team plans, and the Claude Platform (API). This program doesn’t currently support Pro plans, Max plans, or cloud providers. We’ll continue to improve the program and expand access over time. You can read more in our **[blog post announcement](../19-Reference/life-sciences-verification-program.md)**. ------------------------------------------------------------------------ ## About the Life Sciences Verification Program The Life Sciences Verification Program gives verified life sciences organizations access to Claude's most capable models for internal research and development. It has a refined set of biology safeguards for these organizations so everyday scientific work runs without interruption. Claude's generally available models include safeguards that block some biology requests, because the same knowledge that advances medicine can also be misused. These safeguards can sometimes interrupt normal work such as target discovery, molecular design, clinical development, and manufacturing. LSVP lets verified organizations keep protections in place while preventing against the most serious misuse. We’ve designed these new safeguards specifically to defend against three concerning threat models: - Access compromise: malware or account takeover diverting access to a bad actor - Insider threats: rogue or coerced employees intentionally taking malicious action or diverting their access to a bad actor - Agent misuse: agents, especially working in swarms or over long-horizon tasks, taking unintended dangerous actions ## Requirements - 30-day data retention for program usage, with automated safety monitoring and human review of flagged activity in rare circumstances. - A dedicated workspace, with phishing-resistant multi-factor authentication for the Claude apps or Workload Identity Federation for the API. - Use by your own organization, for internal work only. ------------------------------------------------------------------------ ## What's included with LSVP? ### Models Access grants apply to Claude Opus 5.5, Claude Mythos 5.1, Claude Opus 5, and Claude Sonnet 5 today, and to select future models as they launch. On Sonnet 5.5, LSVP relaxes biology safeguards only through the High-risk Use add-on. Claude Fable models aren't part of LSVP and keep their full biology safeguards under every grant. If you hold an LSVP grant, use Claude Mythos 5.1 instead of Fable. The older Claude Mythos 5 preview is not offered under LSVP access. ### Seats The program includes up to 100 seats for each approved team (each team is its own grant). An organization can apply for multiple grants for different teams. ### High-risk Use add-on You’ll have access to an optional High-risk Use add-on for specific projects, such as virology or toxin research, that need further safeguards relaxed. ### Not available during the beta - **Workloads involving protected health information (PHI).** Your organization can still join for research that doesn't use PHI. See **Can we use LSVP with protected health information?** below. - **Customers who use Claude only through a cloud provider** (Amazon Web Services, Google Cloud, Microsoft Azure). The beta runs on Anthropic's first-party products only, so you need a first-party Anthropic organization. We’ll continue to improve the program and expand access over time. - **Individuals and researchers not affiliated with an organization**. We grant access to a verified organization, not to a person. - **Platforms passing access through to their own customers.** A platform can apply for its own internal research and development (R&D) today. ------------------------------------------------------------------------ ## Supported use cases LSVP is designed to support and enable the following use cases: - Drug and countermeasure discovery and preclinical support - Understanding how diseases work - Clinical development and operations - Bioinformatics, computational biology, and research data infrastructure - Diagnostics and laboratory medicine - Manufacturing, quality, and supply chain for regulated products - Regulatory affairs, medical affairs, and market access - Public health, biosurveillance, biosafety, and biosecurity - Agricultural, veterinary, and environmental biosciences - Life sciences funding and diligence - Life sciences education and training ------------------------------------------------------------------------ ## How do I apply? To apply to the Life Sciences Verification Program: 1. **Express interest.** Submit the **[Life Sciences Verification Program interest form](https://claude.com/form/life-sciences-verification-program)**. If your Anthropic account team has already invited you, skip this step. 2. **We review your interest.** If your organization is a fit for the current phase, we'll contact you and ask which Anthropic organization you'd like to use. Not every organization that submits the form will be invited during the beta. 3. **We open the application for your organization.** Once we've enabled the application, it appears in the **[Verification Portal](https://portal.anthropic.com/programs)**. It won't be visible before then. To submit an application you’ll need to verify your identity. For more information, see **[Identity verification on Claude](identity-verification-on-claude.md)**. 4. **Your organization's admin applies.** Only an Admin, Owner, or Primary Owner for your organization can submit. The application takes about 15 minutes, starting with a business verification step. 5. **We review.** Decisions typically come within about three business days. We may email your admin for more details first. 6. **You set up access.** When your application is approved, your account team will let you know and send you a guide to get started for your plan. We provision the grant to your organization automatically. ## What the application asks - Details about your organization. - One life sciences reference, such as an FDA registration, a clinical trial ID, or a public grant number. If none apply, choose "none of the above" and write a couple of sentences about your life sciences work, plus your website. - The team, what it will use Claude for, and how it will use the results. - The name of your IT admin. - A short set of attestations, including that use is internal to your organization. The application doesn’t ask for program-level science, targets, or readouts. Anything you share is subject to our confidentiality obligations. ------------------------------------------------------------------------ ## Data retention, safety review, and privacy ### Why is data retention required? LSVP relaxes the real-time classifiers that normally interrupt biology work. Without them, the way we catch misuse is through an automated review that spots patterns across many conversations. That review is designed to protect against serious biological misuse, insider misuse, and account takeover. - Program usage is retained for 30 days. - Zero data retention isn’t available. Existing zero-retention or custom-retention agreements don't apply to usage under an LSVP grant. - Retention covers only the program workspace or organization. Your other Anthropic organizations are unaffected. - Retained data is used only to identify and prevent misuse. It’s never used for training or product improvement, and it isn't analyzed for any commercial or research purpose. - Anthropic monitors program usage against the scope you shared. If something looks out of scope, we'll notify your admin directly and give you one week to explain, narrow the scope, or dispute it. ### Can we use LSVP with protected health information? Not during the beta. LSVP isn't covered under a Business Associate Agreement (BAA), so workloads involving protected health information (PHI) are out of scope. If your organization has non-PHI workloads, you can still apply. Use a separate Anthropic organization that isn't set up under your BAA and doesn't handle PHI. Organizations set up under a BAA can't receive LSVP grants. --- ## Who owns and manages the data of my Claude for Education account? | Claude Help Center Source: https://support.claude.com/en/articles/11732894-who-owns-and-manages-the-data-of-my-claude-for-education-account Path: 21-Account-Support/who-owns-and-manages-the-data-of-my-claude-for-education-account.md # Who owns and manages the data of my Claude for Education account? March 16, 2026 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](../15-Claude-AI-Features/how-to-get-support.md) 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? | Claude Help Center Source: https://support.claude.com/en/articles/11107691-why-is-a-coupon-or-promotion-not-available-for-my-account Path: 21-Account-Support/why-is-a-coupon-or-promotion-not-available-for-my-account.md # Why is a coupon or promotion not available for my account? March 16, 2026 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.