Impact on Existing Accounts
When enforcing SSO on your Enterprise account, there are two distinct categories of users to consider:
Users with existing Free/Pro/Team accounts who ARE added to your SSO application
These users will maintain access to their existing Free/Pro/Team accounts
They will have the ability to toggle between the Enterprise account and their previous accounts by clicking the profile icon with their initials in the bottom left corner
Users with existing Free/Pro/Team accounts who are NOT added to your SSO application
If "Enforce SSO for Claude.ai" is NOT enabled: These users can still access their existing accounts using the "Continue with email" option
If "Enforce SSO for Claude.ai" IS enabled: These users will be unable to access their existing Free/Pro/Team accounts
Please note, these accounts are not deleted, but can no longer be accessed as the user is unable to login via SSO.
Recommended Steps Before Implementation
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 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
Taking time to test, communicate, and plan before enabling domain capture and SSO will help ensure a successful transition and positive experience for your organization.
For detailed instructions on setting up domain capture and SSO, please refer to our guide on Setting up Single Sign-On on the Enterprise plan.