This guide helps you configure Claude to use Google Workspace as your identity provider for SSO and automated user provisioning. 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 for Console parent org requirements)
Owner or Primary Owner role (Team and Enterprise) or Admin role (Console)
Google Workspace Super Admin access
Your domain verified in Claude's Identity and access settings — see Set up single sign-on for the full setup path including domain verification
Where to find your configuration values
The ACS URL, Entity ID, 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
Console organizations: go to platform.claude.com/settings/identity
Start the SSO setup flow there and keep it open alongside the Google Admin console as you work through the steps below.
Step 1 — Add a custom SAML app in Google Admin
In the Google Admin console, go to Apps → Web and mobile apps → Add app → Add custom SAML app.
Name it "Claude" and click "Next."
Download the IdP metadata XML. You'll upload this in the WorkOS setup flow when prompted.
Click "Next."
Step 2 — Enter service provider details
Enter the values from the WorkOS setup flow: ACS URL and Entity ID.
Set Name ID format to EMAIL and Name ID to Basic Information > Primary email.
Click "Next."
Step 3 — Configure attribute mapping
In the Attribute mapping step, add: Google Directory attribute: Primary email → App attribute: email.
Click "Finish."
Step 4 — Enable auto-provisioning (SCIM)
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.
In the app's settings, go to the Autoprovisioning section and click "Configure autoprovisioning" (may require enabling in Google Workspace admin settings).
Enter the Endpoint URL and Access token from the WorkOS setup flow.
Map the primaryEmail attribute to the Claude email field.
Enable provisioning and save.
Critical: Both SAML and SCIM must use primaryEmail. If someone has aliases, ensure their primary Google email matches what SCIM sends. For troubleshooting, see Google Workspace SSO/SCIM email mismatch.
Step 5 — Assign the app to people or OUs
In the app settings, click "User access."
Enable the app for the relevant Organizational Units or groups.
Click "Save."
Step 6 — Verify
If you enabled SCIM, check that provisioned people appear in your organization's member list.
Have a test user log in via SSO and confirm they land in your organization's workspace.
Need help?
See Set up single sign-on for the full end-to-end flow including domain verification and choosing a provisioning approach. If you run into issues, contact our Support team with your organization's domain and a screenshot of your SAML configuration.
