Important: If you are not already on an Enterprise plan, you will need to reach out to our Sales team to enable this feature before gaining access to the API Console Identity settings page.
Domain Capture, Single Sign-On (SSO), and Just-in-Time Provisioning (JIT) enable API Console organizations to enhance authentication security and streamline user access to console.anthropic.com. This guide assumes that:
You are an Admin on your Console account
You control the DNS settings for your company's email address domain
You control the SSO Identity Provider your company uses to log in to third-party applications (e.g. Okta, Google Workspace, etc.)
If #2 and #3 are not true, please contact your organization's IT Administrator to continue.
Note: WorkOS is Anthropic's provider for domain verification and SSO setup. More details can be found in Anthropic's Subprocessor List.
Understanding Parent Organizations
Our Single Sign-On feature introduces the concept of a “Parent Organization.” This is an entity that stores SSO settings for an organization. For multiple organizations to share the same SSO configuration, each organization needs to be linked to the same parent organization.
Enterprise Claude for Work organizations are created with a parent organization by default, but API Console accounts don’t automatically have this feature when they’re set up.
Important: If you’re part of a Claude for Work Enterprise organization that already has SSO configured, your API Console organization may already be linked to the same parent organization. You can verify this by checking if the Identity settings page is accessible at console.anthropic.com/settings/identity.
If your organization does have an Enterprise Claude for Work account and you’d like to tie the organization’s API Console account to the same SSO settings/parent organization:
Reach out to your Account Manager to request a merge proposal.
Once they confirm this, it will be emailed to these approvers in both the organizations:
Console Admins
Enterprise Owners/Primary Owners
After one approver within each organization approves the proposal via the email, the merge will complete, and the two organizations will be attached to the same parent organization.
Once the merge is complete, the incoming organization will gain access to console.anthropic.com/settings/identity to configure SSO login options, and can enable features like “Advanced Group Mappings."
If your organization does not have an Enterprise Claude for Work account, and you’re hoping to create a new parent organization specifically for your organization’s API Console account to configure SSO settings:
Note that API Console accounts are not created with parent organizations by default.
To request that a parent organization is created for your organization’s API/Console account, please fill out our Contact Sales form.
Once the parent organization is created, the Identity settings page will appear in your Console account and you can continue with the SSO setup process.
Key points about parent organizations:
Domain verification is stored at the parent organization level - once one parent organization verifies a domain, other organizations cannot verify or claim that domain.
Multiple API Console organizations can be linked under the same parent organization.
If you have both Claude for Work Enterprise and API Console organizations, they can share the same parent organization and SSO configuration.
Advanced Group Mappings allow you to control user access to specific organizations under your parent organization.
Capturing your domain
“Domain Capture” proves that you own your company's domain. Once you have confirmed that you own your domain, Anthropic can intercept login attempts for emails on your domain and require your employees to sign in via SSO.
Follow these steps to verify your domain:
Navigate to console.anthropic.com/settings/identity
This section will not appear in your API Console account if you haven't done one of the following:
Worked with our Sales team to enable the SSO feature for your Console organization.
Completed a merge proposal to link your Console to an Enterprise organization.
Click "Add Domain"
Follow the instructions to add your TXT record.
Note: if you're using a subdomain (e.g. subdomain.yourcompany.com), you should set your new TXT record on that subdomain (e.g. _acme-challenge.subdomain.yourcompany.com).
Wait up to 10 minutes for your DNS change to propagate. When you see the green "Verified" badge, you can close the instructions page.
Back on console.anthropic.com/settings/identity, you should see your domain added to the page. If you do not see it, try refreshing your page.
If your domain is listed as "Pending", click the button next to the word "Pending" to refresh your domain status.
Your domain should now be listed as "Verified."
Domain memberships
To view or download information about your verified domains and their usage across Anthropic organizations:
Navigate to claude.ai/settings/identity
Click "View Domain Memberships" in the "Domain management" section
Review the information or download your domain membership details in CSV or JSON format
Adding SSO
After capturing your domain, you can connect your SSO provider to your Console organization so users will be able to log in securely using that provider.
Navigate to console.anthropic.com/settings/identity
Click the "Add SSO" button
Follow the steps provided for your SSO provider
Once you've completed the steps for your SSO provider, navigate back to console.anthropic.com/settings/identity for further configuration options.
Note: Turning on SSO will end all current sessions of your users. They will need to log back in through SSO.
Identity provider-initiated login
While many applications support launching directly from your identity provider (e.g., clicking an app tile in Okta), Claude does not enable this flow due to security considerations. However, to provide a smoother experience for employees who are accustomed to launching apps from their identity provider:
When configuring the SSO application in your identity provider, set the login URL to
https://claude.ai/login?sso=trueinstead ofhttps://claude.ai/loginWhen employees click the Claude tile in your identity provider, they will be directed to a clear login page that guides them to authenticate via SSO
Testing SSO log-in
Before inviting your teammates, verify that everything works correctly.
Log out of your account by navigating to console.anthropic.com/logout
Try logging in again with your email address. You should be directed to your SSO provider. If you’re already logged in via your SSO provider, you may be immediately redirected and logged in to console.anthropic.com .
If you use Google Workspace on your domain, try logging in with Google. This should fail and users should be required to log in via SSO.
Adding and removing users
Managing team members in your organization depends on whether you're using Single Sign-On (SSO) or not. Once SSO is enabled, your Identity Provider (IdP) becomes the primary controller for adding members, while removal involves steps in both your IdP and Console.
Before SSO is enabled
Adding members
Navigate to console.anthropic.com/settings/members
Click the “Invite” button to add new team members
Removing members
Find the user you want to remove
Click the trash icon on the row with their name
Select "Remove"
After SSO is enabled
Adding members
Ensure that the member is part of your SSO organization and has access to the Console application.
When the user logs in for the first time, an account will be created for them (JIT provisioning) and that account will be a member of your organization.
Removing members
First, revoke the user's access to Console in your SSO provider
Then, go to console.anthropic.com/settings/members
Find the user you want to remove
Click the trash icon next to their name
Select "Remove"
Note that the user will remain logged in to console.anthropic.com until you click "Remove"
SCIM
Using SCIM, you can have group members added or deleted based on automatic updates from your IdP. This is the ideal setup for full control of group memberships.
Adding members
Add users to the SSO application in your IdP
Removing members
Remove users from the SSO application in your IdP
If you have multiple organizations under a single parent organization, then it's strongly advised that you enable “Advanced Group Mappings” for each organization. This will allow you to use IdP groups to control exactly which organizations accounts are given access to.
When Advanced Group Mappings is toggled within an organization's settings page, we'll show special "anthropic-" prefixed group names that can be added in your IdP. When members are added to these groups, they will then automatically be provisioned for access.
Manually syncing your directory
SCIM directory syncing happens automatically, but you can prompt a manual sync if needed:
From your Identity and access settings, click "Sync Now" under the Directory sync (SCIM) section.
Advanced Group Mappings
Important: To enable Advanced Group Mappings, you must be an Admin on your Console account. If you can’t access the Identity settings page, contact your Console administrator to add you as an Admin first.
As mentioned above, Advanced Group Mappings can be used to provide not just access but also role assignment. These groups will be sent to Anthropic from your identity provider, and some of the configuration options are IdP specific. As an example, we'll outline how to set this up in Okta.
SAML
For JIT based provisioning, Advanced Group Mappings will be shared at login time via your IdP’s SAML response. To have Okta share groups on login, you will need to edit the SAML section of your SSO Application.
Under “Applications” select the SSO Application you configured for Anthropic
Select “Edit” on your SAML settings
Create a “Group Attribute Statement” to share all groups prefixed with “anthropic-” to Anthropic on login.
Hereafter, all members of group names that start with “anthropic-” will be shared with Anthropic at login time.
Assign members to relevant groups in Okta before turning on Advanced Group Mapping in order to prevent lockout.
Where to edit SAML Settings
On the second page of the SAML integration page
Sharing groups by prefix
SCIM
Sharing groups via SCIM is through a different mechanism. In Okta, these are referred to as Push Groups
Visit the Push Groups page for the SSO Application
Click the “+ Push Groups” button
Create a rule to push all groups starting with the “anthropic-” prefix
Creating a rule-based push group:
Troubleshooting Common Scenarios
My Enterprise organization has SSO already; how can we set this up on our Console organization?
You will need to add API Console access with different user groups:
Verify your organizations are linked: Check if you can access console.anthropic.com/settings/identity. If you can't see this page, contact Sales to link your Console organization to your existing Parent Organization.
Ensure you're a Console Admin: You must be added as an Admin on the Console side to enable Advanced Group Mappings. Have an existing Console Admin add you, or contact your Account Manager if no Console admins exist.
Enable Advanced Group Mappings: Once you're a Console admin, navigate to console.anthropic.com/settings/identity and toggle on "Advanced Group Mappings."
Copy the group names: Copy the Console-specific group names that appear after enabling Advanced Group Mappings.
Configure your IdP: Add these new Console groups to your existing SSO application alongside your Enterprise groups.
Assign users: Add Console users to the appropriate Console groups in your IdP without requiring them to have Enterprise group membership.