---
id: SCR-PFM-NOT-004
title: Notification chain sheet
route: /console/{tenantId}/settings/notifications (side sheet over History); also over /hq/notifications
surface: console
product_area: platform
module: notifications
revision: 1
status: draft
design_intent: confirmed
origin: PLAT-M23 plan approved 2026-10-21 18:05 ET (opening a row shows the request, instance, deliveries
  and the reason for each unused channel), services-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md#3.
  How it works for the user
implementation_evidence: observed
inference: []
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
purpose: Trace a History row through its request, recipient notices and channel event records.
supports:
- JNY-PFM-NOT-003
- CAP-PFM-NOT-011
- CAP-PFM-NOT-010
permission: platform.notifications.manage
entry_from:
- A workspace History row
- An HQ History row
exits_to:
- SCR-PFM-NOT-003
- SCR-PFM-NOT-005
displays:
- field: Request definition, submitting actor, timing, outcome, validation problems and recipient count
  source: getNotificationRequest
- field: Recipient identity, notice progress, language and audience explanation
  source: getNotificationRequest instances and their channel resolution
- field: Channel outcomes, non-delivery reasons and expandable provider event history
  source: getNotificationRequest instance deliveries and their loaded events
actions:
- label: Expand or collapse the loaded event history
  operation_id: 'none: local expansion of loaded events'
  permission: platform.notifications.manage
  confirm: false
- label: Reload the request chain after a failed read
  operation_id: getNotificationRequest
  permission: platform.notifications.manage
  confirm: false
states:
- loading
- error
- read-only
validation:
- BR-CAP-PFM-NOT-011-04
- BR-CAP-PFM-NOT-011-08
- BR-CAP-PFM-NOT-010-04
patterns:
- Sheet presents request and notice facts in definition lists
- Expandable channel rows reveal already loaded events
- Alert offers another load attempt
component: components/notifications/notification-chain-sheet.tsx (NotificationChainSheet)
evidence:
- 'react-console at baf6dae3: components/notifications/notification-chain-sheet.tsx; acceptance/notifications/reports/defects/notifications.md
  (DEF-NT-0015).'
controls: [TC-AVL-001, TC-AVL-004, TC-AVL-005, TC-AZ-001, TC-AZ-002, TC-AZ-003, TC-AZ-004, TC-AZ-005, TC-DAT-001, TC-DAT-002, TC-DAT-003, TC-IAM-001, TC-IAM-002, TC-IAM-003, TC-IAM-004, TC-IAM-005, TC-LOG-001, TC-LOG-002, TC-LOG-003, TC-LOG-005, TC-MON-001, TC-MON-002, TC-PI-001, TC-PI-002, TC-PI-003, TC-PI-004, TC-PI-005, TC-PRV-001, TC-PRV-002, TC-TEN-001, TC-TEN-002, TC-TEN-003, TC-VEN-001, TC-VEN-002, TC-VEN-003]
---
# Notification chain sheet

## What the Screen Is For

Trace a History row through its request, recipient notices and channel event records.

## What It Shows and Lets People Do

The sheet loads the request and its associated notices through the workspace management API, including when opened from HQ. Event expansion is local presentation. The HQ entry therefore does not imply that the sheet uses an HQ read operation.

## States and Errors

The screen distinguishes pending content, an empty result where applicable, and failed reads. Available retry controls repeat reading without changing stored work. History surfaces remain read-only.

## Patterns It Must Respect

Sheet presents request and notice facts in definition lists. Expandable channel rows reveal already loaded events. Alert offers another load attempt.