> ## 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 use cases work

> A use case is a situation such as onboarding, a credential reset or a help desk call. It sets what the employee is told, which flow each directory group gets, and what happens after verification.

This page is for administrators deciding who verifies how. When you finish you will know what a use case controls, how its rules pick a flow, and how each verification is matched to a use case.

## What a use case controls

Open **Use Cases** in the console. Each use case sets three things:

| Part | What it is | Where |
| - | - | - |
| **Wording** | The name and message the employee sees in the email or text and on the verification page. | **About**: Name, Message |
| **Routing** | Which flow each directory group gets. Rules are checked top to bottom and the first match wins. | **Flow → Who** |
| **Outcome** | What happens after a successful verification. | **Flow → When it ends** |

![Credential reset side panel with Name, Message, a Who rule mapping Everyone to Catch All Flow, and a Passed outcome set to Report only](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/use-case-detail-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=cc655560da3c4df18abf50bf30446ca1)

The Credential reset use case: its wording, one routing rule, and what happens when the employee passes or fails.

## Built-in use cases

Every workspace has four. You can change their wording, routing and outcome, but not delete them.

| Use case | Used when | Default message | Link lifetime |
| - | - | - | - |
| **Onboarding** | A new hire activates their account or enrolls a device. | Confirm your identity to activate your account. | 7 days |
| **Credential reset** | An employee resets a password or MFA, including from the [self-service portal](https://docs.truu.ai/idv/use-cases/credential-reset.md#self-service-portal). | Confirm it's you before resetting your password or multi-factor authentication. | 1 hour |
| **Helpdesk** | A help desk agent verifies a caller. | A help desk agent requested verification for your account. Confirm it's you to continue. | 30 minutes |
| **Verification** | A request does not name a use case. Shown in the list as **If no use case is named**. | A verification request was made for your account. Confirm it's you to continue. | 30 minutes |

The link lifetime is shown under the message ("Link expires in 1 hour"). To restore a built-in's original wording, use **Reset to standard wording**.

## Custom use cases

Choose **Add Use Case** for a situation the built-ins don't cover, for example "Badge reissue". Give it a name and a message; it gets its own routing and outcome. Custom use cases can be disabled or deleted. Each use case also has a **key** (shown under its name), which is what the API and connectors send.

## Routing: who gets which flow

Under **Who**, each rule maps one or more directory groups to a flow. Rules are evaluated top to bottom and **the first match wins**, so put narrower groups above broader ones. The last rule, **Everyone else**, always exists and catches anyone no rule above matched. When it is the only rule it reads **Everyone**.

* **Add rule** adds a rule above **Everyone else**. Choose groups, then a flow.
* **Move up** and **Move down** reorder rules.
* Changes save as you make them.
* To limit a use case to certain groups, set **Everyone else** to **Can't use this** (under **Or block**). Anyone outside the groups above is then refused for this use case.

> [!TIP]
>
> Example: contractors don't have a reliable directory photo, so Face won't work for them. Add a rule **Contractors → Remote Contractor Flow** (Proofing first) above **Everyone else → Standard Corporate Flow**.

Rules target directory groups from your connected Entra ID or Okta directory. If a group is deleted from the directory, the rule shows a problem and the [setup review](https://docs.truu.ai/idv/getting-started/go-live.md#review-your-setup) asks you to choose a new group.

## Outcome: what happens after

Under **When it ends**:

* **Passed**: choose what TruU does after a successful verification.

  | Option | What happens |
  | - | - |
  | **Report only** | Records the result. Changes nothing. |
  | **Issue a Temporary Access Pass** | Issues a Windows Temporary Access Pass so the employee can sign in and add a new method. Requires [Windows TAP](https://docs.truu.ai/idv/connect/windows-tap.md). |
  | **Ping re-enrollment** | Resets the employee's PingOne MFA devices so they can register again. Requires [PingOne MFA](https://docs.truu.ai/idv/connect/pingone-mfa.md). |

  An option is only selectable once its connector is set up.
* **Failed**: the employee sees why and can try again, up to the workspace's attempt limit.

## How a verification gets its use case

| Started from | Use case |
| - | - |
| Help desk app | Helpdesk |
| Self-service portal | Credential reset |
| Microsoft Teams | The agent picks one of the use cases allowed for agents; with `verify me`, the employee picks one allowed for self-service |
| ServiceNow | **Verify Identity** on a record sends Helpdesk; Flow Designer sends the use case you pick (Help desk, Pre-hire or Password reset) |
| TruU Passwordless, the API | The use case key sent with the request. API clients can be limited to certain use cases. |
| Anything that names no use case | Verification |

Each person can have one active link per use case. Sending another for the same person and use case reuses the existing request and refreshes its expiry, so the employee never has two live links for the same thing. The self-service portal is the exception: a new portal request replaces the previous link, which stops working.

## Related

> [card] [Flows and templates](https://docs.truu.ai/idv/build/flows.md)
>
> Build the flows your rules point at.

> [card] [Verification requests and links](https://docs.truu.ai/idv/build/verification-requests.md)
>
> Request statuses and what happens to a link.


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