Create an organization and invite a user; establish context, assign roles and deny out-of-scope privileges.
Trusted Records · Platform
Organization and user onboarding
Establish organizations, tenants and user permissions against verified legal records and agreed data scope.
Inputs and starting conditions
Legal entity/domain/representative details, DPA/terms, billing profile, data residency and initial administrator.
Workflow and control gates
- 01Check entity / duplicates
- 02Approve documents
- 03Provision tenant
- 04Invite / activate
- 05Check roles and MFA
Separate request and approval for high-impact changes. Invitations expire; activation does not grant all-project access. Select MFA/passkeys under verified policy.
Exceptions and recovery
Unverified domains/representatives, duplicates or provisioning failure stay pending with reasons and traceable retries; do not create extra tenants to bypass failures.
Roles, outputs and states
| Responsibilities | Evidence and states |
|---|---|
| Organization administrators submit evidence; approvers review grounds; platform administrators provision; users activate invitations. | Entity evidence, versioned terms/DPA, provisioning logs, invitations, activation and role audit. States: requested → checked → approved → provisioned → active. |
Scenario and acceptance criteria
Complete only when
Accounts, organizations, projects and grants retain history.
Interfaces for this workflow
Integration handoff
End-to-end integration workflows
Connect technical states to business decisions instead of merely listing endpoints.
Read detailsOpenAPI and Swagger Reference
The proposed contract is rendered from one local specification; no network Try-It or real credentials.
Read detailsErrors and next actions
A consistent error envelope guides recovery without disclosing sensitive data.
Read detailsContinue the workflow
Projects and readiness
Translate contractual scope into verifiable operational configuration before go-live.
Read detailsTwo 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 detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment