Skip to content
Docs

Start typing to search the documentation.

Workspaces overview

On this page

Every verification starts by picking a workspace in the dashboard. A workspace is the kind of question you ask about a user; the flow you configure decides the exact rules. There are five:

WorkspaceThe question it answersCost
Pre-KYC”Who is this user?” (identity rules, plus data reveals)25 credits
Age Verification”Is this user old enough?“10 credits
Proof of Human”Is this a unique, real person?“10 credits
Sovereign”Is this user from a country I allow?“10 credits
Custom Config”Give me exactly these identity fields, under my custody”25 credits

How to choose

Ask what your product decision actually depends on, and pick the narrowest workspace that answers it. Narrower workspaces disclose less about your users and cost less:

  • You need identity attributes (name, date of birth, document details) or several rules at once → Pre-KYC. It’s the only workspace with data reveals.
  • You only need an age floor → Age Verification. Nothing else is asked or revealed.
  • You need one account per person → Proof of Human. It’s built around the nullifier.
  • You need to restrict access to specific nationalities → Sovereign. The allowlist is the whole workspace.
  • You need the raw identity data itself, stored by you and not by Self → Custom Config (early access, Enterprise plan). Your organization takes custody of the disclosed fields; Self keeps nothing.

What they all share

Whatever the workspace, the mechanics are identical:

  • The same integration. One sessions.create(...) call, a hosted page the user opens, and a signed verification.completed webhook. Switching workspaces later is a config change, not a code change.
  • The same privacy model. The user proves facts with a zero-knowledge proof; you receive pass or fail results (plus any fields you explicitly requested), never the underlying document. See How verification works. Custom Config goes one step further: the disclosed data is delivered only to you, and Self stores none of it.
  • A security level. Every workspace lets you choose Standard (the document is genuine) or Hi-security (the user physically scanned the document’s chip, the default). See Disclosures.
  • Both verification modes: Backend (the default) or On-chain. The exception is Custom Config, which is backend-only.
  • Test and live environments, mock passports, and the same per-verification pricing model.

A workspace holds one active configuration at a time, and a deployed configuration is immutable: to change it, archive it and create a new one. The exception is Custom Config, where an organization runs many active configs side by side. See Anatomy of a flow.

Was this page helpful?