Overview
Use AccessGuard as an audience source for a live visibility rule or a frozen outbound snapshot.
Problem
EngagementHub should not duplicate user approval logic or maintain its own list of approved accounts.
Solution
AccessGuard exposes approved_users through the common provider controller pattern and remains authoritative for account and approval state.
How it works
An editor selects AccessGuard, chooses Approved users, previews the count, then retains a live rule for portal visibility or requests a frozen snapshot for a campaign dispatch. At message send time, the delivery path re-checks current account and consent status.
Who is this for
Customer Experience
Campaign Operations
Access Administrators
Expected outcomes
- No duplicated approval logic
- Current portal visibility membership
- Auditable outbound targeting snapshot
Key metrics
Audience definition duplication
6 count
0 count
Provider preview response time
10 seconds
2 seconds
Outbound snapshot traceability
0 %
100 %
Gallery
Downloads & templates
Security impact
- AccessGuard audience definition, parameters, preview counts, snapshot reference, and account identifiers · PII: Registered user IDs and permitted communication endpoints
Compliance
- Workspace-scoped provider query
- Snapshot does not override later opt-out or suspension
- Identity details minimized
Availability & next steps
Free
Growth
Business
Enterprise