Test notification delivery

Global administrators can test notification delivery from Admin → Dashboard → Maintenance → Notifications.

Send a test

1. Open the Notifications card.
2. Select Test.
3. Wait while it shows Testing.
4. Read the result, channel, provider, target identifier, and tested time.
5. Check the selected target device for receipt.

Test uses the most recently updated active, unexpired notification destination on your account. It can select browser push, mobile push, or mobile local reminders. The dashboard has no destination picker, so the selected destination may belong to another browser or device you use.

Test also needs a Guide available through the destination owner's View, Edit, or Owner folder access. Use-only access is not selected by this test.

This is a delivery attempt, not just a configuration check. It can send a notification and update the destination's delivery/failure history.

Interpret the result

Delivered describes the delivery adapter's outcome. It does not prove a person saw or opened the notification. In mock mode, it does not prove any real device received one.

A returned delivery failure differs from a request that could not finish. Read the visible explanation, resolve the cause, and select Test again. Test does not require a successful readiness check before it can run.

If no destination is enrolled

1. Read the missing-destination message.
2. Use the embedded notification settings on a supported browser or device.
3. Grant permission and complete enrollment when prompted.
4. Select Test again.
5. Confirm the selected target and check receipt.

Opening the recovery controls does not itself request permission or enroll a destination. A browser cannot enroll a mobile destination through a missing native app integration.

Missing browser configuration or unavailable delivery services need the administrator responsible for those services. Follow browser setup or device setup as appropriate.

If a Guide or request is unavailable

A no visible Guide message means a destination exists but the test could not choose a Guide for its owner. Arrange the appropriate folder access to a Guide, then retry. It does not establish that delivery itself failed.

For another request error, check connectivity and current administrative access, then retry. Request diagnostics provides additional request details for authorized support. An incomplete request does not establish whether a device received a notification.

The neighboring cleanup buttons manage registrations across accounts; they are separate from testing your own destination. Read notification cleanup before using them.