Skip to main content

Publish Help Center Release Updates and Planned Changes - Article

Use release content for change communication, select the intended audience and distinguish visibility from notifications. Maintain planned information without presenting it as a committed delivery promise.
Updated: 18 Nov 2026
5 min read

Summary

When a service changes, readers need to understand what the change means for them and whether they need to act. Release content provides a distinct communication route alongside evergreen how-to articles.

Use Releases for dated updates where that capability is part of your Help Center service. Keep the ongoing operating instructions in their authoritative articles and treat planned information as a separately maintained public communication.

Use this article to:

  • Choose between an evergreen article, a Release and planned information
  • Configure Release visibility and notification conditions
  • Review dates, audiences and public planned content before publishing

Give change communication a clear purpose

An article explains how the current process works. A Release explains a dated change and its practical effect. Link from the update to the maintained procedure so readers do not have to reconstruct the current operating process from a series of historical announcements.

Confirm that Releases and the associated notification service are included in your customer-managed Help Center configuration. The Eurekos-managed Help Center uses these capabilities for platform communication; that does not by itself mean every customer service has the same delivery integration.

Keep release audiences aligned with your users

This feature is particularly useful for software companies that maintain a customer or partner academy alongside their software service. A Release can explain a product change to the people who need to act: customer administrators preparing a configuration change, partners supporting an updated process, or users learning a revised workflow.

Use the roles already maintained in the connected LMS to target the update. When customer and partner users are created, assigned roles or maintained through that connected service, those existing populations provide the basis for release communication. This reduces the need to maintain a separate mailing list for each announcement and makes the communication useful throughout the customer relationship.

For example, publish a configuration update for customer administrators and link to the maintained setup article. A separate update can explain the effect on everyday users. Review role assignments, connected-platform eligibility and notification preferences before sending: an article or Release being visible and a person receiving email are separate outcomes.

Create a Release

As a Help Center administrator, open Content management → Releases. Search by title, inspect existing updates and select Create. Published and unpublished records are maintained in the same area.

Field or controlEffect and useful choice
Title and Short descriptionIdentify the update and its main reader benefit or required action
DescriptionExplain the affected process, scope, timing and next step
RolesSelect the intended reader audiences; at least one selection is required
PlatformsRestrict visibility to the selected connected platforms; leaving it empty applies no specific platform restriction
Notify platform users about this releaseEnables the related email notification configuration where supported
Specific platformsNarrows the notification destination within the platforms eligible to see the Release
Email subject and Email bodyProvide the notification message when sending is enabled
Release dateSets the required date in DD/MM/YYYY format and the notification date when enabled

On a production Help Center, the Platforms choices are production platform connections. A platform restriction and a notification destination are different controls: selecting a platform for email cannot make a Release visible when the visibility configuration excludes it.

Do not combine Public user with a specific platform visibility restriction. Anonymous visitors have no qualifying platform identity, so the update can be listed publicly yet fail when opened. Use a coherent public route or a restricted platform audience and test it.

Treat notification delivery separately from publication

Saving or publishing a Release and sending its email are related but different outcomes. When notifications are enabled, eligible users on the selected platforms are considered according to roles, service configuration and subscription preferences. Users who have already received an email for that Release are not notified again merely because the same record is edited and republished.

Use the email for the practical message: who is affected, what changes, when it matters and where to read the current procedure. Do not assume every eligible reader receives email; a reader may have unsubscribed or be outside the notification configuration. Release notification preferences are separate from general training emails.

If an important correction requires additional communication, plan an appropriate new communication rather than relying on republishing the same Release to resend it. Verify the intended audience and delivery route before any live notification.

Maintain Future releases carefully

Content management → Future releases maintains one planned-information page rather than a collection of role-targeted Release records. Open Edit, maintain its Content and choose Save draft or Publish as appropriate.

A published Future releases page is available to everyone who visits the Help Center. It does not have the article-style Roles restrictions. Keep confidential plans out of this page.

Explain the planning horizon and what is tentative. Distinguish an intention from an agreed delivery commitment and remove or revise obsolete plans. Do not use a future page as the operating instructions for a capability that readers cannot yet use.

Check the reader’s change journey

Readers use Releases to browse eligible updates and search by title. A Release presents its title, published information and body, with navigation between appropriate updates. The Future releases entry is available when its page is published.

Scenario or checkExpected result or evidence
A permitted reader opens the ReleaseThe audience and platform configuration allow the intended update
An anonymous visitor opens a public updateThe content opens without an incompatible platform restriction
Notification settings are preparedVisibility, roles, platform eligibility and preferences form a coherent recipient route
An already-notified Release is republishedIt is not treated as a guaranteed resend to previous recipients
The planned-information page is publishedIts contents are suitable for all visitors
A change affects a process articleThe authoritative article is updated, not left dependent on historical release wording

Troubleshooting

ProblemWhat to check
A public Release opens with an access errorCheck for an incompatible specific Platforms restriction
A selected notification platform receives nothingCheck that it is eligible to see the Release, the roles and notification configuration, date and user preferences
Republishing did not resend the emailPreviously notified users are not notified again solely through an edit and republish
A reader cannot see Future releasesCheck whether the page is published and included in the service configuration
An administrator preview shows more updates than a readerVerify the ordinary reader context instead of relying on the administration account

FAQ