Why are we migrating SSO domains?

Mitti is standardizing all SSO connections on its own authentication domain to provide a more reliable and consistent sign-in experience. The previous legacy domain limits compatibility with features like IdP-initiated login and can cause authentication inconsistencies. Moving to the new domain reduces dependency on a third-party provider and better supports future improvements to how SSO works across the platform.

What happens after I update my SSO URL configuration?

Once you've migrated to the new domain, your SSO connection will be more stable and less prone to configuration issues. You'll also be able to test your SSO connection before turning it on for your organization , so you can confirm everything is working correctly before your users are affected.

Will this migration affect users logging into Mitti?

The migration process takes only a few minutes, and any disruption to your users' login experience will be minimal. To migrate your URL configuration, contact our support team to assist you.

Do I need to make changes in my identity provider (like Azure AD or Okta)?

Yes. Depending on how you've set up your connection, you'll need to update the URLs in your identity provider to the new domains after reaching out to our support team for assistance in migrating: Generic SAML : https://auth.safetyculture.com/login/callback?connection={name_provided_in_app} Active Directory Federation Services (ADFS) : https://auth.safetyculture.com/login/callback?connection={name_provided_in_app} You can find the new domains when you edit your SSO connection .

Does migrating the domain affect our automatic user provisioning (SCIM)?

Your user provisioning won't be affected as long as you don't delete the SSO connection on your identity provider's side. After your domains have been migrated, update your SSO configuration in your identity provider to avoid any problems.

How do I know if I’m on the legacy domain?

You can check by reviewing your SSO configuration. If the service provider assertion consumer service URL contains safetyculture.au.auth0.com , your connection is on the legacy domain and will need to be migrated. If it shows auth.safetyculture.com , you're already on the new domain, and no action is needed.

Move your single sign-on (SSO) connection off the legacy domain

Q: When do I need to migrate my SSO URL configuration?

All new SSO connections should be set up using the Mitti domain. If you have an existing SSO connection, contact our support team to assist you with the migration. Migrating early ensures your users avoid any disruption and allows time to troubleshoot if needed.

Last updated: August 27, 2026

This article is about moving your organization's single sign-on (SSO) connection off a legacy Auth0 domain. It's separate from the move of Mitti's web and mobile app domains to mitti.com.

What does this domain migration mean for my SSO setup?

Mitti is moving to its own authentication domain for SSO connections, replacing the previous legacy domain. This change standardizes SSO across Mitti and improves compatibility with features such as IdP-initiated login.

Impact on your SSO connection

If you already have SSO set up, your existing connection will continue to work and will not disrupt your users' login experience. However, it's best to contact our support team as soon as possible to assist with migrating your SSO domains, as the process takes only a few minutes.

If you're setting SSO up for the first time, simply use the new URLs provided in the setup flow.

If you're experiencing issues with an existing SSO connection, setting up a new connection using the new domain is recommended as a first troubleshooting step.

All new SSO connections should be set up using the new authentication domain. If you have an existing SSO connection, contact our support team to assist you with the migration. Migrating early ensures your users avoid any disruption and allows time to troubleshoot if needed.

Frequently asked questions

Need more help?

Was this page helpful?

Move your single sign-on (SSO) connection off the legacy domain

What does this domain migration mean for my SSO setup?

Impact on your SSO connection

Frequently asked questions

Need more help?

Relevant articles

Set up and manage single sign-on (SSO) with Mitti