Available on Enterprise modules only.
Enterprise users can exercise tighter control when updating their Scribe guides 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.
Instead of instantly updating a Scribe when you make edits, you’ll work in a draft state. Changes are autosaved for you and other editors to review, refine, or approve — without affecting what end users see — until you choose to publish changes. The last published version remains live for all viewers until you explicitly click “Publish.”
The publishing workflow only applies to Scribes after they’re captured and saved the first time. Any Scribes you’ve just created will be published as soon as you share them.
Frequently Asked Questions
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 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.
Will viewers get notified when I publish?
- No, a notification will not be sent.