Region

What It Is

A region gives staff a name for a group of people and organizations they work with together. An association might use regions for its chapters, a service organization for its territories, or a customer for a broad residual area outside its usual coverage. The grouping belongs to the customer’s workspace and supplies a common reference for records and geographic policy.

An administrator establishes the catalogue in CRM configuration. Each entry has a stable identifier, a name, an optional description and an active setting. The identifier allows a rule or record to continue referring to the same entry after its name changes. Integration work can supply an external identifier alongside that regional identity. The catalogue contains definitions rather than copies of the people assigned to them.

What It Is Not

A regional definition does not itself describe a geographic boundary. The assignment policy provides that coverage and can use several geographic rules for the same target. A chapter may also have an organization record, but that record and its regional grouping have separate purposes. Country, state and postal values are geographic inputs, while address types describe which part of a record supplies an address.

How It Is Used

Administrators maintain the catalogue, readers inspect it and integrations can load definitions from files. Coordinators encounter regional references while working with people and organizations. A useful catalogue uses names staff can distinguish and descriptions where the distinction needs explanation. The Regions tab shows the available definitions and permits authorized editing through a drawer.

Retiring an entry preserves the references already held by records and policy. Removal is possible only after dependencies are gone. The current implementation does not make an inactive policy target stop receiving automatic placements. Staff therefore need to consider the policy as well as the catalogue when closing a regional group. The acceptance tests also record shortcomings in the display of existing inactive choices on contact screens.

Its Facets

Stable identifier. This reference survives ordinary edits and accepts the legacy regional character grammar. It supports both staff-created definitions and integration inputs.

Display information. The name is required; the description provides optional context. Naming alone does not constrain which geographic rules can target the region.

Availability. Active and inactive distinguish ordinary use from retirement. Existing references remain intact when availability changes.

Protection and integration key. Locks restrict deletion or both editing and deletion. Their current treatment as ordinary writable fields differs from the recorded policy for audited lock actions.

Dependencies. Regional references connect contacts, organizations and rules to the definition. A dependency prevents deletion and supplies the category named in the refusal.

Metadata and export. Platform metadata makes the regional object available for record references, while workspace export includes the catalogue, including inactive definitions.

How It Relates

The assignment policy chooses target regions, and regional placement records the resulting choice on a person or organization. A recalculation changes eligible placements under the saved policy without recreating the catalogue. Contacts and organizations own their regional references; Regions owns the definitions those references identify.

What It Could Become

The product should settle whether an inactive target remains eligible for automatic assignment and provide a retirement experience consistent with that decision. The product should also apply the recorded audited lock policy to regional definitions. Custom fields are excluded by the recorded CRM decision, so adding them would require a new product choice.