Roles And Workflows
A starter map for organizing customer documentation by the teams that use TrialStack.
Read by responsibility
flowchart LR
Admin[Admin] --> Docs[Docs path]
Ops[Operations] --> Docs
Review[Review] --> Docs
Integration[Integration] --> Docs
Customer documentation is easier to use when it follows the teams doing the work instead of mirroring backend or schema structure.
Match the role to the docs
| Role | Main concerns | Best starting pages |
|---|---|---|
| Workspace administrator | setup, defaults, access, oversight | Onboarding, Preferences, Users |
| Trial operations | study records, linked context, day-to-day change | Trials, Documents, Evidence Packs |
| Clinical, quality, and review teams | sign-off, approvals, sensitive change, evidence | Trial Approval, Document Approvals |
| Content and evidence owners | drafting, revision, support material | Documents, Revisions, Evidence Packs |
| Integration owners | system flow and exact contracts | Platform Overview, Integrations & API, the relevant record workflow pages |
Expect overlap
Most teams span more than one role. The useful pattern is to assign a clear admin owner first, then assign operational, review, and integration ownership once the first workflow is understood.