Version History and Approvals in Knowledge
Knowledge adds full version history and an optional approval step before publishing changes, especially relevant now that articles can be published publicly.
Publishing an article change in Knowledge has always been immediate — save, and it's live, for internal readers and, since the public help center feature shipped, potentially for customers too. That immediacy is fine for most edits and risky for the ones that matter, so today's release adds version history and an optional approval step before a change goes live.
How it works
Every article now keeps a full version history, the same model Drive uses — every saved change is a timestamped version showing who made it, with any prior version previewable and restorable. On top of that, any collection of articles can be configured to require approval before an edit publishes: an edit is saved as a pending draft, a designated approver is notified, and the previous published version remains live and unaffected until the edit is approved. Rejected edits go back to the author with an optional note, the same review pattern Content's editorial workflow uses.
Where this is useful
Version history alone is useful anywhere — recovering from an accidental deletion or an edit that didn't turn out as intended. Approval gating matters most for articles with real consequences if wrong: public help center content a customer might act on, compliance or policy documentation, or any collection where an editor's mistake shouldn't be one save away from being visible to everyone.
What's included
Version history, restore, and optional per-collection approval gating are live today, alongside the AI-generated summaries Knowledge already produces, which regenerate for the newly published version once an approved edit goes live. Scheduled publishing — approving an edit now but having it go live at a later date — is planned for a follow-up release.
Version history is on for every workspace by default; approval gating is available now on Knowledge plans that include the public help center feature, configured per collection.