admin guide
SSO setup (SAML & OIDC)
Connect Okta, Entra ID, Google Workspace, Auth0, Ping, JumpCloud, or any generic SAML/OIDC IdP.
12 min read · 4 sections
Prerequisites
- Your plan includes SSO (Business and Enterprise tiers by default).
- You are tenant-owner or tenant-admin.
- You have IdP admin access. For SAML you need metadata XML or the IdP-issued URL.
SAML (generic)
- Open /settings/sso and click "Add SAML provider".
- Copy the ACS URL and Entity ID into your IdP application config.
- Upload your IdP metadata XML, or paste the metadata URL.
- Map SAML attributes: NameID → email; FirstName, LastName, and optionally Groups.
- Enable JIT (just-in-time) provisioning if you want users auto-created on first SSO login.
- Click Test — sign in as yourself through the IdP. Successful login switches the provider status to Verified.
- Toggle "Require SSO for all users" once you have verified at least one production user can log in.
OIDC (Okta, Entra ID, Google, Auth0)
- Open /settings/sso and click "Add OIDC provider".
- Copy the redirect URI into your IdP.
- Paste your IdP issuer URL, client ID, and client secret.
- Scope claim mapping defaults: sub → id, email → email, name → display name, groups → group-to-role map.
- Test the connection. If it reports "groups claim missing", check your IdP includes groups in the ID token.
Group-to-role mapping
SSO groups can auto-assign roles. Add a rule like "acme-qehs-admins → tenant-admin" and every SSO login whose groups claim contains that ID is granted the role. Rules compose — a user in three matching groups gets the highest role.