> ## 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.

# Quickstart

> Create a TruU IDV workspace, take the first-run tour, choose a template, and open your first flow. About 15 minutes, no directory required.

This page is for the first administrator in your organization. When you finish you will have a workspace in sample mode with active factors, a flow built from a template, and use cases routing to it. You can do all of it before connecting a real directory.

## Before you start

* A work email address. The first person to create a workspace becomes its **Owner**.
* About 15 minutes.
* Nothing else. Sample mode uses fictional employees, so you don't need directory access, an Azure subscription or a proofing contract yet.

## Create your workspace

**1. Sign up**

Go to the TruU IDV console and choose **Sign up**. Continue with Google or Microsoft, or enter your name and work email and choose **Continue with Email**.

![The Get started page with Google and Microsoft buttons, name fields and a work email field](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/onboarding-02-sign-up-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=854209a093ce2e61ac10fcae29d1e11d)

**2. Verify your email**

Enter the six-digit code sent to your address. Codes expire after 5 minutes; use **Resend** if it has expired.

**3. Name your workspace**

The name is prefilled from your email domain. Your workspace's short code, used in sign-in and self-service links, comes from the first 50 characters of the name.

![The Name your workspace page with the workspace name field and a Create workspace button](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/onboarding-04-name-workspace-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=25567a4889521fd56dc4e9bf8278711e)

## Take the tour

Choose **Enter your workspace**. A short tour explains the three things you configure: **factors** (methods of proving identity), **flows** (factors arranged into paths with fallbacks) and **use cases** (which flow each group gets, and what happens after). The [Introduction](https://docs.truu.ai/idv/introduction.md#how-it-works) covers the same model.

![Tour slide titled Use cases tie it together, showing a group, a flow and an MFA reset](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/onboarding-09-walkthrough-intro-3-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=e9dc725907e3c35edd583458c3c4559c)

The tour's last explainer: use cases pick a flow per user group and what happens after.

The tour then asks four setup questions. Every answer can be changed later.

**1. Connect your directory, or explore with samples**

Choose **Microsoft Entra ID**, **Okta**, or **Explore with samples**. Samples give you a fictional directory so you can see the whole product first; nothing you do in sample mode contacts a real person. To connect a real directory now, follow [Connect Microsoft Entra ID](https://docs.truu.ai/idv/connect/directory/entra-id.md) or [Connect Okta](https://docs.truu.ai/idv/connect/directory/okta.md).

![Connect your directory step with Microsoft Entra ID, Okta and Explore with samples options](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/onboarding-10-walkthrough-directory-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=25b57a5177cf885ab74cd0cef7b56032)

**2. Set up Proofing**

Pick the vendor that checks government IDs and selfies. **Didit** is recommended and needs no keys: TruU creates the vendor workspace when you continue. PingOne Verify, Persona and Entrust (Onfido) use your own vendor account. See [Identity proofing](https://docs.truu.ai/idv/factors/proofing/overview.md).

![Set up Proofing step with Didit recommended and PingOne Verify, Persona and Entrust listed under bring your own account](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/onboarding-11-walkthrough-proofing-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=d66ce0f152f62a9a50cd54439034263c)

**3. Choose where your data lives**

**TruU managed** storage is the default and needs no setup. Choose **Your own store** to keep proofing captures and face references in your Amazon S3 bucket or Azure Blob container; you can add one later in **Settings → Storage**. See [Storage](https://docs.truu.ai/idv/connect/storage.md).

![Where your data lives step with TruU managed selected as the default and Your own store as the alternative](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/onboarding-12-walkthrough-storage-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=1ca3cb5d94f4955fe04c5415910187aa)

**4. Start with a template**

Each option turns on sample factors and creates a flow for you to explore:

| Option | Template | Flow columns |
| - | - | - |
| Corporate employees | Standard Corporate | A: Face. B: Proofing. C: SMS + Knowledge |
| Frontline staff | Shared Devices | A: Face. B: Badge |
| High-security roles | High Security | A: Face + Knowledge. B: Proofing + Knowledge. C: Badge + Knowledge |
| External contractors | Remote Workforce | A: Proofing. B: Email + Badge. C: SMS + Badge |

Choose **Let's explore**.

![Start with a template step with Corporate employees, Frontline staff, High-security roles and External contractors](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/onboarding-13-walkthrough-template-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=61e996cbb292eed306c73a06a79c8db2)

## Review your first flow

The console opens the flow the template created. Column A is tried first; if a factor there can't run on the employee's device, the flow falls back to B, then C. Every factor in a column must pass.

![Flow editor showing Primary, Fallback 1 and Fallback 2 columns with Face, Proofing, SMS and Knowledge factors](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/onboarding-14-first-flow-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=e56626370587b9dc4fac52caa220eb6e)

The Standard Corporate flow: Face first, Proofing as the first fallback, SMS and Knowledge together as the last.

Then look around:

* **Factors** shows which proof methods are on and what each needs from the directory. See [How factors work](https://docs.truu.ai/idv/factors/overview.md).
* **Use Cases** shows which flow each situation uses. The template routes a sample group to its flow on the default Verification use case; everyone else, and the other built-in use cases, start on the Catch All Flow. See [How use cases work](https://docs.truu.ai/idv/use-cases/overview.md).
* **Get started**, at the bottom of the sidebar, tracks what is left to set up.

> [!NOTE]
>
> The flow builder, use cases and verification page behave the same in sample mode as in production. Only the data source differs, and everything you configure is kept when you connect a real directory.

## Try a verification

Try one from the help desk app: choose **New verification**, search for a sample employee, choose **Copy link** and **Send request**, then open the copied link on your phone. Sample employees aren't real people, so nothing is emailed or texted to anyone. The request moves from pending to verified as you go. See [Agent guide](https://docs.truu.ai/idv/help-desk/agent-guide.md).

## Next steps

> [card] [Connect your directory](https://docs.truu.ai/idv/connect/directory/overview.md)
>
> Replace sample employees with Entra ID or Okta.

> [card] [Set up your use cases](https://docs.truu.ai/idv/use-cases/overview.md)
>
> Decide which flow each group gets, and what happens after.

> [card] [Go live](https://docs.truu.ai/idv/getting-started/go-live.md)
>
> Review your setup against real directory data before rollout.

> [card] [Invite your team](https://docs.truu.ai/idv/admin/team-and-roles.md)
>
> Add admins and help desk agents.


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