Manage Page-level Workflows

If you manage documentation in Scroll Documents collaboratively, you may have faced challenges in tracking changes made by different authors or ensuring that all edits are complete before publishing or saving a new version.

The workflow feature in Scroll Documents helps with this by giving you better visibility into the status of pages and allowing you to treat pages differently based on their status when saving a version or publishing content.

What Are Workflows?

A workflow helps teams manage changes on their content through defined statuses that are applied to every page in your Scroll Document. You can apply a workflow to a document to ensure that changes are reviewed and completed before they are finalized. Scroll Documents offers two types of workflows:

• Simple workflow: A two-step workflow where pages can have the statuses Draft and Approved

• Approval workflow: A three-step workflow where pages can have the statuses Draft, In Review, and Approved

When saving or publishing a document version, you can either include all pages as they currently exist in Confluence or apply workflow rules. For pages that are not ready, these rules let you:

• Exclude pages from the saved or published version.

• Use the last approved version of a page instead of an incomplete draft if previous versions exist. This is referred to as a fallback.

What’s Next?

This section of the documentation will walk you through the individual steps of working with workflows in Scroll Documents: