Communications
Choose which notifications your organization receives, and who receives them.
Notification categories
Payment receipts, failed charges, dunning.
New sign-ins, MFA changes, session reuse.
Provisioning, installs, backups, incidents.
New features and template releases.
Recipients
| Person | Categories | |
|---|---|---|
GI George W. Scott III[email protected] | Billing · Security · Technical | |
PT Priya Tanaka[email protected] | Billing | |
MR Maya Ruiz[email protected] | Security · Technical |
Where platform messages go and proof they arrived. Route billing, technical, and security emails to the right people, and review recent deliveries — including any that failed and were retried — so an important notice never silently disappears.
Behind this page/communications · CanManageAccount
Retrieve
Settings row read fromCustomerCommunicationPreferences — no dedicated getter; the upsert returns the current row. Delivery history lives in CustomerNotificationLog.Save
Preferences saved viasp_Builder_UpsertCommunicationPreferences. Delivery history reads via sp_Communication_GetDeliveryHistory — keyset-paged, filterable by category and channel, gated on CanManageAccount.Success
- Category toggles + recipients persist per account.
- Security category cannot be fully disabled.
- Recipients validate against account members.
CLI handoff
Implement this scaffold from the structured contract, then remove hard-coded preview rows. The source of truth is CLI Handoff and admin-cli-manifest.json.
Server-inject identity and scope values; never trust browser-supplied account, app, tenant, user, entitlement, price, or permission identifiers. Preserve the loading, empty, forbidden, failed, retrying, and completed states shown by the preview.