Dashboard overview
The Drukverify Dashboard at dashboard.drukverify.com is the logged-in self-serve UI your team uses to manage an integration: minting API keys, watching usage, inspecting the audit log, wiring webhook endpoints, tuning decision thresholds and storage, and inviting collaborators. It is also where reviewers open individual liveness checks, OCR scans and face registrations, including the stored images when your storage policy keeps them. It complements the SDKs (in your app code) and these docs (the API surface).
Who it's for
Every tenant has at least one user on the dashboard: the person who set the account up. From there, admins invite teammates and assign roles.
| Role | Reads | Writes | Typical user |
|---|---|---|---|
| admin | everything | everything: keys in both modes, team, webhooks, settings | The person owning the integration end-to-end. |
| developer | everything | test-mode keys | Engineers building against the API who shouldn't mint production credentials. |
| viewer | everything | nothing | Compliance, ops or finance roles who need to see traffic and results but not change anything. |
Role gates are enforced at the API layer too; the UI mirrors them so disabled buttons explain why an action isn't available.
What the dashboard covers
- API keys — create, name and revoke your
dv_sk_/dv_pk_keys in both modes. - Team — invite users, change roles, see who has been logging in.
- Usage — daily call counts and billable units by feature, variant or status, over 7, 30 or 90 days, per mode.
- Audit log — every API request your keys and
session tokens have made, with status, latency and
request_id. - Results — the liveness checks, OCR scans, fraud checks and face registrations stored for your tenant, with captured images, evidence regions and per-component scores where policy keeps them.
- Webhooks — register endpoints for
ocr.completed,face.verify.completedandliveness.check.completed, with a one-time signing secret on creation. - Settings — tenant metadata, your storage policy and the decision thresholds your tenant may tune, with a change history.
What it does NOT cover
- Provisioning a new tenant. New tenants are created by ops; once one exists, the setup flow enrolls the initial admin through an emailed setup link.
- Plan and billing changes. Email
ops@drukverify.com. - Live in-product API testing. Use the
API reference, or call
https://api.drukverify.comdirectly with your secret key.
Security model
- Sessions use a short-lived signed cookie (
dv_dash, 12 hours) issued after email, password and TOTP. - TOTP is required for every role. Six single-use backup codes are generated at enrollment.