Dashboard guide

The operations dashboard is where your team reviews verifications, acts on results, and configures your tenant. Access is scoped to your organization, so you only ever see your own customers.

Roles

Two roles cover day-to-day use.

Admin

Reviews everything, changes and resolves statuses, sends customers to re-verification, and configures tenant settings.

Observer

Read-only. Reviews verifications, results, and the audit trail, but cannot make changes.

Getting dashboard access

Dashboard users are provisioned by the Sentinel team. To add or change access, contact the Sentinel team with each person's email and the role they need (admin or observer). Give every person their own account rather than sharing one, so the audit trail attributes each action to the right individual.

Review verifications

The customer list shows everyone your tenant has verified. Search by name or contact, filter by status and date range, and export the filtered list. Open a customer to see the full record across these views.

Overview

The customer’s identity details and current status.

ID verification

Document data, the face-match result, and the OCR read.

Screening

The sanctions and PEP screening result.

Compliance report

A generated report you can export.

Audit trail

The full history of changes to the record.

Act on a verification

Admins can take action directly on a customer record:

Change or resolve a status, for example: accept or reject after reviewing a Conflict or Duplicate.
Send a customer to re-verification by moving them to Draft, with a reason the customer sees when they reopen their link. See Re-KYC and screening.
Resend the latest webhook for a customer if your endpoint missed it.

Status changes made here are reflected through the same webhooks and result retrieval your systems already use.

Configure your tenant

Admins manage the settings that shape verification and notifications:

Accepted documents: Which documents customers may submit.
Editable identifiers: Whether email and phone stay editable during the journey.
Webhook on customer creation: Also fire a webhook when a customer record is created.
Re-KYC on expiry: Which documents trigger re-verification when they expire.
Expiry warnings: Which documents to warn about, and how many days before expiry.

These settings also drive the hosted journey. Brand theme colors are not yet self-serve, so contact the Sentinel team to set them. See Dynamic link verification for how documents and identifiers affect the journey.

Audit trail

Every change to a customer is recorded with who made it: a member of your team, the API, the SDK, the dynamic link, or the system itself. This gives you an accountable history for compliance review.

Set up re-verification and ongoing checks in Re-KYC and screening.