Global ClinicGuides
← All screen guides
Super AdminAvailable

Test notifications

Check that live notifications reach people. See who is connected to the workspace right now, send them a prepared test message, and read what happened on each of their devices. The test travels the same way every notification does, so a recipient sees it in the bell and as a toast, and hears the chime if their sound is on.

01

What you can do here

Who is connected now

Everybody signed in with a workspace open, across every clinic and hospital, one row per person per workspace. Each row shows the person, their workspace and role, whether they are online, and how many devices and tabs they have open. Open a row to see each device, when it connected and when it last checked in.

People who cannot be sent a test

Somebody without a membership in that workspace, with a suspended account or membership, or in a suspended workspace cannot be chosen, and the row says why. A platform administrator looking around a workspace they do not belong to is one of these.

Prepared messages only

Choose from a short list of test messages. Each one says it is a test, asks for nothing, names nobody and opens the recipient's own notification history, so a test can never start work, assign anything or open a record. There is a quiet one with no sound and a high-priority one with the stronger chime.

Preview before sending

See the message as the recipient will: as a toast, and as it sits in the bell and the notification history. Play the chime they will hear.

A delivery report for every person

After sending, each person's row says whether their devices received it, how many of their devices did, what happened on each one, how long delivery took, and whether they have opened it. Delivered, partly delivered, not delivered, and not sent are each shown clearly.

Connections that are no longer open

A device that closed without saying so is found when a test is sent to it, and removed. Check connections asks the connection service about every listed device at once and removes the ones it reports closed.

02

Follow these steps

Send a test

  1. Find the people in the list. Include people who are not responding if you want to test a device that may have gone to sleep.
  2. Tick each person to send to, up to 25 at once. They appear under Recipients.
  3. Choose a message and check the preview.
  4. Press Send test notification.
  5. Read the delivery report as it arrives. It usually completes within a few seconds.

Test on yourself

  1. Open the workspace in a second tab or on your phone.
  2. Your own name appears in the list for that workspace. Choose it and send the Sound check message.
  3. The toast appears in your other tab, and the chime plays there if you have clicked on that page since opening it.
03

Helpful habits

  • Tell people before you send them a test, or test on your own account first.
  • Use Every device when somebody reports that a notification reached one device and not another.
  • Use Quiet to confirm that a low-priority notification arrives without a sound.
  • If a report does not arrive within 30 seconds, the notification service may be delayed. Check again, then look at Exceptions.
04

Tips

  • A chime plays only when the recipient's notification sound is on and they have clicked or typed on the page since it opened. That is the browser's rule, not a delivery failure.
  • Not responding means a device has not checked in on time. Sending to it, or Check connections, finds out whether it is really gone.
  • A test stays in the recipient's history for 7 days, marked as a test.
  • Every send is recorded in each workspace's audit trail.
Next