What changes when your organization enables SSO
If you already have an elyvate account and your organization switches to Single Sign-On (SSO), the transition happens mostly in the background. No manual migration is needed.
Here is what changes - and what stays the same:
What changes
You log in via your company's identity provider (Microsoft or Google) instead of email and password
elyvate no longer stores or validates your corporate password
Password rules and access policies are now controlled centrally by your IT department
What stays the same
All your data, projects, and permissions remain exactly as they were
Your account is the same - only the login method changes
How the account linking works
When SSO is enabled, elyvate automatically matches your existing account to your SSO identity using your email address. No manual action is required on your end.
Important: Always use the same email address you used before. This ensures your account is linked correctly and nothing gets lost.
Behind the scenes - Auth0 and your identity provider
When SSO is enabled, elyvate connects to your company's identity provider (IdP) via Auth0 - an enterprise-grade authentication service. This means user identities, password rules, and access policies are managed centrally by your IT department, not by elyvate.
This is expected behavior and ensures compliance with your organization's security and access standards.
Making the switch - step by step
Wait for your organization to confirm that SSO has been enabled
Go to the elyvate login page
Select "Microsoft (SSO)" - or Google, if applicable
Log in with your company credentials
Your existing account is linked automatically - you are in
Note: After the switch, you may no longer be able to log in with your previous password. This is expected. If you run into issues, see Common login issues or contact your IT department.
Key facts at a glance
Account linking is automatic - no manual migration needed
Use the same email address as before to ensure correct linking
Data, projects, and permissions are fully preserved
Password management moves to your IT department - elyvate no longer handles it
If something does not work as expected, contact your IT department first - SSO access is managed on their end