Who executes and who decides?
Project observers track progress; authorized users access records; acceptance approvers confirm accepted portions. Ownership does not replace an explicit access decision.
Trusted Records · Platform
Customer Records Owner Portal
Track service delivery, inspect results, request corrections and accept portions; receive records with metadata and handover evidence.
Roles and authority
Portal outputs
Acceptance decisions, outstanding-item lists, delivery receipts and cost reconciliation. Partial acceptance does not close the entire project.
Follow one task
- 01Confirm scope
- 02Track progress
- 03Inspect outputs
- 04Accept manifest
- 05Receive delivery
- 01Detect incorrect metadata
- 02Request item-specific correction
- 03Provider corrects with history
- 04Review revised version
- 05Accept eligible portion
Reference journey for business review; the website does not process records or connect devices.
Interfaces by task
Cross-portal handoff
CUS sends quality feedback to DIG, requests governed access from GOV and engages ADM for accounts or support.
Owner progress and access
Owners inspect progress, quality and provenance before accepting outputs.
Read detailsDelivery, acceptance and closure
Accept against manifests/evidence; disputed items remain separate from accepted quantities.
Read detailsIdentity, accounts and sessions
Place customers in the correct organization/project and recheck identity before high-risk actions.
Read detailsUsage, invoices and payment
Let owners reconcile charges with accepted quantities and agreed billing rules.
Read detailsFrom volume to invoice
Phased, deposit, project or recurring arrangements are contractual. Separate scanned, QC-approved, accepted and billable volumes; retries/rescans/provider faults do not automatically create charges. Partial acceptance sends only approved items to reconciliation. No approved price list or invoice-issuance time is supplied.
NAPAS QR and Trusted Billing
Integration design separates payment confirmation, reconciliation and invoice issuance.
Read detailsPayment request
Design payment requests from acceptance; no payable QR is generated.
Read detailsInvoice request
Proposed Trusted Billing submission; confirm schemas/provider mapping.
Read detailsFollow the same dossier
synthetic-dossier-001 • Reference journey, not a real record
DIG · Sheets and images / QCGOV · Registration / access / preservationADM · Configuration / audit / serviceCUS · Acceptance / costs / invoice
Paper–image discrepancies remain under review; failed QC requires correction; missing permissions deny access; partial acceptance retains outstanding items; invoice failure does not reverse payment confirmation.
Preservation handoff and responsibility
DIG retains QC and sheet–image mappings. GOV selects profiles and registers/reviews evidence. ADM manages connectors, failed jobs and audits within authority. CUS sees permitted statuses and delivery packages. New LTANS content is a reference design rather than a released product screen.
LTANS — long-term evidence preservation
Connect records lineage to Mobile-ID’s published LTANS capability; agree the Records configuration in a contract and profile.
Read detailsService Playground — task-based experience
Exercise a records workflow with forms, requests/responses and a timeline. Use synthetic data in offline simulation or a local HTTP mock.
Read detailsSample package export and verification
Check synthetic-package hashes before delivery; distinguish byte integrity from authenticity, signatures and legal status.
Read detailsWorkspace
Stage-level progress; pending customer responses; QC results; packages awaiting acceptance; support requests and costs using agreed units.
Role-based workflows
Identity, accounts and sessions
Place customers in the correct organization/project and recheck identity before high-risk actions.
Read detailsOwner progress and access
Owners inspect progress, quality and provenance before accepting outputs.
Read detailsDelivery, acceptance and closure
Accept against manifests/evidence; disputed items remain separate from accepted quantities.
Read detailsUsage, invoices and payment
Let owners reconcile charges with accepted quantities and agreed billing rules.
Read detailsControlled customer support
Customers track requests and authorize the scope/duration of support access.
Read detailsContinue the workflow
Two journeys, one records lifecycle
Connect paper and born-digital records through persistent identifiers, policies and evidence.
Read detailsIntegration quickstart
Exercise ingest → job tracking → registration → verification with synthetic data.
Read detailsIntegrity, provenance and evidence
Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment