Heirloom: Inherit Edit Restrictions
Confluence Cloud passes view restrictions down the page tree, but not edit restrictions. Heirloom does: set who can edit a parent page, and every page below it follows.
Get started
- Install Heirloom from the Atlassian Marketplace.
- Open the parent page whose editors you want to pass down. Set who can edit it in Confluence as usual (in the page's Share or Restrictions dialog).
- Choose ••• (More actions) > Apps > Inherit edit restrictions.
- Pick a mode (see below) and, if you want, tick the branches to leave unchanged.
- Click Preview to see what would change. Then click Turn on inheritance.
Keep the dialog open until it says Done. Large page trees are processed in steps while the dialog is open. If you close it early, nothing breaks: open it again and click Save and re-sync.
Modes
Add only (recommended)
Every page below gets at least the editors of the parent page. Editors that were added directly on a child page are kept. Heirloom never removes access in this mode.
Mirror
Every page below gets exactly the editors of the parent page. Editors that exist only on a child page are removed. Run a preview first.
What happens after you turn it on
- All levels: pages at any depth below the parent are updated, including pages inside folders. Folders, whiteboards and databases are passed through but not restricted.
- New and moved pages: a page created in the tree, or moved into it together with everything below it, gets the parent's editors automatically, usually within a minute.
- Parent changes: if you change the parent page's edit restrictions, the rule is marked needs re-sync. Open the dialog and click Save and re-sync to update the pages below.
- Nested rules: if a page below has its own rule, the nearest rule above a page wins.
- Excluded branches: a branch you leave unchanged is skipped completely, including everything below it.
- View restrictions are never read or changed. Heirloom only works with edit restrictions.
Why the Heirloom app is listed as an editor
Confluence only lets an app change edit restrictions that include the app itself. So when Heirloom restricts a page, it also adds itself to the editors of that page. This is what allows new pages to be updated automatically. Removing Heirloom from a page's editors stops Heirloom from updating that page.
Pause or remove a rule
Open the dialog on the parent page and click Pause or Remove rule. Pausing or removing never changes existing restrictions: pages keep the editors they have.
For site admins
Go to Settings (Confluence administration) > Apps > Heirloom edit inheritance to see every rule on the site, with its mode, status, last sync and pages that need attention. Admins can pause or remove any rule there.
Who can use it
Anyone who can edit a page can set up inheritance on that page. Heirloom checks that the person can edit the page before a rule is turned on, changed, paused or removed. After that, new and moved pages are updated by the app itself.
Limits
- Pages the app cannot see are skipped and reported in the result.
- The dialog shows the first 10 planned changes in a preview, with totals for the whole tree.
- Heirloom is for Confluence Cloud only.
Uninstalling
Restrictions that Heirloom set stay on the pages. The rules are deleted together with the app's data by Atlassian.
Questions? See Support.