> ## Documentation Index
> Fetch the complete documentation index at: https://docs.truu.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Sign-in, SSO and passkeys

> How your team signs in to TruU IDV: email codes, Google and Microsoft, passkeys, and enterprise SSO through Microsoft Entra ID, Google, Okta, PingFederate, PingOne or any OIDC provider. Recovery, just-in-time provisioning and multiple workspaces.

This page is for the Owner or Admin deciding how the team signs in to the console and the help desk app. When you finish you will know which sign-in methods to allow, how to set up enterprise SSO safely, and how people work across more than one workspace.

## Sign-in methods

Open **Settings → Security**.

![Security settings with Sign-in methods (Email one-time code and Social login), Enterprise SSO, Just-in-time provisioning and Default roles](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/settings-security-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=abf75cc96f2ae1d7c2e1f1a36cf4dd41)

| Method | How it works | Good for |
| - | - | - |
| **Email one-time code** | A six-digit code sent to the member's email, valid for 10 minutes | On from the start |
| **Social login** | **Continue with Google** or **Continue with Microsoft**, when the account's email matches a member | Small teams without an identity provider |
| **Passkeys** | **Sign in with a passkey** using a fingerprint, face, device PIN or security key | Everyone while SSO is off; only Owners once SSO is on |
| **Enterprise SSO** | Sign in through your identity provider over OpenID Connect | Organizations with an identity provider. Required for just-in-time provisioning. |

Sign-in attempts, successful and failed, are audited, and repeated failures cause a temporary lockout.

## Passkeys

Each person manages their own passkeys under **Settings → Profile → Passkeys → Add passkey**, up to 10 per person. Once added, choose **Sign in with a passkey** on the sign-in page. While enterprise SSO is on, only Owners can sign in with a passkey. Passkeys are phishing-resistant and work with Touch ID, Windows Hello, Android and iOS devices, and hardware security keys such as YubiKey.

![The sign-in page with a work email field, Continue with Email and Sign in with a passkey](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/onboarding-01-sign-in-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=32588bf83bc68417e00f53c255162c16)

## Enterprise SSO

**1. Make sure an Owner has a passkey**

Once SSO is on, it becomes the only way to sign in, apart from Owners' passkeys. If your identity provider has an outage or someone changes the app, an Owner with a passkey can still get in. If no Owner has one, turning SSO on shows a warning, "Enable SSO with no way back in?", with **Add a passkey first** or **Enable anyway**. Enroll passkeys for at least two Owners before you continue.

**2. Register an OIDC app with your identity provider**

Create a web application (OIDC) in your identity provider. Add the **Redirect URI** shown in TruU as an allowed callback, and grant the **Scopes** TruU lists for your provider (`openid`, `profile` and `email`, plus `offline_access` for Microsoft and Okta). Assign the people who should be able to sign in.

**3. Set it up in TruU**

Under **Enterprise SSO**, choose **Set up**, pick the **Provider**, and enter:

| Provider | Identifier field | Plus |
| - | - | - |
| **Microsoft** (Entra ID) | Directory (tenant) ID | Client ID, Client secret |
| **Google** | Workspace domain, for example `contoso.com` | Client ID, Client secret |
| **Okta** | Okta org URL | Client ID, Client secret |
| **PingFederate** | PingFederate base URL | Client ID, Client secret |
| **PingOne** | PingOne issuer | Client ID, Client secret |
| **Generic** (any OIDC provider) | Issuer URL | Client ID, Client secret |

The client secret is stored in a managed secrets service and never shown again.

**4. Test, then rely on it**

Sign in through SSO in a private browser window before closing your current session. While SSO is on, **Email one-time code** and **Social login** are switched off; to change them, remove SSO first.

### SSO recovery

An identity provider change (a renamed app, a rotated secret, a changed issuer) can break SSO for everyone at once. The **SSO recovery** card under Security lists each Owner as having a passkey or not. "No owner has a passkey. If single sign-on fails, no one can sign in." means you should fix that today. If you're locked out anyway, contact [support](https://docs.truu.ai/idv/resources/support.md).

## Just-in-time provisioning

With enterprise SSO on, turn on **Just-in-time provisioning** to create members automatically the first time they sign in through SSO. They receive the **Default roles** you set, which can only be **Agent**. This lets a help desk team sign in without individual invitations. Admin and Owner are never granted automatically; promote people under [Team](https://docs.truu.ai/idv/admin/team-and-roles.md).

JIT also needs a verified email domain, read from a connected **Microsoft Entra ID** directory (with `Organization.Read.All` consented), so that only people from your organization are provisioned. With an Okta directory, JIT isn't available.

## Workspaces

One account can belong to several workspaces, for example a production workspace and a test one, or separate subsidiaries each with their own directory.

* **Switch workspace** and **New workspace** are in the account menu at the bottom of the sidebar.
* **Find your workspaces** on the sign-in page sends a code to your email, then lists every workspace you belong to.
* Each workspace has a **short code** (Settings → General) that identifies it at sign-in. The link icon next to the workspace name copies a sign-in link that opens straight into this workspace, useful for teammates.
* One email address can create up to five workspaces.

## Troubleshooting

| Symptom | Cause | Fix |
| - | - | - |
| A new member can't sign in | Their invited email differs from the email their identity provider or Google account presents | Re-invite with the exact address |
| SSO works for some people only | The identity provider's app assignment doesn't include them | Assign them to the OIDC app |
| Everyone arrived as Agent | JIT only grants Agent | Promote people under Team |
| "Remove SSO to change sign-in methods" | Email and social sign-in are locked while SSO is on | Remove SSO first, or keep it and use passkeys as the fallback |

## Related

* [Team and roles](https://docs.truu.ai/idv/admin/team-and-roles.md)
* [Connect your directory](https://docs.truu.ai/idv/connect/directory/overview.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.