Organizations

This is a dual-bound connection. The same junction links a contact to an organization and an organization to a contact. Both directions share the same underlying record.

Why it matters

• a stakeholder must be linked to the correct organization with an explicit role
• reviewers need organization context around a person — including department and status
• organizational changes affect contact ownership or role context
• the junction tracks source (manual vs. qualification-derived) for audit traceability

Dual-bound relationship

flowchart LR
  C[Contact] -- "status · role · department · source · version" --> O[Organization]
  O -- "status · role · department · source · version" --> C

Junction fields

Both directions show the same columns:

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 from competency matching) or Manual

Operations

Action	From contact page	From organization page
Connect	Pick an organization	Pick a contact
Disconnect	Remove the organization link	Remove the contact link
Reconnect	Update status / role / department	Update status / role / department
Clear all	Remove all organization links	Remove all contact links

From each side

• Use Contacts for the person record.
• Use Organizations for the higher-level operating entity.