Novu provides a way to store user preferences in the subscribers data model. This allows subscribers to specify and manage their preferences, without your intervention. Customizing preferences has become the standard expected behavior for people and Novu can take the technical burden of managing preferences off of you.
Novu allows several levels of preferences:
When creating a new workflow on the Web platform, you can specify default preferences for the subscribers in channel settings. They will be used unless the subscriber overrides them by his own custom preference.
This will allow you to create sensible defaults but still provide the user with the ability to override them. Template level preference can be managed in channel settings. All channels are ON
unless specified otherwise.
Workflow Settings > Channels
Our notification center component will show a user the available preferences, user will be able to modify on the channel level. Critical workflows will be excluded from the list. Click on cog (setting) icon on notification center component to open subscriber channel preferences page.
Only channels with a matched step will be returned from the API in notification center preference page. In case no channel content was found, the API will return an empty array.
Subscribers can set global channel preferences, which override individual settings. For instance, if there are 10 workflows, and a subscriber wants to disable SMS notifications for all of them, they can do so with a single global preference.
Get subscriber’s global preference API
Update subscriber’s global preference API
In some cases, you don’t want the subscriber to be able to unsubscribe from mandatory notifications such as Account Verification, Password Reset, etc…
In those cases you can turn off the toggle Users will be able to manage subscriptions
in channel settings. Workflow will become critical
, once this toggle is turned OFF
. By default, every workflow is non-critical
and subscribers can manage channel preferences irrespective of workflow-level channel preferences. Critical workflow will not show on the subscriber preferences page.
Users will be able to manage subscriptions
toggle is turned off i.e workflow is critical, this will override workflow level and subscriber level preferences and notification will always be sent.false
value set for enabled
field in preference then all other channels will become inactive even if they have true
state.true
value set for enabled
field in preference then notification will be filtered based on subscriber channel preference.Example
For First Workflow
, critical
is false, enabled
is true, in_app, email, push channels are true and sms, chat channels are false. As per above order of priority of preferences, notification will be filtered as per the subscriber preferences. The subscriber will receive in-app, email and push notifications, but not receive sms and chat notifications.
For Second Workflow
, critical
is false, enabled
is false, all channels are true. As per above order of priority of preferences, subscriber will not receive any type of notification because all channels become disabled due to false value of enabled
field.
For Third Workflow
. critical
is true, enabled
is false, email, chat channels are false and the other three channels are true. As per above order of priority of preferences, subscriber will receive all type of notifications as this workflow is critical
.
How to change enabled field from UI?
This field can only be changed using API.
What preferences are applied to a subscriber when we create a new workflow?
In the case of a new workflow, the subscriber will inherit all preferences from the workflow.However, after subsequent preference updates, the subscriber’s preferences will not inherit workflow-level preferences.
How to disable a workflow for a single subscriber?
You can turn off all workflow’s channels for a subscriber using subscriber preference. If all channels are off, then the subscriber will not receive any message from any channel step and hence workflow is disabled for that subscriber
Novu provides a way to store user preferences in the subscribers data model. This allows subscribers to specify and manage their preferences, without your intervention. Customizing preferences has become the standard expected behavior for people and Novu can take the technical burden of managing preferences off of you.
Novu allows several levels of preferences:
When creating a new workflow on the Web platform, you can specify default preferences for the subscribers in channel settings. They will be used unless the subscriber overrides them by his own custom preference.
This will allow you to create sensible defaults but still provide the user with the ability to override them. Template level preference can be managed in channel settings. All channels are ON
unless specified otherwise.
Workflow Settings > Channels
Our notification center component will show a user the available preferences, user will be able to modify on the channel level. Critical workflows will be excluded from the list. Click on cog (setting) icon on notification center component to open subscriber channel preferences page.
Only channels with a matched step will be returned from the API in notification center preference page. In case no channel content was found, the API will return an empty array.
Subscribers can set global channel preferences, which override individual settings. For instance, if there are 10 workflows, and a subscriber wants to disable SMS notifications for all of them, they can do so with a single global preference.
Get subscriber’s global preference API
Update subscriber’s global preference API
In some cases, you don’t want the subscriber to be able to unsubscribe from mandatory notifications such as Account Verification, Password Reset, etc…
In those cases you can turn off the toggle Users will be able to manage subscriptions
in channel settings. Workflow will become critical
, once this toggle is turned OFF
. By default, every workflow is non-critical
and subscribers can manage channel preferences irrespective of workflow-level channel preferences. Critical workflow will not show on the subscriber preferences page.
Users will be able to manage subscriptions
toggle is turned off i.e workflow is critical, this will override workflow level and subscriber level preferences and notification will always be sent.false
value set for enabled
field in preference then all other channels will become inactive even if they have true
state.true
value set for enabled
field in preference then notification will be filtered based on subscriber channel preference.Example
For First Workflow
, critical
is false, enabled
is true, in_app, email, push channels are true and sms, chat channels are false. As per above order of priority of preferences, notification will be filtered as per the subscriber preferences. The subscriber will receive in-app, email and push notifications, but not receive sms and chat notifications.
For Second Workflow
, critical
is false, enabled
is false, all channels are true. As per above order of priority of preferences, subscriber will not receive any type of notification because all channels become disabled due to false value of enabled
field.
For Third Workflow
. critical
is true, enabled
is false, email, chat channels are false and the other three channels are true. As per above order of priority of preferences, subscriber will receive all type of notifications as this workflow is critical
.
How to change enabled field from UI?
This field can only be changed using API.
What preferences are applied to a subscriber when we create a new workflow?
In the case of a new workflow, the subscriber will inherit all preferences from the workflow.However, after subsequent preference updates, the subscriber’s preferences will not inherit workflow-level preferences.
How to disable a workflow for a single subscriber?
You can turn off all workflow’s channels for a subscriber using subscriber preference. If all channels are off, then the subscriber will not receive any message from any channel step and hence workflow is disabled for that subscriber