Is Page Branching available on Confluence Cloud?
Yes! This space documents Page Branching for Confluence Cloud. If you are on Server or Data Center, see Page Branching (Server/DC).
How is Cloud different from Data Center?
Cloud runs as a modern Forge app. The main interaction lives in the page byline right below the title, plus a Forge Branches space page that lists every branch in a space. All the core workflows you know – create, sync, merge, delete, bulk merge, and conflict resolution – are there, redesigned for the new Confluence editor.
Where are branch pages stored?
Branch pages are real Confluence pages, kept under a parent page titled Branches in each space. That means your existing search, permissions, and backups apply automatically – no separate data store, no surprises.
Who can create branches?
Any user with create and edit permission on the original page can create a branch, as long as Page Branching is enabled in the space.
How are branches protected?
Branches use Confluence’s native permission system. They inherit access from the Branches parent page in your space, so whoever can see and edit that area can collaborate on branches. If you want to narrow access further, simply add a page restriction on the Branches parent or on an individual branch – just like on any other Confluence page.
What about attachments and labels?
Page Branching focuses merges on page body content, which keeps merges predictable and safe. Attachments and labels stay on the original page as a single source of truth, so they are never accidentally duplicated or overwritten by a merge.
Why does the byline say my branch is outdated?
The original page was updated after the branch was created or last synced. Click Update on the branch to pull in those changes, then merge.
Can I compare a branch with the original before merging?
Absolutely. Open the branch byline and choose Diff to see a rendered side-by-side comparison. See Comparing branches for details.
Merge failed or shows a conflict – what now?
No problem – have a look at Merge Conflicts. Update the branch, choose how to apply the overlapping edits, and merge again.
What happens to branches after merge?
That depends on your space settings. By default, merged branches are archived under Branches so you keep a history. Space administrators can switch to delete for a leaner page tree – see the Administrator Guide.
Still need help?
Contact Lively Apps support through the channel listed in the footer below, or from the app listing on the Atlassian Marketplace. We are happy to help!
Useful links
-
Our Service Desk is the best way to reach us if you have problems or would like to suggest a new feature.
-
Contact us by email via support@livelyapps.com.
-
Have a look at our other apps and discover more helpful tools