---
id: SCR-PFM-NOT-005
title: Rhythm HQ notification History
route: /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 (HQ, Notifications, History shows any tenant's history
  for support) and PLAT-M23-S04 (reads behind an active staff access grant), 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: Help authorized Rhythm staff inspect a selected customer workspace’s notification history under
  an access grant.
supports:
- JNY-PFM-NOT-004
- CAP-PFM-NOT-012
permission: hq.notifications.read and an active staff access grant into the chosen workspace
entry_from:
- Notifications in HQ navigation
exits_to:
- SCR-PFM-NOT-004
- The HQ workspace area for access-grant setup
displays:
- field: Workspace search results and the current selection
  source: HQ workspace list (Security)
- field: The selected workspace’s notice and request history
  source: listHqTenantNotificationHistory; listHqTenantNotificationRequests
actions:
- label: Select a workspace to inspect
  operation_id: listHqTenantNotificationHistory
  permission: hq.notifications.read
  confirm: false
- label: Filter workspace history by recipient identifier, definition, category, channel, outcome and
    date
  operation_id: listHqTenantNotificationHistory
  permission: hq.notifications.read
  confirm: false
- label: Open the selected request chain
  operation_id: getNotificationRequest
  permission: platform.notifications.manage
  confirm: false
states:
- empty
- loading
- error
- read-only
validation:
- BR-CAP-PFM-NOT-012-01
- BR-CAP-PFM-NOT-012-02
- BR-CAP-PFM-NOT-012-06
patterns:
- StaffOnly and the HQ permission check protect entry
- PageLayout and PageHeader introduce support history
- ListSearch and pressed selection buttons choose a workspace
- NotificationHistoryScreen is embedded without a repeated heading
- Alert directs staff to workspace access setup when a grant is missing
component: components/console/hq/notifications-history.tsx (NotificationsHistory) with components/notifications/notification-history-screen.tsx
  (source hq)
evidence:
- 'react-console at baf6dae3: app/(console)/hq/notifications/page.tsx; components/console/hq/notifications-history.tsx;
  components/notifications/notification-history-screen.tsx; lib/hq/permissions.ts.'
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-IAM-006, TC-LOG-001, TC-LOG-002, TC-LOG-003, TC-LOG-004, TC-LOG-005, TC-MON-001, TC-MON-002, TC-PI-001, TC-PI-002, 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]
---
# Rhythm HQ notification History

## What the Screen Is For

Help authorized Rhythm staff inspect a selected customer workspace’s notification history under an access grant.

## What It Shows and Lets People Do

The HQ list operations require staff authority and a valid workspace grant. Opening a row enters the shared diagnostic sheet, whose current implementation uses workspace management operations. The product treatment of this authority difference remains unresolved.

## 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

StaffOnly and the HQ permission check protect entry. PageLayout and PageHeader introduce support history. ListSearch and pressed selection buttons choose a workspace. NotificationHistoryScreen is embedded without a repeated heading. Alert directs staff to workspace access setup when a grant is missing.