---
id: ADR-PFM-NOT-013
title: Preferences and Workspace Settings Are Stored but Not Applied Yet
product_area: platform
module: notifications
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: Preferences, settings, wording, quiet periods, digests, identities and text accounting remain
  dormant persistence in the current release.
constrains:
- DOM-PFM-NOT-003
- SVC-PFM-NOT-notifications
- STATE-PFM-NOT-006
- STATE-PFM-NOT-007
- STATE-PFM-NOT-008
origin: PLAT-M23 assumption A7 approved through D-13 (preferences are PLAT-M25), services-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md#4.
  Assumptions
alternatives:
- option: Leave the tables until their milestone
  why_not: Waiting to create every table would require later schema work around populated notification
    records.
- option: Apply them now
  why_not: Applying future settings now would expand behavior beyond the approved core release.
consequences:
- The declared definition-disabled outcome has no processing writer.
- Personal explanations describe configuration as a later-release capability.
- Activation needs an approved plan and orchestration proof beyond persistence guards.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: modules/notifications/services/persistence/{preferences,channel-settings,definition-settings,template-overrides,user-settings,identities,sms-usages,digests}.ts;
  orchestration/orchestrate-request.ts header.'
---
# Preferences and Workspace Settings Are Stored but Not Applied Yet

## Context

The core release stores future delivery configuration without activating it for current notices.

## Decision

Preferences, settings, wording, quiet periods, digests, identities and text accounting remain dormant persistence in the current release.

## Alternatives Considered

Waiting to create every table would require later schema work around populated notification records. Applying future settings now would expand behavior beyond the approved core release.

## Consequences

The declared definition-disabled outcome has no processing writer. Personal explanations describe configuration as a later-release capability. Activation needs an approved plan and orchestration proof beyond persistence guards.