The platform console is the tool of the people who run Trialion itself, not of the organizations that use it. It lives in the control plane, a separate application with its own database, its own sign-in and its own audit ledger, that keeps the list of organizations, provisions a new organization and its first administrator, holds the per-organization feature switches, shows a few counts and manages the platform's own administrators. It holds no clinical data, no plans, prices or quotas.
The two applications talk over a service boundary: the control plane tells the data plane (the trial application) to create an organization and invite its first administrator, to suspend or restore it, and answers which features an organization may use; the data plane tells the control plane how many users, studies, exports and bytes an organization holds, and whether the first administrator has come. Everything else, studies, people, roles, clinical data, is the organization's own and is not visible here.
| Page | What it is for |
|---|---|
| Signing in and platform administrators | How a Super-Admin signs in, the first administrator of a deployment, and inviting, suspending and restoring Super-Admins |
| Provision an organization | Creating an organization and inviting its first Organization Admin, and what to do when the push to the data plane fails |
| Manage an organization | The dashboard, the organization list, an organization's page, usage, suspending and restoring |
| Feature switches | The five licensed features, which are enforced, and how a change reaches the trial application |
| The platform audit ledger | Every Super-Admin action, append-only and hash-chained |
The console's menu has four entries: Dashboard, Organizations, Platform Admins and Platform Audit. After an organization is provisioned, the rest of its setup happens in the data plane, by that organization's own administrator: Set up your organization. The whole path, from the platform to a first study, is on From platform to first study.