Notifications

Notifications is where you set up the channels Scryer alerts you through — each entry is a configured provider instance for a notification channel.

Plugin-backed provider

entries are configured provider instances. The available fields come from the installed plugin and its provider catalog metadata. This page covers what Scryer needs to store and test for the configured connection.

• To access: Settings → Notifications
• To view: Requires manageSystemSettings app permission

Working In Notifications

If you want to be alerted when imports complete, fail, or when health warnings appear, install a notification plugin here first, then create a channel instance and select which events it should fire on.

If notifications stopped arriving, check whether the channel instance is still enabled and whether the plugin it depends on is still installed and current.

To add a channel, choose an installed provider type, enter the connection fields that provider requires, and — where supported — select which Scryer events should notify that channel. You can also edit, disable, or remove channels. Name each channel descriptively enough that you can tell which audience or destination it targets.

The usual order is: install the required notification plugin, then create the configured channel here. Send a test notification when the UI exposes that action — before you rely on the channel for operations — and disable a channel before removing the provider plugin it depends on.

Related Concepts

• Plugins — where the notification provider plugin must be installed before a channel instance can be created here
• Activity — live event feed; notification channels can be configured to fire on key events visible here
• System Overview — instance health dashboard where notification-relevant warnings may first appear