Skip to main content

Notifications

Updated over a week ago

Notifications are used to keep members engaged and thus getting value from their subscription. For a variety of events, members can select how they would like to be notified, and when.

Migration from legacy push alerts

Before this notification system, there was a legacy push alert system that automatically sent push notifications upon meal plan or post publish.

Member Kitchen customers active before May 7, 2025 have the legacy system enabled until an admin specifically chooses to turn the new system on.

App station > Settings > Notifications

If the new notification system is turned on, you cannot go backwards to the legacy system.

Customers establishing service after May 7, 2025 have the current notification system enabled by default.

To avoid SPAM complaints, members of your app that were created under the legacy alert system will need to Opt-in to the new notifications (see below re: User preferences), however they will continue to receive the legacy alerts until they choose otherwise.

Members of your app that are created after you have enabled the new notification system, will have a default set of notifications enabled and can Opt-out using their User preferences.


Notification events

Notifications are automatically generated for each of the following events:

  • Meal plan published

  • Dashboard activity feed post published

  • New forum topic created

  • New comment on user topic (sent to users who have already engaged with the topic)

Each user can have different notification settings for each type of notification event (see below).


In app display (no email or push)

All members always haver access to notifications from within the application itself.

Shown below the Notification icon has the Unread notifications dot visible.

Tapping the Notification icon shows all notifications (regardless of notification preferences regarding delivery frequency).

  • Users can navigate to the notification content by tapping on the notification itself. This will mark the notification as read.

  • Users can choose to mark all notifications as read

  • Users can easily navigate to manage their notification preferences


Email notifications

An email notification is an email sent to a users provided email address, notifying them of a new notification. Each email has a link at the bottom allowing the user to modify their notification preferences as well as a link to the content the notification is based upon.

The content of the email is set by the admin via the templating system.


App notifications

An app notification is an notification sent directly to the users device, if the user has allowed for such notifications from your app.

The content of the notification is set by the admin via the templating system and works on any device (desktop or mobile) but does require the user to have installed the Universal app (PWA).

Tapping on the notification will take the user either to their installed app, or a browser window of the app depending on the device and operating system.


User notification preferences

Users can modify their notification preferences by navigating to their user profile and selecting Notifications.

Each type of notification has its own frequency setting so users can customize how often they want to be notified about events.

  • Never

    • Never send this type of notification

  • Immediate

    • Send this notification as soon as the event occurs

  • Daily

    • Only send a maximum of 1 notification per DAY. The first notification is immediately sent when it occurs, however if the same type of event occurs within the following 24 hours, no notification will be sent.

  • Weekly

    • Only send a maximum of 1 notification per WEEK. The first notification is immediately sent when it occurs, however if the same type of event occurs within the following 7 days, no notification will be sent.

Open user profile

Select Notifications

Choose frequency

Did this answer your question?