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

# How factors work

> A factor is a method of proving identity. What each factor proves, what it needs from your directory, how strong it is, and when it is offered.

This page is for administrators choosing which proof methods to accept. When you finish you will know what each factor proves, what it needs, how strong it is, and why every flow needs a fallback.

## Factors at a glance

Open **Factors** in the console to see every factor, whether it is active, and what it needs. Select a factor to open its settings.

![Factors page with cards for SMS, Email, Knowledge, Badge, Face and Proofing, each marked Active](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/console-factors-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=19f1df1860e2f8d77d8ae8cb7c9b8899)

| Factor | What it proves | What it needs | Strength |
| - | - | - | - |
| [Face](https://docs.truu.ai/idv/factors/face.md) | The live person matches a reference photo, with a liveness check | A camera, and a reference photo: the photo kept from a passed proofing check, your directory photo, or photos in your own storage | Strong |
| [Proofing](https://docs.truu.ai/idv/factors/proofing/overview.md) | A government ID is genuine and the live selfie matches it | A camera and a proofing vendor. No directory data | Strong |
| [SMS](https://docs.truu.ai/idv/factors/sms.md) | Possession of the phone on file | A mobile number in E.164 format in your directory | Moderate |
| [Email](https://docs.truu.ai/idv/factors/email.md) | Access to the mailbox on file | An email address in your directory | Moderate |
| [Badge](https://docs.truu.ai/idv/factors/badge.md) | Possession of the physical badge or smart card | A badge reader on the device and a badge identifier in your directory | Moderate |
| [Knowledge](https://docs.truu.ai/idv/factors/knowledge.md) | Knowledge of facts from the employee's directory record | Directory attributes that are populated for most employees | Weak |

## Strength

Each factor's strength feeds the assurance shown on every column in the flow builder.

* **Strong:** Face and Proofing bind the verification to a physical person, not an account.
* **Moderate:** SMS, Email and Badge prove control of something the employee holds. Treat Badge as weaker where badge numbers are printed on the card or widely known.
* **Weak:** Knowledge. Directory facts are what a social engineer collects before calling the help desk.

A column that combines different kinds of evidence (something the employee is, plus something they have) rates higher than one that stacks the same kind.

> [!WARNING]
>
> Never build a column where Knowledge or Badge is the only factor. Pair it with a one-time code at minimum, and keep Face or Proofing first for people who can use them.

## When a factor is offered

A factor is only offered when the employee can complete it on the device in front of them:

| Factor | Not offered when |
| - | - |
| Face | No camera, or no reference photo from any source |
| Proofing | No camera |
| SMS | No mobile number on file, or it isn't in E.164 format |
| Email | No email address on file |
| Knowledge | The challenge attributes are empty for this employee |
| Badge | No badge identifier on file, or no reader on the device |

The verification page checks this before offering a column, so employees never see a step they can't finish. That is why every flow needs a fallback column. The employee can also choose **Try another way** to move to the next column.

> [!TIP]
>
> Phones work; laptop webcams often don't. Face and Proofing can be set to **Phone camera only**, which shows desktop users a QR code to finish on their phone.

## Settings every factor shares

* **Active:** inactive factors can't be added to flows and aren't offered in flows that already use them. Before turning one off, check the flows that use it.
* **Attempts per run:** how many tries an employee gets at this factor in one verification before it fails and the flow moves on.
* **Attribute lists:** factors that read your directory (SMS, Email, Knowledge, Badge) take an ordered list of attributes. TruU tries them in order and uses the first one that has a value for each employee.

## Not factors: actions after verification

Issuing a Windows Temporary Access Pass or resetting PingOne MFA devices happen after a successful verification. They are set on each use case, not in flows. See [How use cases work](https://docs.truu.ai/idv/use-cases/overview.md#outcome-what-happens-after).

## Related

* [Flows and templates](https://docs.truu.ai/idv/build/flows.md)
* [Connect your directory](https://docs.truu.ai/idv/connect/directory/overview.md): attribute mapping and coverage


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