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

# Go live

> Move from sample mode to real employees: connect your directory, work through the Get started checklist, resolve the setup review, and roll out to a pilot group.

This page is for the administrator taking a workspace from sample mode to real employees. When you finish, every factor, flow and use case has been checked against your real directory, your team is invited, and a pilot group can verify.

## Before you start

* A workspace you have explored in sample mode. See [Quickstart](https://docs.truu.ai/idv/getting-started/quickstart.md).
* Rights to connect your directory: an Entra ID administrator who can grant admin consent, or an Okta administrator who can create an API Services app. See [Connect your directory](https://docs.truu.ai/idv/connect/directory/overview.md).
* A pilot group in your directory, ideally 10 to 50 people who know they are piloting.

## What changes when you connect a directory

Connecting a directory is the switch from sample mode to live mode.

* Sample employees are replaced by lookups against your directory.
* Factors, flows and use cases you built are kept.
* Each factor's availability is recalculated from real attribute coverage. A factor that worked for every sample employee may only work for some real ones; for example, SMS needs a mobile number in E.164 format and Knowledge needs the attributes its questions use.
* Use case rules that named sample groups need real groups.

## The Get started checklist

The **Get started** card at the bottom of the console sidebar tracks setup. Before a directory is connected it shows learning tasks; after, it shows the go-live tasks.

| Before a directory is connected | After a directory is connected |
| - | - |
| Explore your flow | Fix your factors |
| Set up a factor | Check your flows |
| Connect directory | Set who gets what |
| | Invite your team |

**Set up recovery** is added for Owners when the workspace uses enterprise SSO and no break-glass passkey is registered, so an Owner can still get in if the identity provider is down. See [Sign-in, SSO and passkeys](https://docs.truu.ai/idv/admin/sign-in.md).

## Review your setup

**Fix your factors**, **Check your flows** and **Set who gets what** open the **Review your setup** dialog. It checks your factors, flows and use cases against the connected directory and lists anything that would stop a verification or limit who can use it.

Each item has a status:

| Status | Meaning |
| - | - |
| OK | Works for everyone it applies to. |
| Limited coverage | Works, but only for some employees, usually because a directory attribute is missing for others. |
| Needs setup | Not configured yet, for example a factor with no data source. |
| Needs a decision | A use case rule points at a directory group that no longer exists. There is no automatic fix; choose a new group or remove the rule. |
| Broken | Will fail when used. |

For each item you can:

* **Apply fix**: for factors, set the directory attribute the review recommends.
* **Accept as-is**: go live with it as it is, even for a blocker. The item shows as accepted, and **Undo** brings it back.
* **Open in Factors**, **Open in Flows** or **Open in Use cases**: go to the setting and change it yourself.

Choose **Finish later** to come back to it, or **Done** when everything is resolved or accepted.

## Roll out

**1. Route the pilot group**

In **Use Cases**, add a rule that sends your pilot group to the flow you want them to use for each use case they will hit. Leave **Everyone else** on a flow you are comfortable with. See [How use cases work](https://docs.truu.ai/idv/use-cases/overview.md).

**2. Verify yourself**

From the help desk app, send yourself a verification on a phone and complete it. Confirm it appears in **Activity**.

**3. Invite your team**

Invite admins and help desk agents from **Settings → Team**. See [Team and roles](https://docs.truu.ai/idv/admin/team-and-roles.md).

**4. Brief people**

Share [What to expect](https://docs.truu.ai/idv/end-users/what-to-expect.md) with the pilot group and the [Agent guide](https://docs.truu.ai/idv/help-desk/agent-guide.md) with agents.

**5. Confirm the basics**

Credential health is green (see [Credential health](https://docs.truu.ai/idv/admin/credential-health.md)), storage is the one you want (see [Storage](https://docs.truu.ai/idv/connect/storage.md)), and you know how you will export audit records (see [Activity and export](https://docs.truu.ai/idv/admin/activity.md)).

> [!TIP]
>
> You are live when the first real request from an agent succeeds for a pilot employee.

## After the pilot

Widen the use case rules to more groups as directory coverage allows, connect your own storage if you have not, and add the connectors you need: [ServiceNow](https://docs.truu.ai/idv/connect/servicenow.md), [Microsoft Teams](https://docs.truu.ai/idv/connect/microsoft-teams.md), [Windows TAP](https://docs.truu.ai/idv/connect/windows-tap.md) or [PingOne MFA](https://docs.truu.ai/idv/connect/pingone-mfa.md).


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