Page Comparison

Navigate to the parent which shall be the starting point of your "edit permission inheritance".

none

Define the edit permissions as needed

none

Click on the Edit Permission Inheritance Icon

Image Modified

Turn on "Edit permission inheritance" at the top of the dialog.

Image Modified

Select additional options if needed (for details refer to the next section).

Click "Apply".

None

When you hit the apply button all descendants get the same edit permissions as the parent page. Additional edit permissions are kept.

Remove additional edit permissions during inheritance

Same as "None" but additional edit permissions on child pages are removed.

Always grant an edit permission to the creator of the page

Same as "None" but the creator of a page will always get an additional edit permission.

Only apply edit permission changes not the whole set

Same as "None" but only the edit permission changes done on the parent page are inherited not the whole set. This might be useful in case you changed the permissions of child pages and don’t want to loose those changes.

Example: in case and edit permission was already present on the parent page before the change of permissions and is still present after the change but the current child page does not have that particular edit permission it will not be added in case this option is selected as nothing changed on the parent side.

This message indicates that an edit permission inheritance is still being processed on this page. You should calculate with ~1 second per descendant.

💡 The message is NOT updated. You have to close the dialog and open it again.

This message indicates that the edit permission inheritance was successful:

• All descendants have been covered

• No error was thrown during the process

💡 Please remember that descendants might still have their own permissions. This message does NOT mean that all child pages have the same set of edit permissions.

💡 Please note that only users and groups can get an edit permission in case there is no view restriction hindering this. Example: a page restriction which only allows user A to view the page will not get an inherited edit permission for user B as an edit permission always means a view permission.

This message indicates that the edit permission inheritance was not successful or that descendants exists which have not been covered yet etc.

The message also indicates the number of descendants which might not be in compliance and indicates the page Ids of the first 5 descendants which do not comply.

💡 You can use the offered link “Fix those pages” to fix the affected pages.

This message indicates that you can’t perform an edit permission inheritance as you don’t have a personal edit permission (an edit permission for your name). You have to add a personal edit permission first and then come back.

💡 The personal edit permission is needed due to technical reasons in Confluence Cloud.

I started an inheritance on a page with many descendants. It seems to take a lot of time before all child have the proper set of edit permissions.

The app is intentionally slow not to overstress the interface to Atlassian Cloud. Please consider something around 1 second per descendant/child page.

I checked whether a child page got the inheritance - but it has not.

There are a couple of things to check:

• Please reload the page and check again. Confluence Cloud is very special in reloading / caching information and simply does not notice the change although it already happened.

• The app does not inherit edit permission to pages which at which a view restriction hinders this. Example: you want to inherit the edit permissions of page 1 which allow the users A and B to edit the page. On of the descendants (page 1.1) however is only viewable for user A. The app will then not grant B an edit permission on 1.1 as this edit permission would allow user B to view 1.1 - which would be a security issue.

How to migrate from Server to Cloud?

Edit Permission Inheritance Migration Guide