Personal Notification Preferences
Last updated: 2026-05-12
StatusPage.me now has two layers of notifications for account users:
- Shared notification channels for your team and status pages, such as email, Slack, Discord, webhooks, and PagerDuty
- Personal notification preferences for your own account, such as the dashboard bell, browser notifications, and critical incident alarm sounds
Use personal notification preferences when you want to control how you see alerts while working in the dashboard.
Where to configure them
Open:
- Personal alert preferences for your personal alert preferences
- Full in-app notification history for the full in-app notification history
If you need to configure team-wide delivery channels instead, use Notification Channels Overview.
Notification Types and Delivery Matrix
The preferences page includes a general notification matrix for categories such as:
- account activity
- security events
- system updates
For each category, StatusPage.me can show separate delivery options for:
- browser notifications
- app notifications
At the moment, app notifications are marked as coming soon, so the main usable personal channels are email, browser, and the in-app dashboard experience.
The page also includes a separate Trial Notifications section where you can control whether you receive trial emails and how frequently they are sent.
Email Frequency
For non-critical personal notifications, you can choose an email frequency:
- Immediate
- Daily digest
- Weekly digest
Use digests when you want fewer inbox interruptions for lower-priority events, while still keeping critical alerts visible through browser notifications or the dashboard alarm.
This frequency setting applies to the general non-critical notification section, while trial-email frequency is controlled separately in the trial section.
Notification bell and in-app notifications
The bell icon in the top navigation gives you a quick in-app notification list.
From the dropdown, you can:
- Open a notification directly
- Mark an individual unread notification as read with the checkmark on that row
- Mark all visible notifications as read
- Open the full notifications page for older items
Clicking a notification row also clears its unread state as it opens the destination.
Use the full notifications page if you want a longer history or prefer reviewing items outside the dropdown.
You can also enable a lightweight sound for new in-app notifications.
- Play sound for new in-app notifications adds a normal notification sound for fresh dashboard items.
- Critical incidents still use the stronger persistent incident-alarm workflow described below.
Browser notifications
Browser notifications let StatusPage.me show incident-related alerts even when the dashboard tab is not in the foreground.
To enable them:
- Open Personal alert preferences
- Turn on Show browser notifications for incidents
- Allow notification permission when your browser prompts you
- Save your preferences
If your browser has already blocked notifications, StatusPage.me will show a warning and you will need to re-allow them in the browser’s site settings before enabling the toggle again.
Browser notifications are tied to the current browser/device. If you use multiple browsers or computers, enable them in each one where you want alerts.
Browser notifications are especially useful if you keep the dashboard open in the background while working elsewhere.
Incident alarm sound
For critical events, you can also enable a local alarm sound inside the dashboard.
This is useful for high-priority events such as:
- monitor down alerts
- on-call escalations
When enabled, you can choose:
- whether the incident alarm is on at all
- which alarm sound to use
- the playback volume
- a quick preview before saving
Available alarm choices include several built-in sounds such as a digital alarm, classic alarm, siren, and emergency-alert-style tones.
The alarm is designed to loop until you dismiss the alert, so it is best used for situations where you want an unmistakable local warning while actively signed in.
If you are tuning the alarm for a noisy room or shared workspace, use the built-in Preview button and the volume slider before saving.
Privacy Option
The preferences page also includes a privacy control:
- Exclude yourself from analytics on your own status pages
Enable this if you want to avoid skewing your own web analytics when you visit status pages you manage.
How this differs from notification channels
Personal notification preferences do not replace your configured notification channels.
- Notification channels decide where your team-facing alerts are delivered across email, chat, webhooks, SMS, PagerDuty, and similar integrations.
- Personal preferences decide how your own signed-in dashboard session behaves.
For example, you can keep Slack and email enabled for the team, while also enabling browser notifications and a local incident alarm for yourself.
Best Practices
- Enable browser notifications on every device where you actively monitor incidents.
- Use the incident alarm only for the highest-urgency local workflows, since it is intentionally hard to ignore.
- Keep normal in-app sounds enabled if you want awareness without the full critical-alarm experience.
- Use digest email frequency for lower-priority updates if your inbox is already noisy.
FAQ
Q: Why do browser notifications work on one laptop but not another?
A: Browser notifications are permission-based and device-specific. Enable them separately in each browser and computer you use.
Q: Can I preview the critical alarm before saving?
A: Yes. The preferences page includes a preview button and volume slider for the incident alarm sound.
Q: Are app notifications available yet?
A: The preferences UI shows app notifications as coming soon.
Q: Do personal preferences replace Slack, email, or PagerDuty channels?
A: No. Personal preferences are for your own signed-in experience. Shared channels still control team delivery.