Critical notifications

Note: requires mobile app version >= 1.2.27

If you need notifications to bypass do-not-disturb policies, for example when you are using Notify17 for night-time monitoring, you can use Critical notifications.

This feature is platform-dependent:

  • iOS supports natively critical notifications, and you don’t need any additional configuration.
  • Android requires some human intervention before this feature can be enabled. Please follow the guide below to configure critical notifications on Android devices.

You can generate critical notifications using:

Android configuration

Disclaimer: To configure critical notifications on Android, you have to first generate (at least once) a notification marked as critical, e.g. by using a critical condition.

After you generate at least one critical notification, you can then open Notify17’s Notification settings, as illustrated below:

The Notification settings button will open Android’s notification settings page for the Notify17 application.

Disclaimer: the following documentation refers to a standard Android operating system version, and different manufacturers may provide a different visual experience.

In this page you can see the list of you possible “notification channels”, each identified by:

  • A CRIT/ prefix, if the notification channel refers to a critical notification
  • The sound name related to this notification channel (default, if no specific sound name has been used)
  • Your shortened login identifier (e.g. email address) and login method

To proceed with the configuration, tap on the relevant CRIT/-prefixed notification channel (if you used a custom notification sound, make sure you’re tapping on the correctly named one!):

Once you’re in the notification channel settings, you need to enable the Override Do Not Disturb switch:

Awesome! Now your critical notifications will bypass the do-not-disturb mode!