> For the complete documentation index, see [llms.txt](https://finext.gitbook.io/one-kyc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://finext.gitbook.io/one-kyc/admin/flows.md).

# Flows

The **Flows** section manages verification scenarios — from creation and configuration to publication and analytics. A scenario defines the sequence of steps a user goes through during verification.

## Scenario list

Every tenant scenario is shown with the following information:

* **Name** — scenario name.
* **Status** — current state: draft or published.
* **Last modified** — time of the last configuration change.

From the list you can edit, view versions, and view analytics for each scenario.

## Creating a scenario

You create a new scenario in one of two ways:

1. **From scratch** — an empty scenario where you add the steps you need one by one.
2. **From a template** — pick a ready-made scenario from the gallery and customise it for your organisation.

## Scenario editor

The visual editor lets you configure the set and order of verification steps:

* **Add steps** — pick the checks and data-collection stages needed for the scenario. KYC flows can include document, selfie, face matching, AML screening, fingerprint, country selection, and completion steps. KYB flows add company input, business document, company verification, and result steps.
* **Step order** — drag blocks to set the execution sequence.
* **Step parameters** — each step has its own settings: accepted document types, liveness check mode, whether the step is required, and other parameters.

After you save changes, the scenario stays in **draft** state. New sessions use the previously published version until you publish the updated configuration.

## Templates

The template gallery holds ready-made verification scenarios optimised for common use cases:

* **Basic KYC** — document and selfie.
* **Standard with AML** — document, selfie, and sanctions-list screening.
* **Age verification** — a simplified scenario for confirming age.

A template is used as the starting point: after selection, every step and parameter is editable.

## Redirect settings

The editor side panel exposes options for the verification completion screen when `redirect_url` is provided (set when the verification link is created):

* **Redirect behaviour on completion** — how the user is redirected back to your site:
  * **Show button** — the completion screen shows a "Return to site" button; the user clicks it to go back.
  * **Auto redirect** — automatic redirect to `redirect_url` after the configured delay.
* **Redirect delay (seconds)** — delay before the automatic redirect (0 to 60 seconds). Applies only in "Auto redirect" mode. Default is 3 seconds.

If the verification link was created without `redirect_url`, neither the redirect button nor the automatic redirect appears.

## Versions

The system keeps a version history for every scenario:

* **Published version** — used when new verification sessions are created.
* **Previous versions** — sessions created earlier continue running on the version they were initialised with.
* **Rollback** — you can promote one of the previously published versions back to active.

To publish a new version, click **"Publish"** in the scenario editor. From that moment, every new session uses the updated configuration.

## Scenario analytics

The analytics page shows metrics for the selected scenario:

* **Sessions started** — total number of sessions created from this scenario.
* **Sessions completed** — number of sessions that reached a final status.
* **Per-step conversion** — percentage of users who passed each stage.
* **Average time-to-complete** — average verification duration from creation to completion.

Use analytics to optimise the scenario: spot steps with high drop-off and decide on configuration changes.