--- id: CON-MBR-STR-002 name: Organizational Unit feature: FEAT-MBR-STR-02 product_area: membership module: structure revision: 1 status: draft product_intent: proposed implementation_evidence: observed source_sha: services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f definition: >- An organizational unit is the continuing record of one chapter, section, region or other part of the association, with local details and relationships. owned_by: MOD-MBR-STR synonyms: - chapter - section - association unit not_to_be_confused_with: - CRM organization - Program classification - Member affiliation facets: - name: Identity and presentation meaning: A workspace-unique code and display name identify the unit to staff and integrations. used_for: 'Recognizing records across lists, searches and loads.' - name: Local contact information meaning: 'Unit-owned contact points, mailing details and coordinates describe how the unit can be reached.' used_for: Maintaining local operational information. - name: Member-facing choices meaning: Visibility and welcome-template selections record intended presentation and communication choices. used_for: 'Preparing member-facing behavior, with welcome sending still absent.' - name: Customer information meaning: Configured custom values extend the unit’s ordinary details. used_for: Recording association-specific information using unit definitions. - name: Organization relationships meaning: 'Effective links connect the unit to CRM bodies with legal, operating or financial purposes.' used_for: Explaining which organizations stand behind the unit. - name: Relationship purposes meaning: Standard and customer-added kinds classify organization links. used_for: Distinguishing the meaning of each organization connection. - name: Settlement settings meaning: >- An ordering-profile pointer expresses local settlement choice, alongside an unused default dues reference. used_for: Supplying local finance configuration. - name: Local dues offerings meaning: Chapter-dues products in Accounting have unit-specific Membership extensions. used_for: Offering package-specific or catch-all dues. - name: Standing meaning: 'Active, inactive and merged distinguish structural availability and retained history.' used_for: Assessing eligibility for incoming children and affiliations. relationships: - to: CON-MBR-STR-001 statement: A unit occupies a classified place in the organizational hierarchy. provenance: observed source: 'services-membership:modules/structure/db/organizational-units.table.ts:organizationalUnits' - to: CON-MBR-STR-004 statement: Dues extensions describe a package-specific offering or the unit’s catch-all context. provenance: observed source: >- services-membership:modules/structure/db/organizational-unit-dues-products.table.ts:organizationalUnitDuesProducts - to: CON-MBR-STR-003 statement: A program can record the unit responsible for administering it. provenance: observed source: 'services-membership:modules/configuration/db/programs.table.ts:programs' lifecycle: - state: active meaning: Available for ordinary use under its owning record’s activity controls. how_it_changes: Deactivation changes availability; a unit can also be combined into a survivor. - state: inactive meaning: 'Retained outside ordinary active use, with record-specific consumer restrictions.' how_it_changes: >- Kinds and configuration can reactivate through their ordinary saves; units have no reactivation operation. - state: merged meaning: The unit records absorption into its survivor while preserving identity. how_it_changes: Structural mutations are refused; organization and finance operations remain separate. acted_on_by: - CAP-MBR-STR-002 - CAP-MBR-STR-003 - CAP-MBR-STR-004 - CAP-MBR-STR-005 - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 - CAP-MBR-STR-020 visible_to: - ACT-MBR-001 - ACT-MBR-002 - ACT-MBR-005 evidence: - >- services-membership: Verified material includes the units, links, relationship kinds, financial settings and dues products tables and persistence, the Accounting products port. - >- services-membership: Verified material includes structure and packages-as-products tests and acceptance journeys. supersedes: - react-console acceptance inventory CAP-MBR-STR-002 - react-console acceptance inventory CAP-MBR-STR-003 - react-console acceptance inventory CAP-MBR-STR-009 - react-console acceptance inventory CAP-MBR-STR-010 - react-console acceptance inventory CAP-MBR-STR-011 --- # Organizational Unit ## What It Is An organizational unit is a recognizable part of the association: a particular chapter, region or section rather than the category shared by many of them. Staff create its record when they build the structure. The unit has a permanent internal identity and a readable code unique within the customer’s workspace. Its name and local details can change while other records continue to refer to the same unit. The record brings together local information with the structural identity that memberships and connected applications use. It carries contact and mailing details, optional geographic coordinates and customer-defined values. Organization relationships and finance settings remain associated information with their own operations. A chapter can therefore keep its structural continuity while its incorporated body, address or selling arrangements change. ## What It Is Not The unit is separate from a CRM organization. A chapter might operate as an internal division or have a dated relationship with an incorporated body. Neither case makes the structural unit interchangeable with that CRM record. It is also separate from a membership program or an affiliation: those describe membership context and a member’s dated connection to the unit. ## How It Is Used Administrators create and maintain units as part of association setup, then use placement and combination work to keep them aligned with reality. Readers locate units by code or name and inspect their branch. Staff maintain local details without attempting to change structural fields through the same replacement. A version conflict requires reconciliation with a newer edit. Finance staff also need to distinguish the unit’s own settlement configuration from product information maintained in Accounting. ## Its Facets **Identity and presentation.** Codes make units recognizable to imports and staff. **Local contact information.** Contact points belong to the unit rather than automatically resolving from a related organization. **Member-facing choices.** Visibility is stored alongside a welcome-template selection whose sender is not implemented. **Customer information.** Custom values use definitions appropriate to units. **Organization relationships.** Dated connections preserve legal and operational context. **Relationship purposes.** Standard purposes and additional customer categories explain those connections. **Settlement settings.** A local ordering-profile choice can override inherited finance context. **Local dues offerings.** Membership adds unit and package context to Accounting’s chapter-dues products. **Standing.** Closure preserves identity; combination records a survivor and restricts ordinary structural changes. ## How It Relates The hierarchy arranges the unit and records its parentage. Programs can identify an owning unit or use unit categories in membership requirements. Package-specific dues offerings refer to membership packages. CRM owns related organizations, Accounting owns the shared product information and Commerce owns ordering profiles. Membership retains the references and local context needed for those relationships. ## What It Could Become The product should decide whether closed units can reopen under their existing identity. It should also establish how organization references are verified and what finance changes remain appropriate after a merge. Member-facing welcome delivery and geographic suggestions are possible future uses of retained settings, but storing those choices alone does not establish those experiences.