Skip to main content

Notification History

Business Purpose​

Give recipients and operators traceable views of message content, status, attempts, processing stages and read state.

Actors​

Employees, notification administrators, support operators, auditors, privacy owners and security reviewers.

Business Flow​

The extracted service stores rendered messages, append-only delivery attempts and audit entries across receipt, resolution, suppression, delivery, retry, processing and read stages. The legacy employee path combines current and older notification tables into one newest-first view and updates read state in the owning table.

Responsibilities​

Employees use read state as a personal inbox aid. Support correlates identifiers rather than treating one status as the full story. Data owners define retention and access. Administrators preserve records required for investigation.

Business Rules​

Delivery attempts and processing audit entries are added rather than overwritten. Employee inbox queries are scoped to the authenticated active user. Read-all updates both legacy data sets; extracted-service read operations update the message and add a read audit entry.

Integrations​

History is consumed by employee inboxes, an admin notification center and operations dashboards. Processed-event records support idempotency and investigation.

Limitations​

The two histories have different schemas and read operations. No reviewed export, archival, legal hold, purge or user-visible delivery-attempt view exists. Text categorization in the legacy inbox is heuristic.

Requires Confirmation​

Confirm retention periods, subject-access and erasure handling, audit consumers, evidence requirements and whether legacy and extracted histories will be consolidated.

Source References​

  • microservices/src/notification-service/Domain/NotificationEntities.cs
  • microservices/src/notification-service/Application/NotificationDispatcher.cs
  • microservices/src/notification-service/Api/NotificationEndpoints.cs
  • Controllers/NotificationsController.cs

See Also​

Keywords​

History, audit, delivery attempt, read state, processed event.

Revision Information​

Draft; reviewed 2026-07-21; next quarterly review 2026-10-21.