A verification workflow template is the blueprint for a verification. Each workflow template lists the checks an applicant goes through, the order they run in, and the per-check configuration. Every verification you start references a workflow template, so when you adjust the workflow template you change every future verification built from it.

## Before you start

You need an active organization and the **Owner**, **Admin**, or **Manager** role to create or edit workflow templates. **Members** can view workflow templates but cannot author them. Open **Dashboard → Workflows** to land on the list page.

You can preview the applicant journey live in the editor before you save.

## Create a workflow template

Click **New workflow**. The page splits into two surfaces:

- **AI setup chat** at the top. Describe the workflow in plain language ("collect name and date of birth, then run a sanctions screen"); the assistant emits a starter document you can refine. The chat may be unavailable in some regions; you simply fall through to the manual editor.
- **Toggle editor and live preview** below. Each check is a switch with its own configuration controls when enabled.

Give the workflow template a name and an optional description. The name appears in the verification list and in audit-log entries, so prefer something descriptive ("Standard sanctions screen") over a code ("v2-final").

## Add checks

Toggle the checks you want in the workflow template. The editor surfaces five check types: `collect_user_info`, `id_verification`, `watchlist`, `background_us_criminal`, and `background_global`. See [Choose the right check types](/guides/workflows/workflow-templates-check-types) for the comparison.

The order in the editor is the order the applicant experiences. `collect_user_info` should sit first because the data it captures feeds every downstream check. Applicant-facing checks render screens in the verify journey; server-side checks run automatically once their inputs are available.

## Configure thresholds

Each check exposes the controls that matter for it:

- **Watchlist**: set the minimum match confidence (50–99%). Lower thresholds catch more hits but produce more false positives that go to manual review.
- **Background checks**: pick whether to include US-only or global sources. The jurisdiction is implicit in the check type itself.
- **Collect user info**: legal name is always collected. Email, phone, date of birth, and home address are toggleable; email and phone are on by default. Downstream checks perform better with more contact data, so removing fields is a deliberate tradeoff.
- **Identity document verification**: choose which document types you accept (passport, driver's license, national ID card, residence permit, visa, work permit; at least one stays selected). The **Face match** control sets the biometric mode: **Off** for document only (`none`, the default), **Selfie photo** (`selfie`), or **Active liveness** (`liveness`). The biometric check is optional and the modes are mutually exclusive. See [Biometric modes](/guides/workflows/workflow-templates-check-types#biometric-modes) for the comparison.

The live preview re-renders as you change controls so you see the applicant view without leaving the editor.

## Add fraud signals (optional)

The **Fraud signals** section lets a workflow watch for suspicious patterns (many verification attempts from one device, networks with a poor reputation, automated behavior, and the like) and surface them to your reviewers. It is off by default and opt-in per workflow. See [Add fraud signals to a workflow](/guides/workflows/workflow-templates-fraud-rules) for the full walkthrough.

## Publish and version

A workflow template has two switches that govern how it is used:

- **Active**: when on, the workflow template can back new verifications. Turn this off to retire a workflow template without deleting it.
- **Default**: when on, this workflow template is the one used when you start a verification without naming a workflow template. Only one workflow template per organization can be the default at a time.

Save the workflow template. Saving updates the existing workflow template or creates a new one, then routes you to the edit page.

## Use the workflow template

Once the workflow template is active, reference it by id when you start a verification, or leave the workflow template id off the call and rely on the default. See [Start a verification](/guides/verification/create-a-verification) for the request shapes. Every verification built from this workflow template inherits its check list and configuration; workflow templates are not versioned, so edits affect future verifications only. Completed verifications retain the document they were created against.

For terminology, see the [Glossary](/glossary).