What has changed?
Contract Logix is migrating its identity platform to Auth0. Your existing SSO connection will not carry over - it needs to be re-created once through the new self-service setup flow. Tenant owners and IT team members were sent a series of email notifications regarding this change beginning in June. For your convenience, you can find below the overview and setup guide that were included in the notification.
Why this change?
Securing your account and the sensitive work stored in Contract Logix is a top priority. Auth0 is a dedicated, industry-leading identity platform that lets us apply stronger, continuously maintained security protections. Moving to it means better safeguards for your login and your data, now and in the future, with the same username and uninterrupted access to all your existing work.
What happens if your team does not make the change before the September 30 Deadline?
The Auth0 connection must be Active and users must be moved to the new connection by September 30, 2026. Any tenant without an Active connection after that date falls back to username and password sign-in until setup is completed. Access and data are unaffected — SSO simply stops routing to your IdP.
You may be prompted to authenticate via LegalSifter's Auth0 connection (shown below). This is expected.
What does this mean for your Contract Logix Administrator and IT Team?
One connection to re-create, roughly fifteen minutes of work. You'll need full access to Settings in Contract Logix plus administrator rights in your IdP.
Technical Overview
Auth0 Migration Checklist:
Create new SSO connection
Test new connection with a few users
Migrate the remaining users
The path:
1. Settings → App Settings → Authentication Type → select SSO Authentication.
2. Click “+” in the SSO Definitions & Policies table, enter a connection name, and click Save & get link.
3. Copy the one-time setup link. It's shown once and expires after 5 days — treat it as a credential. (Lost it? Edit the connection → Get setup link.)
4. Open the link and complete the secured setup assistant: choose your provider, create the Contract Logix app in your IdP using the URLs it gives you (sign-in URL, entity ID, reply/ACS URL), paste your IdP's metadata URL or certificate — or client ID and secret — and let it verify the connection.
5. Back in Contract Logix, refresh App Settings and wait for Status to read Active. The check runs automatically about every 5 minutes.
6. Test the connection with one user before moving everyone over. You'll need to move the user to the new connection on their user screen (application settings>users>select user>authentication). For instructions click HERE
Worth knowing before you start:
· Supported providers: Microsoft Entra ID, Okta, ADFS, Ping, or any SAML / OIDC provider.
· Two things to do in your IdP, or sign-in will fail later: assign the users or groups to the new application, and send email as the identifier, matching each user's Contract Logix email exactly. Users are matched by email address.
· No secrets in Contract Logix. Certificates, client secrets, and signing keys are entered only in the setup assistant. Nothing needs to be copied back.
· No lockout risk during setup. Your users continue signing in with their current authentication method — SSO or User & Password.
If something doesn't work
The attached guide has a status reference (pp. 12–13) and a troubleshooting table keyed to the exact on-screen message (pp. 14–15). The most common issues are an unassigned user in the IdP, an email attribute that doesn't match the Contract Logix account, and a status that simply hasn't been refreshed yet.
To contact our Support Team, create a ticket via the messenger or by sending us a message at [email protected]