---
title: Journeys
slug: one-touch-kyc/journeys
createdAt: 2026-07-31T08:18:13.920Z
---

## Journeys — monitoring your users

A **Journey** is one user's actual verification attempt, generated from a Flow. In practice,
journeys are usually created by your own application calling the [Create Journey API](https://docs.signzy.com/one-touch-kyc/create-journey-api) — the dashboard is mainly where you monitor and manage them.

### Starting a journey manually

If you want to generate a verification link yourself (for testing, or to send manually to a
specific user) rather than through your own integration:

1. Go to the **Flows** tab.
2. On the row for the flow you want to use, click the **link icon → Create journey**.
3. Fill in the journey's settings (redirect URLs, link expiry, etc.) and, optionally, any known user details.
4. Submit — the verification link opens in a new tab, ready to send to your user.

### All Journeys

The **Journeys → All** page lists every journey:

- **Search** by journey ID or name, filter by **date range**, **flow**, or **status** (Not Started / In Progress / Completed / Abandoned / Terminated).
- The table shows each journey's ID, when it was created/updated, the user's name (if captured), how far they've progressed, and their current status.
- Click a row to open the full journey report. The list refreshes automatically while journeys are still in progress, so you don't need to reload the page.

### Journey report

Opening a journey shows everything captured during that verification: submitted documents, selfie/liveness results, extracted user details, and a full status timeline. From here you can:

- **Copy Json** — copy the raw result data.
- **Remove User Data** — permanently delete the user's personal data for this journey (available once it's reached a final status).
- **Mark as Case** — flag this journey for manual review, assigning it to a teammate with a status, priority, risk level, and category.

### Journey Cases

Journeys flagged for manual review appear under **Journeys → Cases**, where you can filter by who they're assigned to, flow, risk, status, priority, or category — useful for teams that manually review flagged or high-risk verifications before final approval.
