Overview
Manage the communication catalogue, per-profile channel preferences, do-not-contact/paused state, purpose consent, lawful-basis/evidence data, and consent lifecycle.
Problem
A delivery channel being technically available does not mean every customer message is permitted or preferred.
Solution
Use AccessGuard communication state as the policy gate before notification delivery and publish preference/consent changes for downstream consumers.
How it works
AccessGuard stores preferred channels/locales, channel enablement, consent status/evidence/expiry and uses communication authorization logic before external delivery.
Who is this for
Expected outcomes
- Consistent communication decisions across applications
- Auditable customer preference and consent evidence
Key metrics
Security impact
- Communication preferences, consent evidence, purpose/channel identifiers, timestamps, source and audit metadata · PII: yes
Compliance
- Purpose/channel catalogue, consent lifecycle, source evidence, authorization policy and change events