Capable Publishing: Structured Workflows for Confluence Content Delivery
Confluence is brilliant for drafting content, sharing ideas, and collaborating on projects. But when it comes to delivering that content - whether to a public site or an internal documentation area - standard Confluence is missing two key capabilities:
- Approval Workflow: A structured system where designated approvers review and sign off on pages. Each action is tracked to maintain a clear and auditable history of changes and decisions.
- Publishing Pipeline: A mechanism to seamlessly transition approved content into a finalized, viewable space - distinct from the drafting environment - whether the target destination is public-facing or private.
This workflow was missing… until now!
We solved the first problem when we launched our Approval Tool. Now we’ve solved the second, with our new Publishing Tool, which completes the journey from draft to delivery.
How It Works
Before we show you the tool in action, this animation offers the clearest explanation of what the Publishing tool does 👇
Draft in a private space
Write and revise until the content is truly ready, away from public view.
Request approval
Configure automatic approval requests when a page is created, or manually add reviewers at any point. Automatic publishing on approval can also be set in the same area.
Publish the page
Once approved the page can be automatically published to a designated publishing space. If preferred, automatic publishing can be turned off, allowing you to bypass the approval step altogether and publish directly.
Share or restrict access
If you're using Confluence public links or third-party tools like Refined Wiki, the page is made public instantly upon publish. For internal content, you can assign publishing spaces with restricted access, ensuring only specific users can view (not edit) the content.