Use OpenID Connect in Slite to allow users to securely sign in with Azure Active Directory identities. When you activate it, SSO becomes the default way your team members sign in to Slite. Workspace owners and admins who have already joined can still use email and password as a backup (for example, if an identity provider secret expires). Guests can join with email and password.
How to Set Up Azure Active Directory SSO
Step one: Get a Tenant ID from Azure Active Directory
You should find your Tenant ID in the Overview tab:
Step two: Get a Client ID from Azure Active Directory
In your Active Directory, click
Add and choose App registration.
Choose a name for this app, for example
Slite.In
Select a Platform, select Web.In the Redirect URL, enter:
https://slite.com/api/auth/openid/callback Click
Register, then you should now find your app under Applications > App registrations .
Click your registered app to see your Client ID.
Step three: Get a Client Secret from Azure Active Directory
In your new app registration, click
Certificates & secrets.Click
+ New client secret.
Add a description, e.g. the name of your Slite workspace.
Add an expiration date. The default expiration is 180 days. This is shorter than most SSO providers, and we recommend a higher value. If the secret expires, workspace admins and owners can sign in using an email and password fallback to update the client secret or disable SSO. ** 👉 * Watch the video below to learn how to set a date that doesn’t expire.*
Copy the 
Not its Secret ID.)
Value of your new client secret. ( Not its Secret ID.)You need to copy this now, and make a note of it, because Azure makes this value unavailable immediately after creation.If you do not copy this value now, you will need to create a new client secret.
Step four: Configure your OpenID authentication in Slite
Click your workspace logo in the top-left corner.
Select Settings from the menu, then go to the
Security section.Next to
SSO authentication enforcement, click Expand.Next to
OpenID authentication, click Configure. You should now see this form:
- In
Provider name, enter the name you wish to display on your Slite login page. (This is not used as part of the technical auth process.) - In
Provider URL, enterhttps://login.microsoftonline.com/TENANT-ID/v2.0, replacingTENANT-IDwith the Tenant ID that you noted earlier. - Under
Client ID, enter the Client ID that you noted down earlier. - Under
Client secret,enter the Client secret that you noted down earlier. - Click
Validate and save. It should redirect you to Azure Active Directory's authentication portal.
Identify yourself, click
Consent on behalf of your organisation then click Accept. You should be redirected to Slite.The SSO configuration process is over. Make sure that your SSO login works.
Optional: Launch Slite from My Apps
If your team opens apps from Microsoft My Apps or the Microsoft 365 app launcher, you can add a Slite tile there.
In Entra, go to App registrations, open your Slite app, and select Branding & properties.
In Home page URL, enter your workspace address, for example
https://your-workspace.slite.com, then click Save.Go to Enterprise applications, open your Slite app, and select Properties. Make sure Visible to users? is set to Yes.
If Assignment required? is set to Yes, assign the users or groups who need access under Users and groups.
Because Slite uses OpenID Connect, the My Apps tile doesn't sign users in directly. It opens your Slite workspace. Users who aren't signed in yet will see your Slite sign-in page and can continue with your identity provider from there. If the tile doesn't open Slite and you see no sign-in attempts in Entra's sign-in logs, check that the Home page URL is set correctly.