Page Tree Edit Restrictions for Confluence: copy edit restrictions to child pages
Confluence passes view restrictions down to child pages, but not edit restrictions, so admins set them page by page. Page Tree Edit Restrictions copies a page's edit restrictions (people and groups) to the pages below it in one step, with a preview and an undo.
Requires Confluence Standard or higher (page restrictions are not available on the Free plan). Free for up to 10 users; see Marketplace for tiers. Runs on Atlassian. For Confluence Cloud.
Getting started
- Open the parent page, choose the ... menu, then Apply edit restrictions to child pages. The page you are on is the parent.
- Wait while the app reads the tree. It then shows how many pages already match, how many would change, and which ones, with each page's current edit restriction next to the new one. Preview writes nothing.
- Choose how far it goes: all levels, direct children only, or the first few levels. Untick any listed page you want to leave alone.
- Press the apply button. Each selected page gets the same edit restriction as the parent. A page that cannot be changed, for example because you may not edit it or one of the people being copied cannot view it, is listed with the reason, and the other pages are still processed.
What it changes
For each selected page it sets the edit restriction to the same people and groups as the parent. Changes run with the permissions of the person who presses the button, so Confluence's own rules about who may change a page's restrictions apply.
What it does not do
- View restrictions and page content are not touched.
- Only pages are changed. Folders, whiteboards, databases and archived pages are skipped.
- One run handles up to 500 pages below the page you open it on. For a bigger tree, run it on smaller branches.
- The parent must have an edit restriction to copy, and you must be able to edit the parent. Otherwise apply is turned off.
- Folders at the deepest level of a very deep tree are not searched for pages below them. The screen says so.
- Preview is available to everyone. Applying and undoing need an active license.
Undo
Before each page is changed, its previous edit restriction is saved. Undo last apply puts the changed pages back, including pages that had no restriction. A page whose restriction someone changed after your apply is left as it is and reported, and a page that cannot be restored is listed so you can retry. Saved copies are kept for up to 90 days; after that Undo is no longer available for that run.
Permissions and data
Runs on Atlassian and does not send data elsewhere. It stores the saved restrictions (account IDs and group IDs) in the app's Forge storage on your site, and reports stored account IDs to Atlassian under the Forge privacy rules. See the Privacy Policy.
Support
Use the Support page or write to support@hullspark.com. Include the page ID of the parent and what you saw. Do not send page content.