Overview
Use the visual audience builder and controlled schema/AST flow to define customer segments.
Prerequisites
Permissions required
Steps (4)
-
1
Choose the root entity
Open the audience builder and select the AccessGuard schema/root entity used for segmentation.
Tips
Validation
Success criteria
-
2
Add relationships and filters
Build nested AND/OR conditions, relationship filters, grouping and HAVING rules using the schema-aware builder.
Tips
Validation
Success criteria
-
3
Validate and preview
Run validation and preview to inspect the compiled/controlled result before saving.
Tips
Validation
Success criteria
-
4
Save and activate
Create the audience, manage versions/status, and expose members through granted audience capabilities.
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.