Organizations and projects
People belong to an organization; keys, workflows, sessions and settings belong to a project.
An organization is your company in OKYC: its people, their roles and two-factor policy. Inside it, projects keep separate products or lines of business apart — a lending app and a wallet, for example.
| Belongs to the organization | Belongs to each project |
|---|---|
| Team members and their roles | API keys (test and live) |
| Invitations | Workflows and their branding |
| Two-factor requirement for owners and admins | Sessions, evidence and decisions |
| Sign-in and security events | Webhooks and events |
| Settings: retention, embedding, redirects, providers | |
| Usage |
Your role applies in every project of the organization. Switch projects from the top of the dashboard's sidebar; owners and admins create new ones there (New project). A new project starts like a new account: its own test key and starter workflows.
Each project also has its own encryption keys. Nothing in one project — a session, a document number, a person — is visible from or matched against another project, or another customer.
With the API
An API key belongs to one project, so a request needs nothing else: sessions it creates, and the webhooks they send, are that project's. To work in another project, use that project's key.
Flutter
Okyc.start pushes a full-screen verification route (Flutter 3.24+, Android and iOS) and returns a typed result.
Workflows and the builder
A workflow is the list of steps an applicant completes and the rules that decide the outcome.
© 2026 Aiistic Technologies Private Limited. OKYC is a product of Aiistic Technologies Private Limited. Privacy notice