What this is, and who it is for
Provisioning creates an organization (a tenant) and invites its first Organization Admin. It is the single highest-authority act in the system: it is where a new identity with full authority over a new tenant comes into existence, so it is done only by a Super-Admin, and it is recorded on both planes' ledgers. There is no self-service sign-up for an organization.
Where to find it
Organizations → Provision organization (Creates the organization and invites its first Org Admin in the data plane.).
- Opens the dialog that creates an organization.
- Filters the list by name or code.
What you can do
Fill in the form:
| Field | Rule |
|---|---|
| Organization name | Required |
| Code | Required; 2 to 32 letters, digits or single dashes between them, in capitals (Letters, digits and dashes, like ACME-PHARMA.). Unique across the platform. It cannot be changed to something that exists |
| Type | Sponsor, CRO, Site or Vendor |
| Country | A two-letter country code, or Not set |
| First Org Admin full name | Required, 2 to 255 characters (As it is to appear on their signature and in the audit trail.) |
| First Org Admin email | Required; a valid address |
Choose Provision. Three things happen, and the dialog tells you which, step by step:
- Organization created. The organization is saved in the control plane with status provisioning, and
org.provisionedis written to the ledger, in one transaction. - Pushed to the data plane. The control plane tells the data plane to create the organization, its first Organization Admin (a person is one login across organizations: found by address, or created) and their membership, and to start the organization's setup wizard. The organization becomes active and the time of the sync is kept.
- Invitation mailed. The data plane queues the invitation mail with a single-use link (valid 72 hours) to the first administrator: A mail with the setup link is on its way … They open it and set the organization up. If the address was already invited, nothing new is sent (Invitation already sent); if the person is already an administrator, nothing is sent (Invitation already accepted).
If the push fails, the dialog says {name} is saved: It could not be pushed to the data plane yet, with what the data plane answered, and The organization is saved with status "provisioning". Nothing is lost. Open it and press Retry sync: that pushes it again and sends the invitation. Open organization goes to the organization's page.
Retry sync, and correcting an organization
On an organization still in provisioning, Retry sync pushes it again; the push is idempotent (it never duplicates the person, the membership or the role) and the dialog tells the same three steps. The API can also correct an organization's name, code, type, country and first administrator's address and name (PATCH /organizations/{id}, a reason of at least 5 characters, both values written to the ledger as org.updated), after which a retry pushes the correction. The console has no screen for it yet.
The first administrator
The first Organization Admin opens the link, signs in with an emailed code and is taken to the setup wizard (Set up your organization). An older link says it was replaced, one used twice says it was accepted, and one past 72 hours says it expired; the organization's Administrators tab shows which, and Resend invitation issues a new link (Manage an organization).
- The organization's name.
- A short unique code: letters, digits and dashes.
- The first administrator's address; the invitation goes here.
- Creates the organization, pushes it to the data plane and queues the administrator's invitation.
Every option
Organization states
| State | Meaning | Moves to |
|---|---|---|
| provisioning | Saved in the control plane; the data plane does not have it yet | suspended, closed (and active only through a successful sync) |
| active | In the data plane; its people can sign in | suspended, closed |
| suspended | Everyone is signed out and cannot sign in; data kept | active, closed |
| closed | Final; the data plane treats it as suspended | none |
An organization that never completed its handshake cannot be "restored" to active: it needs a sync. A closed organization is not reopened by a restore.
What the system records
Control plane ledger: org.provisioned (code, first administrator's address and name), org.data_plane_synced (or org.data_plane_sync_failed with the status and error) and, for a corrected organization, org.updated. Data plane: the tenant provisioning event and platform.user.invited. See The platform audit ledger and Audit events.
What you cannot do, and why
- Reuse a code, or use one that is not letters, digits and dashes.
- Delete an organization. Nothing is deleted; an organization is suspended or closed.
- Provision without a named first administrator. A person is known by name from the first sign-in.
- See anything the organization holds beyond counts: studies, people and data are not shown here.
Compliance Q&A
Yes. Only a Super-Admin can provision; the control plane records who did it, the organization's code and its first administrator in its hash-chained ledger, and the data plane records the creation of the tenant and the administrator in its own.
Evidence: control plane service (org.provisioned in the same transactionorg.data_plane_synced)data plane provisioning event platform.tenant.provisionedsimulation of 20 Oct 2026, step 1
Related
The platform console · Manage an organization · Set up your organization · From platform to first study