Documentation / Connections / Contacts
Trials
How contact records connect to trial records in TrialStack.
This is a dual-bound connection. The same junction links a contact to a trial and a trial to a contact. Both directions share the same underlying record.
Why it matters
- a study needs named owners, investigators, coordinators, and monitors
- reviewers need clear stakeholder context around a trial
- contact changes affect trial-facing operational ownership and delegation
- the junction captures role and delegation status so that responsibility is explicit
Dual-bound relationship
flowchart LR C[Contact] -- "role · delegation · version" --> T[Trial] T -- "role · delegation · version" --> C
Junction fields
From the contact page (contact → trial)
| Column | Description |
|---|---|
| Role | The contact’s trial role — maps to trialContactRole dictionary. Default when connecting: study_coordinator |
| Delegation | Whether the contact has delegation authority (Yes / No) |
| Version | Junction version counter |
From the trial page (trial → contact)
| Column | Description |
|---|---|
| Role | Same trialContactRole value |
| Delegation | Same delegation flag |
| Version | Junction version counter |
Operations
| Action | From contact page | From trial page |
|---|---|---|
| Connect | Pick a trial (default role: study_coordinator) | Pick a contact |
| Disconnect | Remove the trial link | Remove the contact link |
| Reconnect | Update role / delegation | Update role / delegation |
| Clear all | Remove all trial links | Remove all contact links |