---
id: FAS-CRM-ENT-03
title: Contact Details and Communication Preferences acceptance
feature: FEAT-CRM-ENT-03
product_area: crm
module: entities
revision: 1
status: proposed
product_intent: proposed
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
capabilities:
  - CAP-CRM-ENT-005
  - CAP-CRM-ENT-006
  - CAP-CRM-ENT-007
scenarios:
  - id: FAS-CRM-ENT-03-01
    title: Inspect a person’s reachability and choices together
    kind: behaviour
    exercises:
      - CAP-CRM-ENT-005
      - CAP-CRM-ENT-006
      - CAP-CRM-ENT-007
    relies_on:
      - ATS-CRM-ENT-005-01
      - ATS-CRM-ENT-006-04
      - ATS-CRM-ENT-007-04
    preconditions: >-
      A person has owned contact points, one current organization link and
      recorded communication restrictions.
    steps: >-
      Open the person, inspect contact-point origins and read the communication
      choices.
    expected: >-
      Staff can distinguish personal and shared values while seeing the stored
      communication choices on the same person.
    negative: false
    data_needs: >-
      Run-owned people, organizations, classifications and definitions in an
      isolated workspace; controlled calendar or failure fixtures where the case
      requires them.
    bound_to: []
    provenance: proposed
    source: >-
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md
    action_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md
    assertion_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md
  - id: FAS-CRM-ENT-03-02
    title: A source change preserves personal choices and copied values
    kind: interaction
    exercises:
      - CAP-CRM-ENT-005
      - CAP-CRM-ENT-006
      - CAP-CRM-ENT-007
    relies_on:
      - ATS-CRM-ENT-006-04
      - ATS-CRM-ENT-006-08
      - ATS-CRM-ENT-007-04
    preconditions: >-
      A person has one linked address, one copied phone and explicit mail
      choices.
    steps: >-
      Correct the organization’s linked source and copied source; read the
      person and its version.
    expected: >-
      The link resolves the new source, the independent copy retains its
      snapshot and the person’s choices remain stored.
    negative: false
    data_needs: >-
      Run-owned people, organizations, classifications and definitions in an
      isolated workspace; controlled calendar or failure fixtures where the case
      requires them.
    bound_to: []
    provenance: proposed
    source: >-
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md
    action_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md
    assertion_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md
  - id: FAS-CRM-ENT-03-03
    title: Review a disconnected address and keep it as personal information
    kind: lifecycle
    exercises:
      - CAP-CRM-ENT-005
      - CAP-CRM-ENT-006
      - CAP-CRM-ENT-007
    relies_on:
      - ATS-CRM-ENT-006-05
      - ATS-CRM-ENT-006-07
      - ATS-CRM-ENT-007-04
    preconditions: A person has a shared address and a stored mail restriction.
    steps: >-
      Remove the organization’s source; inspect the retained information; keep
      its value and reread the person.
    expected: >-
      The disconnected value remains reviewable before repair; keeping it
      produces an owned detail without changing the stored restriction.
    negative: false
    data_needs: >-
      Run-owned people, organizations, classifications and definitions in an
      isolated workspace; controlled calendar or failure fixtures where the case
      requires them.
    bound_to: []
    provenance: proposed
    source: >-
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md
    action_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md
    assertion_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md
  - id: FAS-CRM-ENT-03-04
    title: A reader sees contact origins without repair authority
    kind: permission
    exercises:
      - CAP-CRM-ENT-005
      - CAP-CRM-ENT-006
      - CAP-CRM-ENT-007
    relies_on:
      - ATS-CRM-ENT-006-05
      - ATS-CRM-ENT-007-04
    preconditions: >-
      A person has a disconnected phone and a caller can read but cannot update
      contacts.
    steps: >-
      Open the person, inspect the origin and restriction notices and attempt a
      repair.
    expected: >-
      The notices are readable while the repair is unavailable or refused; the
      disconnected detail remains unchanged.
    negative: true
    data_needs: >-
      Run-owned people, organizations, classifications and definitions in an
      isolated workspace; controlled calendar or failure fixtures where the case
      requires them.
    bound_to: []
    provenance: proposed
    source: >-
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md
    action_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md
    assertion_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md
  - id: FAS-CRM-ENT-03-05
    title: Failed link removal retains all reachability information
    kind: regression
    exercises:
      - CAP-CRM-ENT-005
      - CAP-CRM-ENT-006
      - CAP-CRM-ENT-007
      - CAP-CRM-ENT-009
    relies_on:
      - ATS-CRM-ENT-006-09
      - ATS-CRM-ENT-007-01
      - ATS-CRM-ENT-005-03
    preconditions: >-
      A person has a linked phone, an affiliation and a communication
      preference.
    steps: >-
      Submit a save removing the affiliation but keeping its unresolved
      dependency, alongside a communication change; then reread.
    expected: >-
      The complete refusal preserves the link, affiliation and original
      preference.
    negative: true
    data_needs: >-
      Run-owned people, organizations, classifications and definitions in an
      isolated workspace; controlled calendar or failure fixtures where the case
      requires them.
    bound_to: []
    provenance: proposed
    source: >-
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md;
      rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md
    action_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md
    assertion_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md;
        rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md
evidence:
  - >-
    rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
    rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
    rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md
  - >-
    rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-005-keep-the-e-mails-phone-numbers-and-addresses-of-contacts-and.md;
    rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-006-share-an-organization-s-addresses-and-phone-numbers-with-its.md;
    rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-007-record-how-a-person-wants-to-be-contacted.md;
    rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md
---

# Contact Details and Communication Preferences: Feature Acceptance Suite

## What the Feature Must Do as a Whole

The suite examines contact points and communication choices together on an affiliated person. It follows the record through direct edits, source changes and disconnection, then checks the information that readers receive. Permission and regression cases cover the same record rather than a separate settings fixture.

## Interactions Between Capabilities

The source-change case checks the dependent person after the organization’s information changes. The suite distinguishes the source-backed values from the person’s owned values and communication choices through the detailed scenarios it cites.

## Regression Record

| Revision | Change | Scenario | Why |
|---|---|---|---|
| 1 | initial | all | Establish the feature acceptance suite from the planning and design contracts. |
| 2 | continuation examination | all | Rewrite the suite explanation, verify its evidence and restore source-backed bindings where available. |