Overview
Set channel/purpose policy and record customer communication preference/consent evidence.
Prerequisites
Permissions required
Steps (4)
-
1
Review the communication catalogue
Confirm the AccessGuard channel and core-purpose catalogue used by the workspace.
Tips
Validation
Success criteria
-
2
Set profile preferences
Configure preferred channel/locale, channel allowance, do-not-contact, and pause state for the customer profile.
Tips
Validation
Success criteria
-
3
Record consent evidence
Record channel/purpose status, source, lawful basis, wording/version, timestamps, and supporting evidence fields.
Tips
Validation
Success criteria
-
4
Verify delivery authorization
Create a notification recipient and confirm AccessGuard communication authorization uses the current preference/consent state.
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.