---
id: ADR-PFM-NOT-002
title: Staff Notices and Association E-mail Are Separate Models
product_area: platform
module: notifications
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: Staff notices and association mail retain separate records and authoring models; future staff
  e-mail uses Communications through caller-rendered requests.
constrains:
- DOM-PFM-NOT-003
- DOM-PFM-NOT-004
- DOM-PFM-NOT-005
- SVC-PFM-NOT-notifications
- SVC-PFM-NOT-communications
origin: 'The approved Platform Notifications architecture (Andrew 2026-10-21 17:15 ET) as recorded in
  services-platform:docs/communications/architecture.md#22. Staff notifications: designed in the Platform
  Notifications architecture (2026-10-21)'
alternatives:
- option: One message model for staff and members
  why_not: Combining the models would mix personal inbox choices with address-based consent and suppression.
- option: Notifications sends e-mail directly through the provider
  why_not: Direct notification e-mail would rebuild sender protection, rate control and provider feedback.
consequences:
- Application declarations supply staff wording, while association publications supply member-mail wording.
- The proposed staff e-mail connection uses transactional purposes and retains outcomes on the staff delivery.
- Staff channel choices belong to Notifications; business modules retain member consent decisions.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: docs/communications/architecture.md §2 and §22; docs/proposals/notifications/11-email.md
  §4.'
---
# Staff Notices and Association E-mail Are Separate Models

## Context

Association member mail and staff inbox notices address different people and preserve different kinds of state.

## Decision

Staff notices and association mail retain separate records and authoring models; future staff e-mail uses Communications through caller-rendered requests.

## Alternatives Considered

Combining the models would mix personal inbox choices with address-based consent and suppression. Direct notification e-mail would rebuild sender protection, rate control and provider feedback.

## Consequences

Application declarations supply staff wording, while association publications supply member-mail wording. The proposed staff e-mail connection uses transactional purposes and retains outcomes on the staff delivery. Staff channel choices belong to Notifications; business modules retain member consent decisions.