Who executes and who decides?
Records managers approve registration and classification; access staff handle permissions; preservation officers monitor fixity and migration; authorized approvers decide holds and disposition.
Trusted Records · Platform
Records Governance & Preservation Portal
Register, access and preserve records under policy: identify authoritative representations, authorized users and permitted lifecycle disposition.
Roles and authority
Portal outputs
Records with RecordIDs, versioned metadata and policies; access histories; fixity reports; preservation packages and migration/disposition decisions.
Follow one task
- 01Validate package
- 02Register RecordID
- 03Apply access and retention
- 04Provide governed access
- 05Check and preserve
- 01Detect checksum mismatch
- 02Quarantine affected representation
- 03Compare recovery copy
- 04Approve recovery
- 05Recheck and retain history
Reference journey for business review; the website does not process records or connect devices.
Interfaces by task
Cross-portal handoff
GOV receives packages from DIG or digital sources; CUS accesses records within granted authority; ADM governs connectors and platform policy.
Born-digital ingest
Ingest digital documents while retaining context, format and provenance, with validation before official record registration.
Read detailsOfficial records management
Establish when documents become registered/declared governed records and preserve subsequent change history.
Read detailsRetention, legal hold and disposition
Expiry does not authorize deletion. Check retention triggers, all active holds and authority before disposition.
Read detailsLong-term digital preservation
Maintain readability, integrity verification and record context over time; backup is only part of recovery.
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 detailsFinal sources tied to business decisions
Workspace
Packages awaiting registration; metadata corrections; access requests; retention schedules; active holds; failed fixity checks and migrations awaiting approval.
Role-based workflows
Born-digital ingest
Ingest digital documents while retaining context, format and provenance, with validation before official record registration.
Read detailsOfficial records management
Establish when documents become registered/declared governed records and preserve subsequent change history.
Read detailsRetention, legal hold and disposition
Expiry does not authorize deletion. Check retention triggers, all active holds and authority before disposition.
Read detailsAuthorized search and access
Find the right record and provide only authorized representations, fields and access periods.
Read detailsLong-term digital preservation
Maintain readability, integrity verification and record context over time; backup is only part of recovery.
Read detailsConversion and migration
Change formats or repositories while preserving source–target reconciliation, version lineage and exceptions.
Read detailsPolicy, privacy and audit
Simulate and approve policy impacts before applying changes to records.
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