---
id: SCR-PFM-ELG-011
title: Attention settings and personal preferences
route: >-
  not built; proposed under Settings › Attention for the shared settings and in
  the attention list for the personal panel
surface: console
product_area: platform
module: eligibility
revision: 1
status: draft
design_intent: proposed
implementation_evidence: not-implemented
inference: []
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
purpose: >-
  Provide the proposed administrator configuration and personal hiding surfaces
  for attention settings already exposed by the service.
supports:
  - CAP-PFM-ELG-020
  - CAP-PFM-ELG-019
permission: >-
  platform.attention.read to see the catalogue; platform.attention.manage to
  read and change a kind's settings; platform.attention.use for personal
  preferences
entry_from:
  - Proposed shared settings navigation
  - 'SCR-PFM-ELG-002: proposed personal settings entry'
exits_to:
  - SCR-PFM-ELG-002
displays:
  - field: >-
      Proposed catalogue of kinds with class, category, owner, enablement and
      sweep freshness
    source: listAttentionDefinitions (DOM-PFM-ELG-005)
  - field: >-
      Proposed per-kind configuration within declared schema and lifecycle
      bounds
    source: getAttentionDefinitionSettings
  - field: Proposed personal hidden-kind controls with required kinds fixed visible
    source: getMyAttentionPreferences
actions:
  - label: Save kind settings
    operation_id: putAttentionDefinitionSettings
    permission: platform.attention.manage
    confirm: true
  - label: Save my preferences
    operation_id: putMyAttentionPreferences
    permission: platform.attention.use
    confirm: false
states:
  - empty
  - loading
  - error
  - read-only
validation:
  - BR-CAP-PFM-ELG-020-01
  - BR-CAP-PFM-ELG-020-02
  - BR-CAP-PFM-ELG-020-03
  - BR-CAP-PFM-ELG-020-04
  - BR-CAP-PFM-ELG-020-05
  - BR-CAP-PFM-ELG-020-06
  - BR-CAP-PFM-ELG-020-07
  - BR-CAP-PFM-ELG-020-09
  - BR-CAP-PFM-ELG-019-07
patterns:
  - Proposed v0 design under the UI-change approval rule
  - Proposed ConfigurationManager catalogue
  - Proposed example-backed wording preview
  - Proposed stale-version Reload handling
evidence:
  - >-
    services-platform at ad3f6a6: modules/attention/aws/api/attention.routes.ts,
    attention.schemas.ts; services/persistence/settings.ts, preferences.ts;
    docs/milestones/PLAT-M16-attention-follow-up-and-tuning.md.
  - 'react-console at baf6dae: no settings screen or preference panel exists.'
controls: [TC-AVL-004, TC-AVL-005, TC-AZ-001, TC-AZ-002, TC-AZ-003, TC-AZ-004, TC-DAT-001, TC-DAT-002, TC-DAT-003, TC-IAM-001, TC-IAM-002, TC-IAM-004, TC-IAM-005, TC-LOG-002, TC-LOG-003, TC-LOG-004, TC-LOG-005, TC-MON-001, TC-PI-001, TC-PI-002, TC-PI-003, TC-PI-004, TC-PI-005, TC-PRV-001, TC-PRV-002, TC-PRV-004, TC-TEN-001, TC-TEN-002, TC-TEN-003, TC-TEN-004, TC-VEN-001, TC-VEN-002, TC-VEN-003]
---
# Attention settings and personal preferences

## What the Screen Is For

These settings surfaces are proposed: the console currently has neither the shared kind-settings page nor personal preference panel.

## What It Shows and Lets People Do

The proposed catalogue opens kind settings and previews wording against declared examples. The personal panel permits hiding advisory and opportunity kinds while keeping required kinds visible. The approved target enables reminders only after administrator action and leaves digest and quiet-hour preferences to Notifications; current service behavior differs.

## States and Errors

The intended shared read-only mode follows management authority. Stale writes need reload feedback and invalid settings need field-level refusal messages. These interactions are design requirements rather than observations of a built screen.

## Patterns It Must Respect

A new v0 design and UI approval are required before building this surface. Proposed catalogue, preview and version-conflict components remain explicitly separate from the implementation evidence for the existing endpoints.