Sites

This is a dual-bound connection. The same junction links a contact to a site and a site to a contact. New connections must be created from the site page — the contact page shows the link but does not offer a connect action.

Why it matters

• a person needs site-level operational context and defined roles
• reviewers need to know which site a stakeholder belongs to and their responsibility
• site-specific work depends on named contacts staying attached with correct status

Dual-bound relationship

flowchart LR
  C[Contact] -. "status · roles · job title · version" .-> S[Site]
  S -- "status · roles · department · version" --> C

The dashed arrow indicates that connect is blocked from the contact side. Use the site page to create new links.

Junction fields

From the contact page (contact → site)

Column	Description
Status	The contact’s status at this site — maps to siteContactStatus dictionary
Roles	One or more roles the contact holds at this site (multiselect array)
Job Title	The contact’s job title at this specific site
Version	Junction version counter

From the site page (site → contact)

Column	Description
Status	Same siteContactStatus value
Roles	Same multiselect roles array
Department	The department within the site
Version	Junction version counter

Operations

Action	From contact page	From site page
Connect	Blocked — “connect from the site side”	Pick a contact to link
Disconnect	Remove the site link	Remove the contact link
Reconnect	Update status / roles / title	Update status / roles / department
Clear all	Remove all site links	Remove all contact links

From each side

• Use Contacts for the stakeholder record.
• Use Sites for the execution-location context.