Overview
Build a logical notification, recipients and inbox state, then allow the dispatch worker to use configured providers.
Prerequisites
Permissions required
Steps (4)
-
1
Create or select a template
Use the notification-template administration surface to create, preview and activate the content definition.
Tips
Validation
Success criteria
-
2
Create the logical notification
Create the notification with source, category/type, priority, content, action/payload, expiry and dedupe metadata.
Tips
Validation
Success criteria
-
3
Add or dispatch recipients
Use notification.dispatch or recipient APIs so AccessGuard creates delivery/inbox state and applies communication policy.
Tips
Validation
Success criteria
-
4
Inspect delivery history
Use recipient and event views to inspect delivery status, provider reference, attempts, inbox/read state and retry/skip controls.
Tips
Validation
Success criteria
About this guide
AccessGuard centralizes workspace authentication and customer identity. External websites can use the signed Bridge v2 proxy and JavaScript SDK for registration, login, verification, recovery, token refresh, profile management, protected media, and notification inbox operations.
Inside the workspace, AccessGuard owns users, sessions, verified identities, customer profiles, communication preferences and consent, approval state, KYC documents, risk flags, notification state, audience segments, application operation grants, delegation policies, and trusted context actions. Canonical capabilities are available through Handler and RCP, with selected operations available through Bridge v2.
Configured providers handle downstream delivery and human work: email, SMS, WhatsApp, voice, push, and case/problem operations can be delegated while AccessGuard preserves the identity, authorization, provenance, and customer-policy record.