Dashboard

The dashboard is the operational home for your integration. It's where you build and publish workflows, mint API keys, watch verifications come in, configure webhooks, and manage billing and team access. This page orients you to the main areas; the linked guides go deeper on each.

Overview

Your landing view: a real-time read on API usage, geographic distribution, method health, and success rates. Use it to spot anomalies — a drop in success rate or a spike in a particular jurisdiction — at a glance.

Workflows

Where you build the recipe every verification runs inside. Create a workflow, pick its use case and target markets, choose methods and composition, set preferences, and publish it. Two builders are available — a simple use-case-driven editor and a node-based visual graph for branching flows. Sessions always run the published version, so you can edit a draft without touching live traffic.

Sessions

A searchable log of every verification session, with its status, method, jurisdiction, environment, and result. Drill into a session to see its timeline and — where your plan includes it — a compliance evidence trail. This is the first place to look when debugging a specific verification.

Reviewing held sessions. When a workflow routes a session to manual review, it appears as Needs your review — a banner on the sessions list shows the pending count and the soonest auto-reject deadline. Open the session to adjudicate: captured ID imagery is shown in the Evidence tab (retained only while the review is open, watermarked, and purged automatically on decision), an optional AI recommendation summarizes the structured evidence (it never sees the images — always look at them yourself), and Approve clears the hold — the session verifies immediately when every other step already passed, or returns to requires_input so the person can finish the remaining steps (a pre-method review, or an all_of flow with steps left) — while Reject finalizes it as not verified. Undecided reviews auto-reject when the workflow's review window elapses. Reviewers are notified by an hourly digest email, a deadline reminder, and the dashboard bell.

API keys

Create and revoke secret keys (stile_sk_…), and review per-key usage. Secret keys are shown once, so store them immediately. Existing publishable keys remain visible in a collapsed legacy section while you migrate browser session creation to your server.

Webhooks

Register the webhook endpoints that receive verification events, choose which event types each subscribes to, and inspect delivery history. The deliveries view shows each attempt, the response your endpoint returned, and lets you retry a failed delivery once your endpoint is healthy. Rotate an endpoint's signing secret here if it may have leaked.

Billing

Manage your plan, view usage, and top up prepaid credits. The free tier (100 verifications/month by default) covers your first verifications each calendar month; usage beyond that is billed via prepaid credits. A sandbox organization is unbilled and capped at 500 sessions/month. See Testing for the zero-setup Workflow Sandbox and sandbox-organization behavior.

Team & roles

Invite teammates and assign roles to control who can manage keys, edit workflows, or view sessions. Organizations and applications let larger setups separate teams and products.

Settings

Org-level configuration, organized as General / Verification / Security:

• General — organization name and icon (an emoji or preset glyph with a color scheme; applications have the same customization in their edit dialog).
• Verification — Stile Trust Network participation. This toggle sets the organization-wide network dedup flag, which lets Stile recognize a credential hash already seen elsewhere on the network. It is not the switch for consent-based Trust Reuse: that is a separate, per-application feature enabled through PATCH /v1/trust_reuse/settings with an explicit liability acknowledgement, and turning on network dedup alone leaves it off.
• Security — require two-factor authentication for the organization, block publishable-key session creation, and the API inspector for logging recent API requests/responses during debugging.

Data-subject and erasure requests are handled through your account's support channel; they are not actioned from Settings.

The dashboard navigation does not currently include a standalone Compliance section or erasure-request queue. Verification-time jurisdiction resolution and the GET /v1/compliance/check lookup remain available through the API.

Next steps