Overview
Use templates, logical notifications, recipients, in-app inbox state, events, read/seen/pin/archive/dismiss controls, delivery state, and retries.
Problem
Applications need a consistent customer notification record instead of coupling business events directly to delivery providers.
Solution
Create notifications in AccessGuard, keep recipient and inbox state in one governed service, and apply customer communication policy consistently.
How it works
AccessGuard owns notification, recipient, inbox and event history, supports read/seen/pin/archive/dismiss flows, and runs background lifecycle processing for notification state and maintenance.
Who is this for
Application Engineer
Notification Administrator
Customer Operations Team
Expected outcomes
- One logical notification/inbox model across applications
- Provider delivery separated from business-event ownership and customer policy
Key metrics
Security impact
- Notification content, recipient identity, channel, delivery status, inbox state and events · PII: yes where notification content or recipient identity is personal
Compliance
- Operation authorization, communication policy, provider delegation, retry state and notification audit events
Availability & next steps
Pro
Enterprise