Push notifications deliver alerts to a user's device even when the application is not open. ActiveManage uses the standard Web Push protocol so notifications work on Android phones, desktop browsers, and iOS (16.4+) Safari without requiring a native app.
Prerequisites
- HTTPS is required (Web Push will not work on plain HTTP, even on localhost beyond the dev exemption).
- The Service Worker must be installed (see the PWA section).
- VAPID keys configured under Site Settings → Communication → Push Notifications.
Generating VAPID Keys
The settings page has a Generate VAPID keys button. Click it once; the public key is embedded in client requests, the private key never leaves the server. Rotating the keys invalidates existing subscriptions so users have to re-enrol.
End-User Enrolment
- The user opens the application and is offered a banner: “Turn on notifications for new chat messages and booking confirmations?”.
- If they accept, the browser prompts for permission (one time).
- On allow, the subscription endpoint and keys are sent to the server and saved against the user.
Example Use Cases
- Field workers: Get a push when a new job is assigned, even when the app is closed.
- Marketplace sellers: Receive notifications for new orders so they can ship quickly.
- Educational platform: Students get notified when a lecture is published or an assignment is due.
Note: iOS requires the user to install the PWA to their home screen first before push notifications can be enrolled — there's no in-Safari push for ordinary tabs. Surface a friendly “Add to Home Screen” guide for iOS visitors.