Rhythm 2.0 Specifications

Appearance

CON-MBR-STR-002Organizational Unit

Markdown

CON-MBR-STR-002

Organizational Unit

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

Planning

Feature
FEAT-MBR-STR-02
Owned by
MOD-MBR-STR
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
Not to be confused with
CRM organization, Program classification, Member affiliation

Design

Specified by
DOM-MBR-STR-002

KindKey conceptProduct areaMembershipModuleOrganizational Structure, Membership Configuration and TermsRevision1

Read atservices-membership 5994c270react-console baf6dae3

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.

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Definition
An organizational unit is the continuing record of one chapter, section, region or other part of the association, with local details and relationships.
Synonyms
chaptersectionassociation unit

Relationships

ToStatementProvenance
CON-MBR-STR-001A unit occupies a classified place in the organizational hierarchy.observed
services-membership:modules/structure/db/organizational-units.table.ts:organizationalUnits
CON-MBR-STR-004Dues extensions describe a package-specific offering or the unit’s catch-all context.observed
services-membership:modules/structure/db/organizational-unit-dues-products.table.ts:organizationalUnitDuesProducts
CON-MBR-STR-003A program can record the unit responsible for administering it.observed
services-membership:modules/configuration/db/programs.table.ts:programs

Lifecycle

StateMeaningHow it changes
activeAvailable for ordinary use under its owning record’s activity controls.Deactivation changes availability; a unit can also be combined into a survivor.
inactiveRetained outside ordinary active use, with record-specific consumer restrictions.Kinds and configuration can reactivate through their ordinary saves; units have no reactivation operation.
mergedThe unit records absorption into its survivor while preserving identity.Structural mutations are refused; organization and finance operations remain separate.

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software