Space Publisher for Confluence helps teams keep working content separate from published content by publishing pages from one Confluence Cloud space to another.
What it does
- Pair a source space with a destination space.
- Publish one page or a page subtree.
- Keep mapped destination pages in place when publishing later updates.
- Preserve the published hierarchy.
- Track whether source content has changed since it was last published.
- Detect destination edits before overwriting them.
- Keep destination permissions independent from the source.
Configure a space pair
Open the source Confluence space, then go to Space settings and open Space Publisher.
Choose the destination space and save the pairing.
A source space can have one active destination space. The destination must be different from the source.
Publish a page
Open the source page and select the page actions menu (•••), open Apps, then choose Publish to destination.
Review the destination and page status, then choose Publish page.
Publishing runs in the background. You can review status from the Publishing page in the source space.
Publish a subtree
From the same Publish to destination action, choose Publish subtree to publish the selected page and its descendant pages.
The app preserves the mapped destination hierarchy. Existing mapped pages are updated rather than duplicated.
Destination edits
If a destination page has been changed since the app last published it, Space Publisher warns before overwriting it.
Publishing from the source is one-way. Destination edits are not synchronized back to the source.
Permissions
Space Publisher does not copy source-page permissions into the destination. The destination space's own access model remains authoritative.
A user must have the Confluence permissions required to perform the requested publication.
Deletions
Space Publisher does not automatically delete destination pages.
If a source page is deleted, the previously published destination page remains.
If a mapped destination page is deleted, the app marks that mapping as orphaned so it can be republished explicitly. Republish other pages that link to the missing destination so their links use the replacement page.
Publishing limits
Each publication supports up to 100 pages. Larger subtrees are rejected before any destination content is changed. A source space supports up to 2,000 mappings. The dashboard shows ten mappings at a time.
Reset a pairing
A source-space admin can explicitly reset the pairing and mappings from Space settings. Reset leaves destination pages in Confluence. Selecting the same destination again can produce title collisions with those retained pages.
Data handling
Space Publisher is built on Atlassian Forge. It does not use an external content backend or external analytics service.
See the app-specific Privacy Notice for details.
Support
For help, contact hello@renewalhub.co.za.
Publisher: Renewal Hub Digital Services Website: https://www.renewalhub.co.za