Digest Notification Emails
under review
Kesavan M
Currently, users receive individual emails for every article update, leading to notification overload. We request an option to send consolidated digest emails (for example, weekly or daily summaries). This will reduce email fatigue and improve user engagement. It will also help prevent users from unsubscribing due to excessive notifications.
Log In
D
D360 Product Management
marked this post as
under review
K
Kavya
Hi Particular Beetle, Tangerine Narwhal,Kesavan M
Thank you for sharing this feedback.
Currently, you can control notification volume by toggling off specific events or channels from the notification mapping settings, which helps reduce the number of individual emails being sent.
Attached sample for reference
That said, to better understand your requirement for digest emails, could you please clarify:
What kind of summary format are you expecting?
Daily / Weekly digest
Grouped by articles updated
Grouped by user/activity (e.g., assigned to me, followed articles)
Should the digest include only updates from followed/subscribed articles, or all project activity?
Do you expect this to be configurable per user (opt-in/out), or at a project/admin level?
This will help us evaluate whether a digest-based notification system can be considered as an improvement.
Photo Viewer
View photos in a modal
H
Heliotrope Koala
Kavya
Thank you for following up. Happy to clarify.
- What digest format are we expecting?
Both daily and weekly digests would be valuable, ideally user-selectable. The Salesforce model mentioned in the comments is a good reference: users can choose between no notifications, immediate (individual), daily digest, or weekly digest. A weekly digest would be the most impactful starting point for reducing fatigue.
The digest itself should be a single email summarizing all relevant activity in the period. Something like:
- Article title + a brief description of what changed
- Who made the change
- A link directly to the article
Grouping by article updated makes the most sense for readability.
- Should it include only followed/subscribed articles, or all project activity?
Ultimately, it probably should be up to the end-users, and cover only articles they follow or that belong to categories they subscribe to — not all project activity.
However, for our use-case, we would be fine with a digest of all published project activity.
- Per-user opt-in, or admin-controlled?
First, let's define user. A user can be either someone logging into Document360 or a customer coming to view documentation. The context that this was raised was regarding the latter.
So, the "user" we are referring to are subscribers. They do not need to log into Document360. They subscribe to receive notifications.
Now to answer the actual question. Ideally both, with a hierarchy:
-Project Default: Document360 Administrators set the default frequency (e.g., weekly digest) for the entire project.
-Subscriber Override: Individual subscribers can override the default with their own preference (immediate, daily, weekly, or none).
This mirrors how most mature notification systems work and gives both admins control over defaults and subscribers autonomy over their own inboxes.
To directly address your note about the current notification mapping settings: We are aware of the ability to toggle off events or channels entirely, but that's an all-or-nothing solution. The ask here is specifically about frequency control. Letting users stay informed without being overwhelmed. Turning off notifications entirely defeats the purpose of the subscription system.
P
Particular Beetle
Does this happen to customers? Is there a setting to help prevent this?
T
Tangerine Narwhal
This is a great idea. In Salesforce, users can opt for no notifications, individual notifications, daily digest, and (I believe) a weekly digest of all changes to records being followed.