Settings Module

The Settings module provides cross-cutting, admin-oriented preferences and configurations that are not owned by any specific business domain.

What belongs here

• View configurations: persisted table/column layouts and filters per entity.
• User preferences: per-user key/value preferences used by admin UI and tooling.

Active view selection

The currently active view for an entity is stored as a user preference:

• key: active_view.<entity>
• value: { viewConfigurationId: string | null }

Setting viewConfigurationId: null is an explicit instruction to bypass personal defaults and fall back to a system default view (when present).

What does not belong here

Domain configuration that changes a module’s behavior should remain in the owning module, even if it is “a setting”.

For example:

• Space settings (tenant/workspace behavior and policies) remain in the Space module.
• Only admin/UI preferences for Space should be expressed via this Settings module.