Skip to main content
Not every update should stay up forever. A maintenance window, a temporary workaround, or a beta invite is only useful while it is true. Unpublishing takes a live entry off your changelog while keeping the entry, its content, and its stats in your admin, and duplicating turns any entry into a fresh draft you can edit and publish again. For writing and publishing an entry in the first place, see Create changelog entries.
Unpublishing an entry cannot be undone. There is no way to put an archived entry back on your changelog, so the way to publish something again is to duplicate it and publish the copy.

Take an entry down now

Use this when an update has served its purpose and you want it off your changelog straight away.
1

Open the entry and open its actions menu

Go to the Changelog, click the entry you want to take down, then click the button in the top right.Unpublish only appears on entries that are currently live. A draft and a scheduled entry were never public, so there is nothing to take down: delete them instead.The changelog editor actions menu open, showing Duplicate, Unpublish, and Delete
2

Confirm the takedown

Click Unpublish, then confirm. Sleekplan reminds you that the entry cannot be published again and that duplicating it is how you publish a new copy.The Unpublish this entry confirmation dialog with Cancel and Unpublish buttons
3

The entry becomes archived

The entry is marked Archived and disappears from your public surfaces immediately. It stays in your admin, where you can still read it and see its stats.
Taking an entry down by hand is available on every plan. It is a safety valve, not a paid feature, so you never have to delete a live entry just to remove it.

Schedule a takedown in advance

If you already know when an update stops being relevant, set an unpublish date and Sleekplan takes the entry down for you. This is the setting to use for a scheduled maintenance notice: publish it before the window, and let it retire itself afterwards.
1

Open the Unpublish date field

In the entry’s options panel on the right, find Unpublish date underneath Publish date. It is available while you are writing a draft, on a scheduled entry, and on an entry that is already live.The Unpublish date field in the changelog options panel, set to Select date
2

Pick a date and time

Choose when the entry should come down. The field is optional, and you can clear a date you set earlier if you change your mind, as long as the entry is still live.
3

Save the entry

Save the draft, or publish or update the entry as usual. Sleekplan checks for expired entries every minute, so the takedown happens within a minute of the time you picked.

The six hour minimum

An unpublish date has to be at least six hours after the entry’s publish date. An entry that comes down sooner than that was never really published: most subscribers would never have seen it. The gap is always measured against the entry’s own publish date, not against the current time. An entry published three months ago accepts an unpublish date tomorrow. An entry you published an hour ago does not accept a date two hours from now, because that is a gap of three hours, not six. If the date you pick is too close, the field shows “Must be at least 6 hours after the publish date” and the Publish, Schedule, or Update button stays disabled until you fix it.
Setting an unpublish date needs a plan that includes changelog scheduling (Business plan and above), the same as scheduling a publish date. If your plan does not include it, saving prompts you to upgrade. Taking an entry down by hand works on every plan. See Billing for what your plan includes.

What happens to an archived entry

Archived is the end of an entry’s life. It is removed from everywhere your users could see it, and it is frozen in your admin. Your users no longer see it:
  • It is gone from the changelog in your widget and on your public portal.
  • Its public link no longer resolves to the entry.
  • It drops out of your changelog RSS feed and out of your sitemap.
  • It stops appearing as an in-app announcement pop-up.
  • If an email about it was still waiting in the notification queue, that email is not sent.
In your admin it becomes read only. The title, the body, and every option in the panel are locked, and the only two actions left are Duplicate and Delete. The panel replaces the unpublish date with the date the entry was archived, and the stats it collected while it was live stay visible. An archived changelog entry showing the Archived badge and the date it was archived The actions menu on an archived entry, offering only Duplicate and Delete

Find your archived entries

The Changelog list has an Archived section and a matching Archived tab, alongside Scheduled, Published, and Drafts. Use the tab to see only the entries you have taken down. The Changelog list filtered to the Archived tab, showing one archived entry
Delete is still permanent and still different from unpublishing. Deleting removes the entry, its content, its images, and its stats for good. Unpublishing keeps all of it. If you only want the update off your changelog, unpublish it.

Reuse an entry with Duplicate

Duplicate copies an entry into a new draft, so you can edit and publish it without rewriting it. It works on any saved entry, whatever its state, and it is the only way to put an archived update back on your changelog.
1

Open the entry you want to copy

Open any entry from the Changelog list, then click the button in the top right and choose Duplicate.
2

Edit the new draft

Sleekplan creates the copy as a draft and opens it straight away, so you can change the dates, adjust the wording, and publish when you are ready.The duplicated entry open as a new draft with its stats reset to zero
Here is what the copy keeps and what it starts fresh:
The copy is a genuinely new entry, so publishing it notifies subscribers again if Notify subscribers is on, and it starts its own view and reaction counts. Check the distribution settings on the draft before you publish it.

Run a recurring notice

Unpublishing and duplicating are designed to work together for updates you post again and again, like a deployment or maintenance notice.
1

Publish the notice

Write the entry once and publish it. If you already know when the window ends, set an unpublish date at least six hours out and skip step 2.
2

Take it down when it is over

Unpublish the entry from its actions menu. It disappears from your changelog and moves to the Archived section.
3

Duplicate it for the next time

When the next window comes around, open the archived entry, choose Duplicate, update the dates and details in the new draft, and publish. Your wording stays consistent and you never start from a blank editor.

Create changelog entries

Write an entry, schedule it, target a segment, and notify subscribers.

The changelog

Read the changelog list and use its status tabs, category filter, and search.

In-app announcements

Surface a published entry as a New Updates pop-up inside your widget.

Plans and billing

Check what your plan includes, including changelog scheduling.