Share organization contact points with affiliated people
Purpose
A person may use a member firm's address or telephone rather than maintain an independent work contact point. This capability keeps the source relationship explicit, lets a live value follow the organization, and gives staff a recovery process when removed source information can no longer be treated as reliably shared.
How It Works
Addresses and phones distinguish owned values, intentional copies, live links, and disconnected values. A link names an affiliation and a source belonging to that affiliation's organization. New or redirected links need an affiliation effective today. The service prevents a linked row from carrying a competing value; reads resolve the current organization source without saving the person when the source changes.
An affiliation that is no longer effective leaves its link unresolved. Removing the organization source has a different effect: in the same transaction, affected contact entries become disconnected, retain the last value and source provenance, require verification, and advance their contacts' versions. Clients cannot manufacture that server-recorded state.
With the current contact version, staff can verify a disconnected value as independently owned, relink it to one eligible source, or remove it. A deliberate independent copy also stops following later source changes. Removing an affiliation requires dealing with all its supplied links in the same save, while ending it can retain unresolved links.
Default mappings fill empty destination types on eligible affiliations and respect the saved selection. An omitted selection and an explicitly empty selection differ. Future choices wait for the start, and changing type defaults does not rewrite existing people.
Example
Ruth's work address links to Harbor Engineering's main address through her current employer affiliation. A move updates the value Ruth sees without a contact edit. Later the firm removes the source address. Ruth retains the last address with a disconnected state and a newer record version. A coordinator reads that version and relinks the work entry to the firm's billing address, resolving the uncertainty without losing the explanation of the old source's removal.
Ruth's coordinator reads her latest version after the firm's source removal. An editor opened before that removal is stale because disconnection advanced the affected contact. She then chooses one recovery, verifies its returned state and reads the record again: verification leaves an independent owned value; relinking uses a currently effective affiliation and one eligible source; removal leaves no element. Merely sending back the disconnected row does not erase its server provenance. If Ruth's affiliation ended instead of the source being removed, the resulting unresolved link is a different starting state and cannot be treated as a disconnected element requiring the same recovery action.
Why It Works This Way
Our reading is that live resolution prevents synchronization copies from drifting while preserving which organization supplies the detail. Restricting new links to effective affiliations prevents a future or former employer from becoming a current source. Refusing competing linked values keeps the link from meaning two things at once.
Disconnection differs from a deliberate copy because source removal is evidence that reliability needs review, not evidence that the person wants an independent address. Preserving the last value supports investigation without silently treating it as confirmed. Versioned recovery prevents a coordinator from resolving an entry that someone else already changed. Empty-destination defaults avoid overwriting independent information, and nonretroactive configuration respects decisions already made on existing contacts. Handling link removal together with affiliation removal prevents dangling explanations of source ownership.
Relationships
Maintain a person’s organizational relationships owns the affiliation that authorizes sharing. Configure affiliation types and contact roles supplies default mappings, and Keep dated relationships current applies pending choices on eligible starts. Maintain reliable contact points owns value validation. Platform metadata supplies display; organization and contact persistence coordinate source-removal changes transactionally rather than relying on a later synchronization copy.