No this is not currently available. We would have to add in the ability to specify if you wanted an update to go out. If you're only changing a few spelling mistakes, you probably don't want to inform your users of changes.

It's not something we're working on at the moment. We understand the need, but we are simply focusing on other features right now.

My use case is knowing when a client facing article has an update, and my team knows, so we're all aligned on what changes are being made to the external facing help center. Right now, someone on my team can make a change to a whole section of an article, and I'd never know about it. I'd like to know about it.

Below is a screenshot of how a similar knowledge management application handles notifications for watchers, when articles are changed or have edits.

Is there a way in the future to add version control on articles? The reason for this is I want to be able to track changes over time and be able to edit an article without publishing it until all changes are made. Right now, if I edit the article, the only way to keep the old one published is to publish the new changes when I save. It would be nice to have an Edit vs Publish status. There are use cases to keep an article in Edit mode yet keep the previous version published. Example a monthly newsletter, or new version info, etc.

It sounds like both your use cases are internal. It's not to inform end-users of changes, it's so that you (and your team) can keep track of changes made? We have features coming that might help alleviate this problem by showing all events that happen to your articles and also showing revisions of articles, with specific changes to body content and title (similar to Jimmy's screenshot). These events would not be end-user facing, so do you believe that it still helps in alleviating the problem?

Will this feature allow the previous version (V1) to stay published and the newest version (V2) to stay in edit mode? Then, that helps us. If I press the Save button on the new version (V2) and it auto overwrites the older published version (V1), then that is a problem. We should only publish when we are ready to publish, not because we want to retain changes. Some of our changes come in over time and we don't want to publish them until all changes come in. We need to be able to collect changes on the newest version without publishing.

We put our documentation online, and whenever we add something new to our APIs, we usually updated existing articles, and would really like to notify our end-users with these additions, as the majority of our changes are brought to us directly from our customers, so it's highly relevant.

Getting notified for updated articles is a useful feature for many types of articles.

There's only one concern that what if you are just editing a typo! you want your user get notified?

I don't want it for our KB, But there's a solution for this!

If the articles have an option for version control, then if the author is fixing a spelling issue, won't change the version, however, if there's a big change to the article's content, then they can modify the version, and the end users can get notified, which is what exactly the users are looking for if they are following an article!

+1 for upgrading this feature to include a notification service when articles are updated. We use articles to write product releases, so the feature would be very valuable in terms of automating a few steps and add more value to our helpcenter in general.

We are also working with statuspage.io, and when we write a post there, we can choose if we want the update to be pushed to subscribers from ticking a box. Pretty simple feature to integrate and to control which content will be pushed out. Regarding the above comment, changing an insignificant thing like a typo, would not be pushed as a change to the subscribers, because the author would then simply avoid ticking off the box "Notify subscribers of changes made to this article"

Zendesk, is this on your roadmap? We would reconsider using the platform for our product releases, which would be a huge shame.

Hello, is there any update on when this feature will be added? It seems that there's a good demand from customer for this feature. It's really important for our users to be notified when an article they are following has been updated.

+1 vote for the option to receive an email notification whenever a followed section or article has been updated - with the author's option to enable/disable the notification for any given update.

We provide our software release notes to our clients on our HD and really want an automated way to notify our clients that the updates are available. The workaround to unpublish and republish the article with each update is clunky.

I was testing the 'Follow' feature but it does not seem to send email to users after I re-published an article. Can anyone provide a link to a good guide I can use to setup article so that users who 'Follow' my article will receive emails after I upload an attachment?

This is an issue for us. We update release notes articles on a bi-monthly basis. To get notifications, we have to create a new article in its place, copy everything over from previous releases and add the new release. Then we publish. The original article has to be archived. When we have many products, I have to do this for each product so users get notifies when they follow.

Would be nice if there is an option on each article that allows you to Notify followers (a checkbox) when that article is updated without having to keep creating new ones/archiving old ones.