Back Office Overview
The back office is the platform's built-in UI for the people who operate a verification program — reviewing ambiguous cases, investigating fraud, and correcting records. It is available on the Stored tier (there are no records to manage on the session-based tier).
What it is for
| Job | Where |
|---|---|
| Monitor volumes and clear the review queue | Dashboard |
| Inspect and resolve individual verifications | Digital Identities → detail |
| Manage customers and their history | Customers → detail |
| Track what was issued to customers | Assignments |
| Decide review cases and duplicates | Manual Review |
Finding records
The Customers and Digital Identities lists share one search box. Type a name or a number, then choose in the drop-down which field to search. The search runs only when you choose a row or press Enter, never while you type.
| Field | Lists | Matching |
|---|---|---|
| Name | Customers, Digital Identities | Similarity search on the name from the identity document. It tolerates typos and spelling variants, and a single name part is enough. Needs at least 3 characters. The best matches are listed, ordered by similarity. |
| Document number | Customers, Digital Identities | Exact, upper and lower case are treated as equal. |
| Personal number | Customers, Digital Identities | Exact, upper and lower case are treated as equal. |
| External ID | Customers | Exact. |
- Filters narrow the list with or without a search: status (Active / Blocklisted for Customers; Incomplete / Review / Accepted / Rejected for Digital Identities), the duplicity check result (Digital Identities), document type, issuing country and a date-of-birth range.
- Only one search runs at a time per user, and after a search the search button stays disabled for a few seconds (3 by default). The name search settings — how many candidates are considered, the minimum name similarity and that pause — are part of the document duplicity check configuration in IDV Configuration.
- The active search and filters are part of the page address, so switching tabs, the browser's Back button, a reload or a shared link keep them. The x in the search box clears the search and keeps the filters.
- Anonymized records never appear in lists or search results.
The Assignments list is searched by the exact item identifier or external ID and by Customer ID, and filtered by assignment status.
Roles
Three roles gate what a user can see and do (enforced by the platform, not just the UI):
| Role | Can do |
|---|---|
| Operator | View records; work the review queue; Accept / Reject; resolve duplicates. |
| Supervisor | Everything an Operator can, plus edit Customer data, reset decisions to review, blocklist, and anonymize. |
| Administrator | Everything a Supervisor can, plus configuration and user management — see Administration. Full detail in Roles & Permissions. |
The third writer
The back office is one of three ways records change, alongside verification workflows and the Customer API. Every human action here is audited with actor, timestamp, and a before/after diff, and can be delivered to the Company's backend as a record-action webhook.