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)

ColumnDescription
RoleThe contact’s trial role — maps to trialContactRole dictionary. Default when connecting: study_coordinator
DelegationWhether the contact has delegation authority (Yes / No)
VersionJunction version counter

From the trial page (trial → contact)

ColumnDescription
RoleSame trialContactRole value
DelegationSame delegation flag
VersionJunction version counter

Operations

ActionFrom contact pageFrom trial page
ConnectPick a trial (default role: study_coordinator)Pick a contact
DisconnectRemove the trial linkRemove the contact link
ReconnectUpdate role / delegationUpdate role / delegation
Clear allRemove all trial linksRemove all contact links

From each side

  • Use Contacts for the person record.
  • Use Trials for the governing study record.