Scope
This guide covers setup & configuration for Push Notifications. Availability depends on your tenant package, role and configured providers.
Purpose
Reach opted-in web or app audiences with timely notifications.
Configure push provider, site/app identity and opt-in flow.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- Open the correct tenant and confirm the project or workspace that owns this capability.
- Configure push provider, site/app identity and opt-in flow.
- Connect or select the required source records and owners.
- Create a safe test configuration before using live customer or campaign data.
- Review sends, delivery, clicks and re-engagement.
- Respect permission state, caps and channel eligibility.
Verify the result
Review sends, delivery, clicks and re-engagement. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Respect permission state, caps and channel eligibility. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.