Identity and people

Connect your company SSO

Set up company sign-in using your existing identity provider.

Deployment
BYOC

Use your existing identity provider so employees can sign in with their work identity. The organization onboarding path uses SAML 2.0, a standard supported by most company identity systems.

How a company SSO sign-in travelsThe employee enters a work email in the console. Diakrin sends a SAML request to your identity provider. The provider signs the employee in, applying MFA, and posts a signed SAML response to Diakrin's ACS URL. Diakrin checks for membership or an invitation before opening the console.Employee browserconsole sign-inDiakrin sign-inSAML service providerIdentity providerOkta, Entra, Google…1 · work email2 · SAML request3 · sign-in + MFA4 · signed response → ACS URL5 · membership check, then console
Your identity provider proves who the employee is. Diakrin then decides what they can access, based on membership or an invitation.

SSO setup at a glance

  1. Get your setup packetDiakrin onboarding contact

    Exact ACS URL, Entity ID and metadata for your environment.

  2. Create the SAML appIdentity administrator

    Follow your provider's guide, send a stable NameID and the work email, and assign pilot users only.

  3. Return the metadataIdentity administrator

    Send the identity provider's metadata, approved domains and certificate expiry to your onboarding contact.

  4. ActivateDiakrin onboarding contact

    The connection is activated for your domains and environment.

  5. Pilot, then roll outIdentity administrator

    Run the pilot checklist, then widen the provider assignment in stages.

Choose your provider

Identity providerConfiguration guide
OktaCreate a SAML app integration
Auth0Use the SAML2 Web App add-on
Microsoft Entra ID / Azure ADCreate a SAML enterprise application
Google WorkspaceCreate a custom SAML app
OneLoginUse the advanced SAML connector
PingOneConfigure a SAML application
KeycloakCreate a SAML client
Another provider, including AD FS or PingFederateUse the common SAML checklist

These are configuration paths for compatible providers. Each connection still requires activation and testing. If your company requires a direct OIDC connection, discuss it with your onboarding contact; generic organization OIDC setup is not available through this flow. Auth0 uses SAML here even if your other applications use Auth0 OIDC.

Get your setup packet

Ask your Diakrin onboarding contact for the values for the correct environment. Supply your organization name, owner, identity provider, IT contact and work-email domains.

Value from DiakrinWhere you use it
ACS / Reply URLWhere the identity provider sends the signed SAML response
Audience / SP Entity IDIdentifies Diakrin’s authentication service
SP Metadata URL or XMLImports the service-provider configuration, where supported
Console sign-in URLWhere employees start sign-in
Approved work-email domainsRoutes company sign-in to the activated connection

Use the worksheet below to prepare copyable values from the authentication URL supplied by Diakrin. Do not substitute the console home page for the ACS URL. Treat staging and production as separate setups.

Configure and return the metadata

  1. Follow your provider guide and use the setup packet’s exact values.
  2. Send a stable NameID in emailAddress or persistent format, plus the employee’s work email as an email attribute. Keep identifiers stable across later sign-ins.
  3. Assign only the pilot users or a pilot group. Apply your company’s MFA policy in the identity provider.
  4. Return the identity provider’s metadata URL or XML, approved domains, email-attribute name and certificate expiry to your Diakrin onboarding contact through your agreed onboarding channel.
  5. Wait for activation confirmation, then follow Test and roll out SSO.

Metadata includes public configuration and a public signing certificate. Never share private signing keys, user passwords, client secrets, session tokens or raw login assertions.

Sign in and join your team

Open the console, choose Sign in with company SSO, enter your work email and select Continue with SSO. Complete your provider’s sign-in and return to Diakrin. Your verified email must already have tenant membership, an active administrator assignment or an authorized invitation. Active email assignments and invitations attach automatically after verification.

Your email domain discovers a login connection; it does not grant access to an organization. Provider groups do not automatically become Diakrin roles. To add and remove members automatically, set up SCIM provisioning. Enforcing SSO for every console sign-in is not available in this setup; apps can require it, as described below.

Existing accounts and recovery

A previous password or social-login account and an SSO account can be separate identities, even with the same email. Before migrating an owner, follow the account migration checks. Keep an agreed recovery owner available until the pilot succeeds.

Ask your onboarding contact to confirm SSO availability and any applicable commercial terms before rollout. Employees do not need access to the underlying authentication service’s administration console.

Signing in to apps

Once SSO works for the console, employees use the same sign-in for deployed company apps. Diakrin brokers the sign-in, so you do not register each app with your identity provider. To require company SSO for every app, set Allowed methods to company SSO under Settings → Organization administration → Sign-in. See Sign in to company apps.

Next stepTest and roll out SSO →