Documentation / Connections / Organizations
Trials
How organization records connect to trial records in TrialStack.
This is a dual-bound connection. The same junction links an organization to a trial and a trial to an organization. Both directions share the same underlying record.
Why it matters
- a study must remain linked to the correct sponsor, CRO, or partner organization
- reviewers need organization context around a trial for delegation and oversight
- operational reporting depends on clear organization-to-trial relationships
- the junction captures role and primary-organization status
Dual-bound relationship
flowchart LR O[Organization] -- "role · primary · version" --> T[Trial] T -- "role · primary · version" --> O
Junction fields
From the organization page (organization → trial)
| Column | Description |
|---|---|
| Role | The organization’s role in the trial — maps to trialOrganizationRole dictionary. Default when connecting: sponsor |
| Primary | Whether this is the primary organization for the trial (Yes / No) |
| Version | Junction version counter |
From the trial page (trial → organization)
| Column | Description |
|---|---|
| Role | Same trialOrganizationRole value |
| Primary | Same primary flag |
| Version | Junction version counter |
Operations
| Action | From organization page | From trial page |
|---|---|---|
| Connect | Pick a trial (default role: sponsor) | Pick an organization |
| Disconnect | Remove the trial link | Remove the organization link |
| Reconnect | Update role / primary status | Update role / primary status |
From each side
- Use Organizations for the entity relationship.
- Use Trials for the governed study record.