In this section

Resources / Help / Changelog

The public changelog page

A shareable page that lists your published posts, at app.hubbo.io/page/{your key}.

Besides the widget, Hubbo hosts a public changelog page for each account. It works like a changelog or announcement feed: a list of every published post whose Page channel is switched on.

URLs

WhatURL
The listhttps://app.hubbo.io/page/{your account key}
A single posthttps://app.hubbo.io/page/{your account key}/{post id}

These are the default addresses on app.hubbo.io. On Premium you can serve the same paths on a hostname you own. See Your own address.

The widget’s “Read Post” buttons open the single-post URL, unless you set a custom URL on the post.

What is shown

  • Changelog in the published state with the Page channel on, ordered with pinned items first, as blog-style tiles (category above the title, short excerpt, Published date).
  • Category labels in the colors you configured.
  • Opening a tile goes to the single-post URL (or the post’s custom URL when set).
  • Comments and reactions on the single-post view when you enabled them.

Using it

  • Link to it from your website footer, app menu or release emails you write yourself.
  • Share a direct link to a single post in a social post or a support reply.
  • Add it to your documentation as “What’s new”.

Visitors

A visitor session on the public changelog page can count as a visitor (once per browser session), like your own site. Signed-in admin editor previews do not count. See Visitors explained.

It is public

Anyone with the link can read published posts. Do not publish confidential information, and archive anything that should no longer be visible.

Targeting vs shareable links

Visitor auth (Anyone / Logged in / Logged out) and other Targeting rules decide who sees a post in the embed (toast, top bar, bell list on your site). They are not an access-control layer on the public page. A visitor who matched targeting can open or share /page/{key}/{id}; that URL stays readable for anyone who has it. Use Targeting for delivery, not secrecy.

Developers: see Public URLs and Identify visitors.