Updating SSO Provider

Updating Your Single Sign-On (SSO) Provider

If your team is migrating to a new identity provider (e.g., switching from Okta to OneLogin), we are here to help ensure the transition is seamless. Please follow the guide below to initiate the change.

Important: Transition Policy

Before we begin, please note our current authentication policies:

• Supported: Moving from Username/Password to SSO.
• Supported: Moving from one SSO provider to another (e.g., SSO1 to SSO2).
• Not Supported: Reverting from SSO back to Username/Password login.

How to Change Your Provider

To update your SSO configuration, please follow these three steps:

1. Identify Your New Provider

Reach out to our support team and let us know which SSO platform you are migrating to. Common providers include Okta, OneLogin, Microsoft Entra ID (Azure AD), and Google Workspace.

2. Configure Your Side

Once you’ve notified us of the new provider, we will send you a SAML Setup Guide specific to that platform. You will need to use the parameters in that guide to configure the application within your new SSO dashboard.

3. Submit Your Metadata

After the configuration is complete on your end, we need your new SAML Metadata. You can provide this in one of two ways:

• A publicly accessible Metadata URL.
• A downloaded Metadata XML file.

What Happens Next?

Once you send us the metadata, our support team will attach it to a technical request for our engineering team. They will swap the metadata on the backend to point to your new provider.

Note: We recommend scheduling this change during a window of low activity, as the switch to the new login flow happens immediately once the metadata is updated.