Documentation / Connections / Organizations
Contacts
How organization records connect to contact records in TrialStack.
This is a dual-bound connection. The same junction links an organization to a contact and a contact to an organization. See Contact → Organization for the reverse direction — both sides show identical junction fields.
Why it matters
- a team needs named stakeholders under an organization with explicit roles and department
- reviewers need person-level context around organization work and source traceability
- organization changes affect which contacts belong where
Junction fields
| Column | Description |
|---|---|
| Status | The contact’s status within the organization — maps to orgContactStatus dictionary |
| Role | The contact’s organizational role — maps to orgContactRole dictionary |
| Department | The department or unit within the organization |
| Version | Junction version counter |
| Source | How the link was created — Qualification (auto-derived) or Manual |
Operations
| Action | From organization page | From contact page |
|---|---|---|
| Connect | Pick a contact | Pick an organization |
| Disconnect | Remove the contact link | Remove the organization link |
| Reconnect | Update status / role / department | Update status / role / department |
| Clear all | Remove all contact links | Remove all organization links |
From each side
- Use Organizations for the higher-level entity.
- Use Contacts for the stakeholder record.