Why am I getting a 'permission denied' error when enabling push notifications?
If you’re using Chrome on macOS and you click Enable in the Push notifications section of the Settings page, you may see a “permission denied” error — even if you’ve never explicitly denied notifications in Chrome.
What’s causing it
Section titled “What’s causing it”This isn’t a bug in Propel Replays or in Chrome. It’s how Chrome interacts with macOS’s notification system.
On macOS, Chrome won’t display notifications unless Google Chrome itself has been granted notification permission in System Settings → Notifications. When that OS-level permission is missing, Chrome blocks the request and reports the web permission as denied — which surfaces in Propel Replays as the permission-denied error.
The reverse happens too: even when the web permission shows “granted”, macOS can silently suppress the banner if Chrome doesn’t have OS-level notification permission. That’s why some merchants think notifications are enabled but never see one arrive.
How to fix it
Section titled “How to fix it”- Open the macOS System Settings app.
- Go to Notifications.
- Find Google Chrome in the list of applications.
- Turn on Allow notifications, and make sure the alert style is set to Banners or Alerts (not None).
- Return to Propel Replays, go back to the Push notifications section in Settings, and click Enable again.
The same fix works for Edge and Firefox — they have the same constraint. Safari isn’t affected because it uses macOS’s notification system directly.