Set up workspace single sign-on (SSO)
Connect your company's login system like Okta, Auth0, or Microsoft Entra ID to control how team members access your Lovable workspace. You verify your domain, link Lovable with your provider using OIDC or SAML, and optionally require everyone to log in through it.
Workspace owners or admins on Business or Enterprise plans setting up secure, centralized team logins.
Do this, in order
- 1
Verify your organization's domain in Lovable workspace settings under Access and Identity.
The Add provider button stays disabled until your domain is verified with a DNS TXT record.
- 2
Click Add provider under SSO providers and choose either Configure OIDC or Configure SAML.
This starts the connection wizard between Lovable and your identity system.
- 3
In your identity provider (Okta, Auth0, or Entra ID), add the Lovable application and paste the Lovable redirect/ACS URL (https://auth.lovable.dev/__/auth/handler).
Your identity provider needs to know where to securely return users after they log in.
- 4
Copy your identity provider's details (such as Issuer URL, Client ID, Client Secret, or SAML metadata) and paste them into Lovable.
Lovable needs these credentials and endpoints to authenticate your users against your identity provider.
- 5
Fill in the Display Name, select your verified domain, and optionally add a Login URL suffix.
This generates your team's direct login link (for example, lovable.dev/sso-login/acme-com).
- 6
Click Test configuration (for OIDC) or Test & import (for SAML), review the confirmation screen, and click Confirm & enable SSO.
Verifying credentials before activating prevents team members from being locked out due to configuration errors.
- 7
Wait at least 6 hours, test an SSO login, and toggle Enforce SSO if you want to require all members to use it.
Lovable enforces a 6-hour safety cooldown before mandatory enforcement to ensure logins work properly.
Words decoded
- SSO (Single Sign-On)
- A setup that lets team members log into Lovable using their company work account instead of a separate password.
- IdP (Identity Provider)
- The central service your company uses to manage accounts and passwords, like Okta, Microsoft Entra, or Auth0.
- OIDC / SAML
- Standard industry formats that allow your identity provider and Lovable to securely talk to each other.
- ACS URL / Redirect URI
- The web address Lovable gives you so your login provider knows where to send users after they sign in.
Where people get stuck
- Do not confuse workspace SSO (for team members editing apps in Lovable) with app SAML SSO (for end users logging into the apps you build).
- You cannot turn on Enforce SSO until at least 6 hours after adding your provider, and you cannot enable it if 'Require two-factor authentication' is set to 'Everyone'.
- In Microsoft Entra ID OIDC setup, you must manually add the optional 'email' claim to the ID token, or login will fail.
- If your workspace shares a verified domain with another workspace, you must provide a unique Login URL suffix.
The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.