Workflows
Roles And Workflows
A starter map for organizing customer documentation by the teams that use TrialStack.
Roles And Workflows
Customer documentation is easiest to use when it follows the teams doing the work rather than mirroring the backend.
Workspace administrator
This role usually owns:
- workspace setup and onboarding progress
- preferences and organization-level defaults
- access-sensitive operations
- visibility into usage, deleted records, and policy-sensitive workflows
Start with:
Trial operations
This role usually owns:
- creating and maintaining trial records
- linking organizations, sites, contacts, and related records
- coordinating day-to-day document and evidence workflows
- using history, compare, and restore when changes become risky
Start with:
Clinical, quality, and review teams
This role usually owns:
- protocol-facing trial workflows
- approvals and sign-off boundaries
- evidence quality and traceability
- review of sensitive or AI-assisted output
Start with:
Content and evidence owners
This role usually owns:
- drafting and updating documents
- deciding when a revision is safer than editing the base record
- assembling evidence packs for review
- attaching supporting media and contextual material
Start with:
Integration owners
This role usually owns:
- connecting external systems to TrialStack
- understanding when to use UI workflows versus API calls versus job-backed operations
- aligning technical implementation with the operational workflow already used by the customer team
Start with:
- Platform overview
- Integrations and API
- the workflow pages for the records your integration will create, read, or update
How to use these role guides
Most teams span more than one role. The useful pattern is:
- assign an admin owner
- assign operational owners for trials and governed content
- assign review owners for approval-sensitive workflows
- assign integration owners only after the product workflow is understood