Home/Platform/Four portals, clear roles

Trusted Records · Platform

Four portals, clear roles

Separate execution, oversight and approvals across the same records lifecycle.

One lifecycle, four authorities

Portal	Work	Outputs
DIG · Digitization Operations Portal	Active batches; pending reviews; interrupted stations; sheets awaiting reconciliation; QC results and outstanding items before delivery.	Source images, approved metadata, QC reports, sheet–image links and a versioned delivery manifest. Acceptance begins only after outstanding discrepancies receive a decision.
GOV · Records Governance & Preservation Portal	Packages awaiting registration; metadata corrections; access requests; retention schedules; active holds; failed fixity checks and migrations awaiting approval.	Records with RecordIDs, versioned metadata and policies; access histories; fixity reports; preservation packages and migration/disposition decisions.
ADM · Platform Administrator Portal	Access requests; pending changes; incompatible devices; failed webhooks; service incidents; usage reconciliation and expiring support grants.	Versioned configurations, grant history, change approvals, operating evidence and incident reconciliation. Platform administration does not automatically grant access to every record.
CUS · Customer Records Owner Portal	Stage-level progress; pending customer responses; QC results; packages awaiting acceptance; support requests and costs using agreed units.	Acceptance decisions, outstanding-item lists, delivery receipts and cost reconciliation. Partial acceptance does not close the entire project.

Coordinate paper records from intake to handover: preserve order, assess quality and resolve discrepancies at each station.

Register, access and preserve records under policy: identify authoritative representations, authorized users and permitted lifecycle disposition.

Govern organizations, permissions, configurations and integrations while preserving project responsibility boundaries and privileged-action controls.

Track service delivery, inspect results, request corrections and accept portions; receive records with metadata and handover evidence.

Connect paper and born-digital records through persistent identifiers, policies and evidence.

Exercise ingest → job tracking → registration → verification with synthetic data.

Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.

Agree record classes, quality criteria, permissions and evidence before scaling.