Who executes and who decides?
Organization admins manage membership; project admins assign work; platform admins govern environments and integrations. Delegated support needs time limits, bounded scope and access history.
Trusted Records · Platform
Platform Administrator Portal
Govern organizations, permissions, configurations and integrations while preserving project responsibility boundaries and privileged-action controls.
Roles and authority
Portal outputs
Versioned configurations, grant history, change approvals, operating evidence and incident reconciliation. Platform administration does not automatically grant access to every record.
Follow one task
- 01Create organization/project
- 02Assign roles
- 03Validate configurations/connectors
- 04Approve change
- 05Monitor and audit
- 01Webhook fails
- 02Identify contract/access issue
- 03Approve configuration correction
- 04Replay with deduplication
- 05Reconcile before closure
Reference journey for business review; the website does not process records or connect devices.
Interfaces by task
Cross-portal handoff
ADM supplies permissions and configurations to DIG/GOV/CUS; project owners retain acceptance-scope and record-access authority.
Organization and user onboarding
Establish organizations, tenants and user permissions against verified legal records and agreed data scope.
Read detailsOrganization and platform administration
Manage permissions, tenant lifecycle and platform resources with clear privilege boundaries.
Read detailsIntegration governance
Authorize integrations and release them to production against approved contracts, certificates and tests.
Read detailsDevice fleet and lifecycle
TURAPING Flow R is the selected device. Sheet-level compatibility and deployment configuration require separate validation.
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
Access requests; pending changes; incompatible devices; failed webhooks; service incidents; usage reconciliation and expiring support grants.
Role-based workflows
Organization and user onboarding
Establish organizations, tenants and user permissions against verified legal records and agreed data scope.
Read detailsProjects and readiness
Translate contractual scope into verifiable operational configuration before go-live.
Read detailsOrganization and platform administration
Manage permissions, tenant lifecycle and platform resources with clear privilege boundaries.
Read detailsService models and billing principles
Reconcile accepted quantities with contractual rules before billing instead of charging all processing attempts.
Read detailsIntegration governance
Authorize integrations and release them to production against approved contracts, certificates and tests.
Read detailsSupport, incidents and change
Track issues through remediation evidence and closure with time-limited support access.
Read detailsDevice fleet and lifecycle
TURAPING Flow R is the selected device. Sheet-level compatibility and deployment configuration require separate validation.
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