Push notifications are off until an admin enables the channel at the org level. The steps below turn on both in-app and push for the Salesforce mobile app, then point you at custom notifications for org-specific events.
- Open Notification Settings
In Setup, use the Quick Find box to search for Notification Settings (under the Salesforce mobile app section) and open the page.
- Enable in-app, then push
Turn on in-app notifications first, since push depends on it, then enable push notifications for the org. Save your changes.
- Choose a content level
Decide between full content and minimal content for lock-screen display. Keep full content for convenience, or switch to minimal content if you handle sensitive data.
- Add custom notifications if needed
For business-specific events, create a Custom Notification Type, pick the mobile channel, then send it from a record-triggered flow, Apex, or the Connect REST API.
- Confirm on a device
Have a test user accept the OS permission prompt in the Salesforce mobile app, then trigger an event and verify the alert appears on their lock screen.
The bell-icon list inside the app. Must be enabled before push works.
Lock-screen and banner alerts delivered while the app is backgrounded or closed.
Whether the notification body shows on the lock screen or is hidden behind a generic prompt.
A metadata record that defines a custom notification and its desktop or mobile channels.
- Push will not work unless in-app notifications are also enabled in the same org settings.
- Each user must accept the operating system permission prompt on their device, or no push appears regardless of org settings.
- Delivery runs through Apple APNs and Google FCM and is best effort, so do not rely on push as the only signal for critical work.
- Over-notifying trains users to mute the app, so gate custom notifications behind tight entry criteria.