What is TruU IDV?
TruU IDV is a workforce identity verification platform. It connects to your employee directory (Microsoft Entra ID or Okta) and answers one question at the moments that matter: is the person we are dealing with right now the employee we think they are? It is not consumer KYC and it is not a one-shot document-and-selfie API. It is an orchestration layer. You choose the proof methods your organization accepts, arrange them into verification paths with fallbacks, and decide which path each group of employees gets for each situation. A help desk agent, a self-service request, an enrollment, a connector or an API call then starts a verification, the employee completes it on their own device, and TruU records the outcome.Start by role
IT and identity admins
Create a workspace, connect your directory, and set up your use cases.
Security reviewers
What runs where, what is stored, audit events, and the threat model.
Developers
Create an API client and send your first verification link with curl.
HR and onboarding
Verify new hires before they get credentials, and what employees experience.
Help desk leads
Replace challenge questions with verification agents can trust.
Employees
What a verification looks like on your phone and what happens to your data.
How it works
The console’s first-run tour teaches the model in three steps, and the rest of these docs use the same words.1
It starts with factors
A factor is a method of proving identity: a face match, document proofing, an SMS or email one-time code, knowledge questions drawn from directory attributes, or a badge tap. You choose which ones your organization can use. See How factors work.
2
Flows build verification paths
A flow turns factors into a sequence with fallbacks. Column A runs first; if a factor there can’t run on the employee’s device, the flow falls through to column B, then C. Every factor in a column must pass. See Flows and templates.
3
Use cases tie it together
A use case is a situation such as onboarding, a credential reset or a help desk call. For each one you pick a flow per directory group, the wording the employee sees, and what happens after success, like issuing a Temporary Access Pass or resetting MFA. See How use cases work.
Where verification starts
What makes TruU IDV different
- Directory-first. TruU reads your directory with read-only access you grant. The console shows which attributes are populated, so you see which factors your data can support before anyone is asked to use them.
- Fallbacks are part of the design. Every flow carries its fallback columns, and the builder shows how strong each path is, because the weakest reachable path is the one an attacker looks for.
- Phone-first for the employee. Verification links open on the employee’s own phone, where cameras work and the help desk agent cannot see the answers.
- One audit record. Help desk, self-service, onboarding, enrollment and API verifications all land in the same workspace-scoped audit trail.
- An orchestration layer, not another MFA vendor. TruU coordinates proof; it does not replace your authentication stack.
Your data
TruU stores verification outcomes and the evidence your factors need, and you can keep proofing captures and face references in your own Amazon S3 or Azure Blob storage. See Data handling.Explore the documentation
Quickstart
Create a workspace, take the tour, and open your first flow.
How use cases work
Who gets which flow, for which situation, and what happens after.
How factors work
Every proof method, what it needs from your directory, and how strong it is.
How integrations fit together
Directory, storage and the connectors that start or finish a verification.

