Skip to content

Documentation

Single sign-on & provisioning

Let people sign in with your company's identity provider over OIDC or SAML 2.0. Keep the user list current with SCIM provisioning or Microsoft Entra ID directory sync.

Where
Admin → Settings → Organization settings → Authentication · Admin → Settings → Directory sync · Admin → Roles
Permission
Full administrator (sign-in settings) · MANAGE_SETTINGS (SCIM tokens, directory sync)
Updated
October 2026

Before you start

Single sign-on (SSO) lets people sign in with the work account they already have, through your identity provider (IdP).

Connect one IdP per workspace, over OpenID Connect (OIDC) or SAML 2.0. Microsoft Entra ID, Okta, Google Workspace and any standards-based provider work.

Only full administrators can change sign-in settings, even when MANAGE_SETTINGS is given to another role.

SSO only covers email domains you have verified with a DNS TXT record. Add every domain your people sign in with, such as a second brand domain.

A verified domain stays trusted for 90 days after its last successful check. Verify it again from the same page to extend it.

Authentication mode has three settings: Password only turns SSO off, SSO optional shows both sign-in methods, and SSO required sends everyone to the IdP.

SSO required only applies while the connection is active. If SSO is off or not set up, passwords keep working, so a broken connection never locks the workspace out.

The settings page refuses to require SSO unless your own email domain is covered by it.

Just-in-time (JIT) provisioning creates an account, as an Employee or an Agent, the first time someone from a verified domain signs in through SSO.

JIT never creates administrators; invite or promote them by hand. With JIT off, only people who already have an account can sign in through SSO.

With SCIM 2.0 (automatic user provisioning), your IdP creates, updates and deactivates users and pushes group membership.

Directory sync is the alternative for Microsoft Entra ID: EvenTier pulls users from your tenant on a schedule.

Step by step

  1. 01

    Verify your email domain

    Prove you own each email domain by adding a DNS record. Start in Admin → Settings → Organization settings → Authentication.

    • Enter the email domain, for example acme.com
    • Publish the TXT record below at your DNS provider, then choose Verify
    • Repeat under Additional verified domains for every other domain your staff use
    • A domain can belong to only one workspace
    1. Type: TXT
    2. Host: _eventier-login.<domain>
    3. Value: the value shown on the page
  2. 02

    Connect an OIDC provider

    Choose Provider type OIDC. Register EvenTier as a web application in your IdP, then paste the provider's details back into EvenTier.

    • The Authorization, Token and User info URLs are in the provider's discovery document: <issuer>/.well-known/openid-configuration
    • EvenTier asks for the openid, profile and email scopes and uses PKCE
    • The client secret is sent in the token request body (client_secret_post)
    • The ID token's signature is checked against the provider's published keys
    • The client secret is encrypted at rest and never shown again
    1. In your identity provider, register a web application with:
    2. Redirect URI https://<your host>/api/org-auth/oidc/callback
    3. Paste into EvenTier:
    4. Issuer URL
    5. Client ID
    6. Client secret
    7. Authorization URL
    8. Token URL
    9. User info URL
  3. 03

    Or connect a SAML 2.0 provider

    Choose Provider type SAML 2.0. Give your IdP EvenTier's details, then paste the IdP's details back into EvenTier.

    • Set your IdP to sign both the SAML response and the assertion
    • Entra ID: choose Sign SAML response and assertion
    • Google Workspace: choose Signed response
    • The user's email is read from an email or mail attribute, the Entra ID emailaddress claim, or an email-format NameID
    1. Give your identity provider:
    2. SP entity ID shown on the page
    3. ACS URL shown on the page
    4. or the metadata URL https://<your host>/api/org-auth/saml/<workspace slug>/metadata
    5. Paste into EvenTier:
    6. IdP SSO URL
    7. IdP entity ID
    8. X.509 signing certificate
  4. 04

    Turn it on and test it

    Switch the connection on and save, then choose Test SSO. It signs you in through the provider and comes back with a confirmation.

    • Tick OIDC configuration is active (or the SAML equivalent)
    • Choose whether to create users automatically, and with which role
    • Failed attempts are logged under Admin → Audit logs → Changes as auth.sso.login_failed or auth.saml.login_failed, with the reason
    • Each failure records the reason, such as an unverified domain or an unsigned response
  5. 05

    Require SSO

    Once the test passes, set Authentication mode to SSO required and save.

    • People on a verified domain are sent to the IdP from the sign-in page
    • Password sign-in, password resets and new passwords stop for them
    • If you later switch the connection off, password sign-in comes back automatically so admins can still get in
  6. 06

    Provision users with SCIM

    Let your IdP add, update and remove people for you. Create a token in the SCIM provisioning section of the same page, then enter it in your IdP.

    • Turn SCIM on, choose an expiry (or Never expires) and choose Generate
    • Copy the token now; it is shown once
    • Unassigning or deactivating someone in the IdP deactivates them in EvenTier, which ends their access
    1. SCIM base URL: https://<your host>/api/scim/v2/<workspace slug>
    2. Microsoft Entra ID
    3. 1. Create a non-gallery enterprise application
    4. 2. Open Provisioning and set the mode to Automatic
    5. 3. Tenant URL: the SCIM base URL
    6. 4. Secret Token: the token
    7. Okta
    8. 1. Enable SCIM provisioning on the app
    9. 2. SCIM connector base URL: the SCIM base URL
    10. 3. Unique identifier: userName
    11. 4. Authentication: HTTP Header, with the token
  7. 07

    Map groups to teams and roles

    Name the groups your IdP pushes so EvenTier knows which team or role each one stands for.

    • A role is assigned by name only when Directory sync can assign this role is ticked on it in Admin → Roles
    • The built-in Admin role is never assigned by name
    • Groups that match nothing appear under SCIM group mapping, where you pick the team or role for each one
    1. Team: Network Ops adds the group's members to the Network Ops team
    2. Role: Service Desk assigns the Service Desk role
  8. 08

    Or sync from Microsoft Entra ID

    Have EvenTier pull users from Entra ID on a schedule instead. Set it up in Admin → Settings → Directory sync.

    • Preview changes shows who would be created, updated or deactivated, without changing anything
    • Queue sync runs it
    • A run never deactivates more than a quarter of the users it manages (at least one)
    • Existing accounts are linked by exact email only when you allow it for that run, and never for administrators
    1. In Entra ID, register an application with:
    2. Permission Microsoft Graph User.Read.All (application, admin consented)
    3. Client secret create one
    4. In EvenTier, enter:
    5. Directory (tenant) ID
    6. Application (client) ID
    7. Client secret
    8. Group object id optional: sync only that group's members
    9. Sync interval 15 minutes or more
    10. Default role Employee or Agent, for new users
    11. Removed people deactivate them, or leave them active

Endpoints to give your identity provider

Replace <your host> with your workspace address and <workspace slug> with the slug shown on the Authentication tab.

EndpointUsed for
/api/org-auth/oidc/callbackOIDC redirect URI
/api/org-auth/saml/<workspace slug>/acsSAML assertion consumer service (ACS) URL
/api/org-auth/saml/<workspace slug>/metadataSAML service provider metadata
/api/org-auth/saml/<workspace slug>/sloSAML single logout
/api/scim/v2/<workspace slug>SCIM 2.0 base URL (Users, Groups, ServiceProviderConfig)

Good to know

  • While you roll out SSO required, keep one full administrator who can sign in with a password and multi-factor authentication (MFA).
  • Test with a second browser before requiring SSO.
  • Neither SCIM nor directory sync deactivates the only person who can manage users and roles, or changes the sign-in email of someone with administrator access. Make those changes in Admin → Users.
  • Every SCIM and directory sync change is written to the audit log. The Admin actions filter in Admin → Audit logs shows them with other changes to people and roles.
  • Sign-ins through SSO are under Admin → Audit logs → Security events.