---
title: User Guide
slug: one-touch-kyc/user-guide
createdAt: 2026-07-29T07:30:54.098Z
---

## Overview

A walkthrough of the OTKYC dashboard: setting up your account, building verification Flows, and monitoring the Journeys your users complete. If you're integrating programmatically instead, see the [API Integration Guide](https://docs.signzy.com/one-touch-kyc/api-integration-guide).

***

## Getting started checklist

- [ ] Generate an API key (**Settings → Team**) if you plan to integrate programmatically.
- [ ] Set up your callback URL (**Settings → Callback config**) so you're notified when a journey results.
- [ ] Build your first Flow (**Flows** tab).
- [ ] Create a test Journey from that Flow and try it yourself.
- [ ] Check the result on the **Journeys** tab.

***

## Settings

Everything account-wide lives under **Settings**, organized into tabs:

| Tab                         | What you'll find there                                                                                                                                                                    |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **General**                 | Manage the dropdown values used elsewhere in the dashboard — statuses, risk levels, categories, priorities.                                                                               |
| **Profile**                 | Your own name, phone number, job title, and password.                                                                                                                                     |
| **Organization**            | Your organization's details and preferences.                                                                                                                                              |
| **Team** *(Admins only)*    | Team details, and **API Keys** — generate, copy, or revoke the keys used to call the OTKYC API. You'll need a key here before programmatic journey creation will work.                    |
| **Automatic Data Deletion** | How long completed users' personal data is retained before it's automatically deleted.                                                                                                    |
| **Callback config**         | The URL and authorization key we'll send verification results to automatically. See [Callbacks](https://docs.signzy.com/one-touch-kyc/callbacks) in the API reference for what gets sent. |
| **Tour Management**         | Replay the guided in-app tours for any page.                                                                                                                                              |

### Setting up your callback URL

1. Go to **Settings → Callback config**.
2. Enter your **Callback URL** — it must start with `https://`.
3. Enter an **Authorization Key** — a secret of your choosing that we'll include on every callback so you can confirm it really came from us.
4. Click **Save Changes**.

Your saved key is masked afterward for security; click the pencil icon next to it if you need to
change it later.

### Generating an API key

1. Go to **Settings → Team**.
2. Click **Generate API Key**.
3. Copy the key immediately and store it somewhere safe — for security, you won't be able to view the full key again once you leave the page.
4. Use **Generate CURL** on any existing key for a ready-to-run example request.
5. If a key is compromised or no longer needed, remove it from the same table — this takes effect immediately.

***

***

## End-to-end walkthrough

1. **Settings → Team** — generate an API key.
2. **Settings → Callback config** — set the URL where you want results delivered.
3. **Flows → New flow** — build your verification process (documents, liveness, screening, branding).
4. Create a journey — either call the [Create Journey API](https://docs.signzy.com/one-touch-kyc/create-journey-api) from your application, or use **Flows → (row) → Create journey** to generate a link by hand.
5. Send the resulting link to your user.
6. Get notified automatically via your callback URL once they finish — or check **Journeys → All** any time to see live status.
7. Review the result on the journey's report page; mark it as a case if it needs manual follow-up.
