Publish approved Confluence content to spaces and remote instances
The problem
Content is approved in one space, then someone manually copies it to a downstream wiki — or forgets. The approved version and the published version diverge within a week.
How Churrie Page Management and Sync helps: configure publish targets once. After quorum and final approval, Publish copies approved content to internal Confluence spaces and pushes through Churrie Sync connectors to remote instances — in one action.
Integrated publish + sync
- Publish to Confluence spaces — view-oriented published copies in configured space keys
- Publish to sync destinations — approved payload sent through existing destination routes
- Block sync while locked — draft and in-review content does not leak outbound (default on)
Typical flow
- Author completes draft and submits for review.
- Reviewers approve; final approver signs off.
- Approver clicks Publish.
- Content appears in publish spaces and/or arrives on remote instances via Churrie Sync.
Workflow-only? Use publish spaces alone. Sync-only? Use destinations without workflow. Together they are strongest when policy requires approval before distribution.