--- id: FAS-CRM-ENT-04 title: Affiliations and Roles acceptance feature: FEAT-CRM-ENT-04 product_area: crm module: entities revision: 1 status: proposed product_intent: proposed source_sha: services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f capabilities: - CAP-CRM-ENT-009 - CAP-CRM-ENT-010 - CAP-CRM-ENT-011 scenarios: - id: FAS-CRM-ENT-04-01 title: Record an employer and its responsibilities kind: behaviour exercises: - CAP-CRM-ENT-009 - CAP-CRM-ENT-010 - CAP-CRM-ENT-011 relies_on: - ATS-CRM-ENT-009-11 - ATS-CRM-ENT-010-01 - ATS-CRM-ENT-011-05 preconditions: The workspace has a default employer type and an eligible automatic role. steps: >- Set a person’s primary organization on the workspace day and read its relationship and responsibilities. expected: >- The saved relationship identifies the employer, effective dates and eligible responsibilities consistently. 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-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md action_evidence: provenance: proposed source: >- rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md assertion_evidence: provenance: proposed source: >- rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md - id: FAS-CRM-ENT-04-02 title: A future tie acquires responsibilities when it becomes current kind: interaction exercises: - CAP-CRM-ENT-009 - CAP-CRM-ENT-010 - CAP-CRM-ENT-011 relies_on: - ATS-CRM-ENT-009-07 - ATS-CRM-ENT-010-04 - ATS-CRM-ENT-011-06 preconditions: >- A future affiliation has a permitted automatic role and the workspace date can be controlled. steps: >- Inspect it before its start, reconcile on its start day and inspect the person and organization people list. expected: >- The tie becomes current and receives due responsibilities; the two record perspectives agree. 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-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md action_evidence: provenance: proposed source: >- rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md assertion_evidence: provenance: proposed source: >- rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md - id: FAS-CRM-ENT-04-03 title: Move an employer and preserve the former service period kind: lifecycle exercises: - CAP-CRM-ENT-009 - CAP-CRM-ENT-010 - CAP-CRM-ENT-011 relies_on: - ATS-CRM-ENT-009-16 - ATS-CRM-ENT-011-03 - ATS-CRM-ENT-010-01 preconditions: A person has a primary employer affiliation with open responsibilities. steps: >- Choose a new primary employer and end the earlier stay; inspect current and past views and the ended responsibility periods. expected: >- The new primary is current, the former stay remains as dated history and its open responsibilities end with that stay. 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-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md action_evidence: provenance: proposed source: >- rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md assertion_evidence: provenance: proposed source: >- rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md - id: FAS-CRM-ENT-04-04 title: Organization authority does not authorize a person’s relationship edit kind: permission exercises: - CAP-CRM-ENT-009 - CAP-CRM-ENT-010 - CAP-CRM-ENT-011 relies_on: - ATS-CRM-ENT-009-15 - ATS-CRM-ENT-010-06 - ATS-CRM-ENT-011-04 preconditions: A caller reads organizations but lacks contact update and bulk authority. steps: >- Attempt a person affiliation correction and a date reconciliation request; verify the person afterward. expected: >- Both unauthorized mutations are refused and the saved relationships and responsibilities remain intact. 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-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md action_evidence: provenance: proposed source: >- rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md assertion_evidence: provenance: proposed source: >- rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md - id: FAS-CRM-ENT-04-05 title: Concurrent first joins establish one first-contact assignment kind: regression exercises: - CAP-CRM-ENT-009 - CAP-CRM-ENT-010 - CAP-CRM-ENT-011 relies_on: - ATS-CRM-ENT-011-11 - ATS-CRM-ENT-009-04 - ATS-CRM-ENT-010-01 preconditions: >- An empty organization has an active first-contact role and several eligible people. steps: >- Join the people concurrently on the same workspace day; read each resulting relationship and role list. expected: >- The relationships are saved and exactly one person receives the first-contact responsibility. 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-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md action_evidence: provenance: proposed source: >- rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md assertion_evidence: provenance: proposed source: >- rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md evidence: - >- rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md --- # Affiliations and Roles: Feature Acceptance Suite ## What the Feature Must Do as a Whole The suite follows a person’s organizational relationship through creation, dated changes and responsibilities. It checks the relationship’s saved information alongside the calendar-driven outcomes that depend on it. Permission and regression cases exercise these outcomes with controlled grants and dates. ## Interactions Between Capabilities The future-relationship case joins calendar reconciliation with automatic role assignment. Each dependent outcome is checked after the relationship becomes current; the suite retains the capability scenarios that specify the separate date and role checks. ## 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. |