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

# Flows and templates

> A flow turns factors into verification paths with fallbacks. Columns, how a flow runs, column strength, retries, and the setup templates.

This page is for administrators building verification paths. When you finish you will know how columns and fallbacks work, how to read a column's strength, and which template to start from.

## What a flow is

A flow defines what someone must prove, in what order, and what happens when the preferred way isn't available. It's built from [factors](https://docs.truu.ai/idv/factors/overview.md), and [use cases](https://docs.truu.ai/idv/use-cases/overview.md) decide who gets which flow.

Because flows are configuration, different groups get different experiences from one engine: a strict flow for administrators, a phone-first flow for frontline staff, a lighter flow for a low-risk request.

![Flows page listing Standard Corporate Flow and Catch All Flow, with a Quick Start row of templates](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/console-flows-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=cd952d694bdd258830b612fde195edef)

The Flows page lists your flows and the setup templates you can start from.

## Columns are paths

A flow is a row of **columns**, labeled **Primary**, **Fallback 1**, **Fallback 2** and so on. Each column is a complete way to pass.

* **Primary runs first.** If a factor in it can't run for this person or device, the flow falls through to the next column.
* **Every factor in a column must pass** ("All factors required together"). Factors run in the order shown, so Knowledge then SMS means the person answers a question, then enters a texted code.
* **The flow passes when any one column passes.** The verification records which column completed and which factors ran.
* The person can choose **Try another way** to move to the next column themselves.

![Flow editor with Primary, Fallback 1 and Fallback 2 columns and a factor list on the left](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/onboarding-14-first-flow-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=e56626370587b9dc4fac52caa220eb6e)

Standard Corporate: Face first; Proofing if there's no photo; SMS and Knowledge together as the last resort.

To edit, open a flow, drag factors from the list into a column or use **Add Factor**, add a column with **Add Fallback**, then choose **Save flow**.

> [!WARNING]
>
> Always include at least one fallback column. A single-column flow blocks everyone whose device or directory data can't support its factors, and blocked people end up in the unaudited side channels verification is meant to replace.

## How a flow runs

1. A request is created for a person and a use case.
2. The use case's rules pick the flow for that person's directory groups.
3. Columns whose factors this person can't run are set aside: no camera, no phone number on file, no reference photo.
4. The first remaining column is offered. If the person fails a factor and has tries left, they retry; if the column can't be completed, the next one is offered.
5. The result, the column that completed, each factor's outcome, and which directory attribute served each factor are written to the [verification request](https://docs.truu.ai/idv/build/verification-requests.md) and the audit trail.

## Column strength

Each column shows a colored dot next to its label: **Strong** (green), **Fair** (amber) or **Weak** (red). Hover it to see why, including warnings and which combinations earned extra credit. It updates as you edit.

* **Factor strength anchors the column.** Face and Proofing rate highest; Badge, SMS and Email come next; Knowledge rates lowest.
* **Combining kinds of evidence adds more.** Knowledge plus a delivered code rates higher than either alone; two code factors add less.
* **Adding a weak factor to a strong column doesn't lower it;** removing the strong factor does.

Strength is relative, not certified against an external standard, and nothing enforces a minimum. Use it to compare:

* **Columns within a flow.** The gap between Primary and the last fallback is what someone gets when they can't use Primary. Decide deliberately whether that's acceptable; if not, strengthen the fallback rather than deleting it.
* **Flows across groups.** Higher-risk groups should get flows whose weakest column rates at least as high as everyone else's.

> [!TIP]
>
> Audit the weakest column, not the first. It's the path an attacker looks for. If a column you wouldn't accept for a password reset is reachable in the flow the Helpdesk use case assigns, fix it.

## Retries

Two limits work together:

* **Attempts per run**, set on each factor: how many times someone can try that factor before it fails. See each factor's page.
* **Verification runs per link**, under **Retry defaults** on the Flows page: how many full runs (from **Begin** until the verification ends without success) one link allows. Factor tries reset at the start of each run. With **Open a review case when runs are used up** on, a link that runs out of runs goes to manual review instead of simply failing.

## Templates

Start from a template under **Quick Start** on the Flows page, or from the first-run tour. Applying one turns on the factors it needs and creates the flow.

| Template | Primary | Fallback 1 | Fallback 2 | Good for |
| - | - | - | - | - |
| **Standard Corporate** | Face | Proofing | SMS + Knowledge | Office and remote employees with their own devices |
| **Shared Devices** | Face | Badge | | Frontline staff at shared workstations |
| **High Security** | Face + Knowledge | Proofing + Knowledge | Badge + Knowledge | Executives and administrators |
| **Passwordless Access** | Face | | | Employees who already have a reference photo. It has no fallback; add one before using it widely. |
| **Remote Workforce** | Proofing | Email + Badge | SMS + Badge | Contractors and temporary workers without a photo on file |

Every workspace also has a **Catch All Flow**, the starting flow for **Everyone** on the built-in use cases.

## Best practices

* **Lead with the strongest column your people can actually use.** Check photo and attribute coverage first.
* **Keep fallbacks meaningful.** A fallback that drops to a single weak factor undermines the flow. Pair Knowledge with a delivered code at minimum.
* **Cover how your people really verify:** on phones, at shared machines without cameras, and new hires with nothing on file.
* **Test as an employee,** including the fallbacks, by sending yourself a verification from the help desk app.

## Related

* [How factors work](https://docs.truu.ai/idv/factors/overview.md)
* [How use cases work](https://docs.truu.ai/idv/use-cases/overview.md)
* [Verification requests and links](https://docs.truu.ai/idv/build/verification-requests.md)


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