Skip to main content
Use Changelog to tell customers what shipped. Entries begin as private drafts and become public updates only when you publish them or their scheduled time arrives.

​
Draft the update

Open Changelog in the workspace dashboard and select New entry. Add a clear title and body that explain the customer outcome. You can also add tags. To add a version, a workspace owner or admin must first enable Version numbers under Workspace settings → Changelog. The editor shows the version field only when that setting is on. Keep the entry set to Draft while you review it. Drafts never appear on the public portal.

​
Draft with the assistant

Plus workspaces can ask the in-app assistant to draft an update from recently completed roadmap work. Open Assistant in the workspace sidebar, then choose Draft a changelog entry from recent work or describe the update you want. The assistant can prepare the copy and propose one of two actions:
  • Create a new unpublished changelog draft.
  • Update the title, body, or version of an existing unpublished draft.
The assistant shows the exact proposed fields before it changes anything. Choose Create draft or Save changes to approve that one action, or choose Cancel. It cannot publish, schedule, delete, tag, link requests to, or change engagement settings on an entry. Verify every claim and linked request before publishing through the normal review flow below. In the entry editor, link the requests addressed by this release. These links preserve the history from customer feedback to roadmap work to the public announcement. Review every linked request before publishing so the update represents the work that actually shipped.

​
Publish now or schedule

Turn Draft into Published when the update is ready to go live immediately. To publish later, choose a future date and time under Schedule, confirm the timezone, and select Schedule. The entry stays private until that time. You can change or clear the schedule before publication.
First publication can email every customer record that has an email unless that customer opted out of changelog emails. Review the title, body, audience, links, and timing before publishing now or scheduling the entry.

​
Published-entry limits

Your plan controls how many published updates appear publicly: When a new publication exceeds the limit, Glean Feed keeps the entry published and automatically hides the oldest public update. The dashboard labels a hidden entry Archived (plan limit). Its content, publication date, comments, reactions, tags, and linked requests are preserved. If your plan gains capacity—or you unpublish or delete a visible update—Glean Feed automatically restores the most recently plan-archived update that fits. Plan-limit archival is automatic; it is separate from changing an entry back to a draft.

​
Confirm the public update

Select Public Portal in the dashboard sidebar and open Updates. Confirm the new title, body, version, tags, and linked context appear as intended. If Updates is missing from the portal, a workspace owner or admin must enable Updates under Workspace settings → Portal → Behavior.
The workflow is complete when the entry is marked Published in the dashboard and the same update appears under Updates on the public portal. If an older update shows Archived (plan limit), confirm it no longer appears publicly.

​
Optional customer interactions

Workspace owners and admins control Update reactions and Update comments under Portal → Behavior. Both require Visitor accounts and the Updates public section. You can also turn reactions or comments on or off for an individual entry. When comment approval is enabled, new customer comments wait for team review before becoming public.