Currently, users lack a streamlined way to be notified of important updates to a Knowby without being overwhelmed by notifications for minor edits (e.g., typo fixes or small formatting changes). If notifications were automated for every save/publish action, it would quickly become "spam," causing users to ignore the notification system entirely.
Introduce a "Notify relevant users of this update" checkbox within the approval/publication workflow. This gives the creator or approver the power to determine if a new version warrants a ping to the team.
The Trigger: Add a checkbox to the final "Publish" or "Approve" modal that asks: "Notify users that a new version of this Knowby is available?"
Smart Audience Targeting:
If the Knowby is organisation-wide, notify all organisation members.
If the Knowby is restricted by Team, the notification should strictly only target members of those specific teams.
Notification Method: Delivery via the In-App Notification System (bell icon).
Audit Trail: (Optional) Log in the version history whether a notification was broadcasted for that specific version.
Reduced Noise: Users only get interrupted for significant process changes or safety updates.
Higher Engagement: By making notifications intentional, users are more likely to actually click and read the updates when they occur.
Administrative Control: Creators can push "silent updates" for minor maintenance without clogging up their teamβs activity feeds.
Please authenticate to join the conversation.
In Review
π‘ Feature Request
3 days ago
Get notified by email when there are changes.
In Review
π‘ Feature Request
3 days ago
Get notified by email when there are changes.