# Connect your company SSO

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

Source: https://diakrin.com/docs/sso

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.

```diagram sso-sequence
Your identity provider proves who the employee is. Diakrin then decides what they can access, based on membership or an invitation.
```

> [!SELF-HOSTED]
> Self-hosted installations do not use this SAML flow. People sign in with local accounts, and an administrator can add one company OIDC connection in the installation's configuration. Each OIDC subject must be assigned to an account; a matching email never links accounts on its own. Employees then choose **Company SSO** on the sign-in page.

## SSO setup at a glance

```steps
Get your setup packet | Diakrin onboarding contact | Exact ACS URL, Entity ID and metadata for your environment.
Create the SAML app | Identity administrator | Follow your provider's guide, send a stable NameID and the work email, and assign pilot users only.
Return the metadata | Identity administrator | Send the identity provider's metadata, approved domains and certificate expiry to your onboarding contact.
Activate | Diakrin onboarding contact | The connection is activated for your domains and environment.
Pilot, then roll out | Identity administrator | Run the [pilot checklist](/docs/sso/testing), then widen the provider assignment in stages.
```

> SSO setup is admin-assisted. Your IT administrator configures the identity provider; your Diakrin onboarding contact activates the connection. A guide or completed identity-provider application does not establish an active or tested Diakrin integration.

## Choose your provider

| Identity provider | Configuration guide |
| --- | --- |
| Okta | [Create a SAML app integration](/docs/sso/okta) |
| Auth0 | [Use the SAML2 Web App add-on](/docs/sso/auth0) |
| Microsoft Entra ID / Azure AD | [Create a SAML enterprise application](/docs/sso/microsoft-entra) |
| Google Workspace | [Create a custom SAML app](/docs/sso/google-workspace) |
| OneLogin | [Use the advanced SAML connector](/docs/sso/onelogin) |
| PingOne | [Configure a SAML application](/docs/sso/pingone) |
| Keycloak | [Create a SAML client](/docs/sso/keycloak) |
| Another provider, including AD FS or PingFederate | [Use the common SAML checklist](/docs/sso/generic-saml) |

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 Diakrin | Where you use it |
| --- | --- |
| ACS / Reply URL | Where the identity provider sends the signed SAML response |
| Audience / SP Entity ID | Identifies Diakrin’s authentication service |
| SP Metadata URL or XML | Imports the service-provider configuration, where supported |
| Console sign-in URL | Where employees start sign-in |
| Approved work-email domains | Routes 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](/docs/sso/testing).

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](/docs/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](/docs/sso/testing#existing-account-migration). 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](/docs/app-signin).
