---
title: "Review, versions, and scheduling"
url: "/help/buuk/review-versions-and-scheduling"
updated: "2026-10-22T11:13:09.485Z"
---
# Review, versions, and scheduling

Every article keeps version history. Restore an earlier snapshot if a rewrite goes the wrong way.

## Review statuses

Turn on **Editorial workflow** in **Settings → General** when publish should wait for a second pair of eyes. The switch reads: editors submit pages for review, an owner must approve before they publish, owners can always publish. Only owners can change the setting.

With the setting on, a review bar appears at the top of the article editor. The page carries one of four status chips: **Not in review**, **In review** (amber), **Changes requested** (red), or **Approved** (green). The bar explains the rule inline: editors need approval before this page can be published.

- **Submit for review **puts your page into the review queue.
- **Request changes **sends it back for another pass.
- **Approve **is owner-only. It clears the page for publish.

> [!NOTE]
> Approving does not publish anything. An approved page still waits until someone presses Publish — review is a gate, not a trigger.

## Version history

Save is automatic, and each meaningful edit snapshots the article as a new version. Open version history to see the numbered snapshots and when each was made. Restoring an earlier snapshot writes its content back in and records it as a new version, so restoring is itself undoable.

## Scheduled publish

From the status menu in the editor, choose **Schedule…** and pick a date and time in the **Schedule publish** dialog. The editor shows a **Scheduled** label with the date. Until the moment arrives, the page stays a draft and stays out of search, the widget, and Ask AI.

A scheduled job publishes due articles. That run still checks the workspace plan limits — a Starter workspace at its published-article cap will not silently exceed it overnight. Scheduled publish is a replay of a decision you already made: you picked the content and the time.

## Worked example

You are rewriting the billing FAQ on Monday. Press **Submit for review**. An owner reads it, presses **Request changes**, you fix the refund wording, and the owner presses **Approve**. Because pricing goes live with the release notes on Wednesday at 9:00, you schedule publish for that slot instead of pushing it by hand. On Wednesday morning the cron job publishes the page, and the live URL is unchanged.

## Troubleshooting

**A scheduled page did not publish exactly on time**

Scheduled publishes run on a periodic job, so a page goes live within the next pass after the scheduled time, not to the second. If the page is still a draft, check that an owner approves it when approval is required, and that the workspace has not hit its plan limit.

**I approved but the page is still not public**

Approval clears the page for publishing; it does not publish. An owner or editor still presses Publish, or the scheduled time arrives.

**I restored the wrong snapshot**

Restore again from an earlier version. Every restore is recorded as its own version, so no step of the back-and-forth is lost.

## Related

- The publishing pass itself: [Write and publish an article](./write-and-publish-an-article).
- Who can approve and publish: [Members, roles, and groups](./members-roles-and-groups).
- External review inputs: [Suggested updates](./suggested-updates).
- What readers see once a page is live: [Publish your help center](./publish-your-help-center).