Dashboard overview
The dashboard is where you configure products, manage keys, watch traffic, and pay for what you use. This page is a map.

Top-level sections
Home
The landing surface. It greets you, surfaces a low-credit alert when your balance runs low, and shows a card for each of the four products (Pre-KYC, Age Verification, Proof of Human, Sovereign) alongside a Resources row: Developer Docs, Mobile SDK, and Status Page.
Products
Each product (Pre-KYC, Age Verification, Proof of Human, Sovereign) has its own page and holds one active configuration at a time. The page splits into tabs:
- Configure: disclosure rules and (for Pre-KYC) additional data.
- Test and Live: the per-environment integration tabs. Each shows the configuration’s
flowId, SDK snippets, and a link to your API keys. They unlock once the configuration is deployed. - Activity log: verifications and errors over time.
- Configuration settings: archive the configuration, plus a usage and credit snapshot.
The Test, Live, and Activity log tabs stay locked until the configuration is deployed. To change a live configuration you archive it first, then create a new one.
Archive
Where a product’s previous configurations go once you replace them. Archived configurations have their proof requests deactivated, but their activity log stays viewable for audit.
Developer
Org-scoped developer surfaces, in the sidebar under Developer:
- Webhooks: register HTTPS endpoints and manage signing secrets.
- API keys: generate and revoke the
sk_test_…/sk_live_…keys your backend uses. - Developer Docs: a link to these docs.
Settings
Org-wide configuration, organized into tabs:
- General: organization name and icon, your profile, theme, sign out, and leaving the organization.
- Usage & Billing: plan, credit balance, and usage.
- Audit: an exportable record of changes.
- People: members and invites. Visible only to owners and admins.
- System Status: live service status.
Permissions
Members have one of three roles, owner, admin, or member, which control who can manage keys, webhooks, and billing. See People → Roles. For machine access, use API keys rather than a member’s login.
Thanks for your feedback!