CRM Settings
What It Is
CRM Settings holds workspace defaults used across contact and organization work. It includes default presentation assignments, the default affiliation type, and the date-reconciliation watermark. These are workspace-level choices and processing state, not values describing one person or one organization. Their scope lets staff share a baseline while type-specific presentation can override it.
The stored settings record is versioned, but its sections have different reading and updating authority. A caller receives only the sections it may inspect. Platform owns the definitions referenced by presentation settings; CRM owns the assignments and effective resolution behavior.
Why It Exists
Our reading is that shared defaults prevent every coordinator or integration from making the same configuration choice independently. Workspace-wide presentation can serve the common case while classifications customize exceptions. A default affiliation type makes the Organization command usable without inventing a relationship category in each request, and a settled-day marker lets boundary processing resume reliably after missed work.
What It Is Not
CRM Settings is not an organization record, a complete catalogue, or a Platform form or layout definition. It selects existing definitions and types rather than owning their content. The reconciliation watermark is processing state, not the effective date of every affiliation. Reading contact records or effective presentation does not give a staff member unrestricted authority over all settings sections.
What It Controls
Presentation defaults supply the fallback after a type leaves a particular form or layout slot unset. Each slot resolves independently, including distinctions between create and edit. An unconfigured slot remains unconfigured rather than producing an invented definition. The default affiliation type supplies supported Organization-command creation when no explicit type is given.
The watermark identifies the last settled reconciliation day so later runs can include missed boundaries and avoid repeating completed effects. Settings updates preserve unnamed sections and require authority for every section named. A stale settings version prevents overwriting another administrator's changes, and forbidden sections are absent on reads rather than represented as empty defaults.
How It Is Used
The CRM Administrator chooses baseline forms, layouts, and relationship defaults. The CRM Editor and CRM Reader retrieve effective definitions for everyday record work under their record authority. The CRM System uses settled-date state during Keep dated relationships current. Good use distinguishes a type override from a workspace default and an authorized unset value from information the caller cannot read.
Example
An association chooses a default contact page layout and the Other affiliation type for ordinary Organization commands. A Member contact type overrides its edit form but leaves the page-layout slot empty, so staff receive the workspace layout. Another administrator concurrently changes organization defaults; a stale combined update is refused, preserving the newer settings rather than silently writing over them.
How It Relates
Contact Type and Organization Type hold presentation overrides that resolve ahead of CRM Settings. Affiliation Type supplies the default relationship vocabulary. Platform metadata owns the selected forms and layouts, and Platform security evaluates section authority. Affiliation date reconciliation uses the watermark, but deployment configuration separately controls whether scheduled processing runs; the settings record does not imply an enabled scheduler.