Repository navigation
Phone Alerts ntfy
Email and Teams alerts depend on Microsoft. On a day when Outlook and Teams are down, an alert sent that way goes nowhere -- exactly when you most need it. Phone alerts send a short push message straight to a technician's phone through ntfy, a free, open-source notification service, so an alert still reaches you.
- On each phone that should get alerts, install the free ntfy app (iPhone or Android).
- In Groundskeeper, go to Settings -> Notifications and find the Phone push (ntfy) card.
- Switch on Enable phone push alerts and click Save phone push settings. Groundskeeper makes a long random topic for you and shows it in the Topic box.
- Click Copy, then in the ntfy app choose Subscribe to topic and paste it in. Leave the server as the default (ntfy.sh) unless you run your own.
- Click Send test message. A message should appear on the phone within a few seconds.
By default only the alert title and how serious it is leave your network, for example "Core switch is down" with a note that it is a critical alert. Switch Send the title only off if you also want the detail line sent.
- Critical alerts are sent by default; tick Send on warning events to include warnings.
- A critical alert arrives as a high-priority notification; a warning arrives at normal priority.
- If you have told Groundskeeper the address people use to reach it (app.public_url), tapping the notification opens the dashboard.
Whatever you choose above, a Microsoft 365 Service Health alert about Exchange (Outlook) or Teams is always sent to the phone, because those are the services your email and Teams alerts depend on. Other Microsoft 365 services follow the normal rules.
On the free public server, the topic is the password: anyone who knows it can read your alerts. So Groundskeeper makes a long random one and will not accept a short topic there unless you use an access token. Treat the topic like a password: do not post it anywhere.
Two ways to make it safer:
- An access token. On an ntfy server that uses accounts, create an access token and paste it into Access token. Groundskeeper stores it encrypted and never shows it again. Leave the box blank to keep the saved one, or click Remove saved token to delete it.
-
Your own ntfy server. ntfy can be run inside your own network. Type its address (it must start with
https://) into ntfy server. Phones then need a way to reach it, so this suits schools that already run a VPN or a public address.
- Send test message says why it failed: a wrong address, a refused token, or no connection.
- Groundskeeper needs to reach the ntfy server on port 443 (HTTPS). If your web filter blocks
ntfy.sh, ask for it to be allowed. - If the ntfy server cannot be reached, Groundskeeper pauses push attempts for half a minute and tries again, so a dead server never slows down your email or Teams alerts. The failure is written once to the log.
- Phone push has no quiet hours of its own: use the phone's Do Not Disturb settings.
Under notifications.ntfy in config.yaml, so a settings backup carries it.
Last updated: 2026-11-12
Last updated: 2026-11-13 (v0.196.6)
- Home
- Getting Started
- Connectors
- What Groundskeeper Watches
- Firewall and Network
- Service Account
- AI Features
- Dashboard
- Staff Status Page
- Devices
- Alerts Page
- Incident Log
- Network Diagram
- Reports Page
- Software Advisories
- Intelligence Page
- SLT Dashboard
- Cyber Essentials Readiness
- DfE Filtering and Monitoring Readiness
- Central Edition
- Backup and Restore
- Updates
- Maintenance Windows
- Alerts and Notifications
- Phone Alerts (ntfy)
- Power BI Feed
- Two-Factor Sign-in
- Troubleshooting
- Support Bundle