Control when edits go live with publishing changes

What’s new?

Teams can now have more control over when updates to their Scribes become visible by keeping new edits separate from publicly visible content. This intentional editing and publishing workflow ensures that your teams can collaborate on updating documents with confidence and prevent accidental sharing of incomplete or incorrect steps, ensuring work gets done right.

How does it work?

Instead of instantly updating a Scribe when edits are made, changes are now saved in draft mode. Edits are autosaved for you and other collaborators to review, refine, or approve — without affecting what viewers see — until you choose to publish. The last published version remains live until you explicitly click “Publish” to push updates.

Learn more here. Available for all Enterprise customers.

FAQs

What happens to the Scribes my team created before these states were introduced?

All existing Scribes remain published and visible just as before. Any future edits you make will be saved in a draft state and will require you to publish them.

Can I turn this feature off?

Yes. If you’d like edits to be published immediately — bypassing the draft state — Admins can disable publishing changes in Org Settings → Features.

Can I share a draft?

You can invite teammates to co-edit your draft, but the changes won’t appear in shared or published listings until you publish.

Can I revert to a previous version?

Absolutely. Use version history to restore drafts or published versions.