Organizational Unit

What It Models

A unit is a recognizable part of the association, such as a chapter or region. It combines a stable identity with local contact information, placement, organization relationships and the products used to collect dues.

Identity and Attributes

The permanent record identity survives a code change, closure or merge. Staff can maintain descriptive details and declared custom values independently of placement. Organization relationships carry dates, while financial settings hold pointers to Commerce and Accounting rather than their records.

Relationships

Each unit has one kind and an optional current parent. Programs may identify their administering unit, packages may be named by local dues extensions, and CRM organizations may be linked for different purposes. Membership owns those links and extensions, while the referenced services retain their own records.

Invariants

The invariant rows specify which writes validate identity, placement, links and dues references. A closed unit still accepts detail corrections; a merged unit rejects them, although its separate links and financial facets remain writable.

How It Is Stored and Shared

The structure service owns the unit and its facets. It validates custom values through Platform's shared definitions and includes them in single-record and query results. Unit and link versions retain attributed changes, and the workspace lifecycle exports or removes the corresponding data.

Open Design Questions

Reopening a closed unit and handling a merged source in current views remain product decisions. The merge returns finance, link and committee leftovers without assigning or tracking that follow-up work.