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 Added

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

Image Added

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.

Delay the application of the inheritance

Delay the start of the inheritance process by 2 minutes (could be subject to change). This option can be used in case the app runs into conflicts with other apps.

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

• x indicates the number of sub-inheritances under the current one. The first page Ids holding sub-inheritances are shown on brackets. A sub-inheritance stops the edit permission inheritance into that branch.

• y indicates the number of pages at which the application of least some edit permissions has been omitted due to missing view permissions of a user or group (for details see this chapter). The first page Ids at which this happened are shown in brackets.

💡 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.

💡 The browser console shows all sub-inheritances and all page Ids at which the application of edit permissions has been omitted.

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 want to inherit the edit permission but want to exclude a branch.

Define two edit permission inheritances. One on the head of your “tree” the other one on the head of your “branch”. The edit permission inheritance of the “tree” will skip the “branch”.

I want to inherit an edit permission for the whole space.

Despite the fact that the can handle this you should consider to change the space settings instead.

I want to know on which pages an edit permission inheritance is configured.

Perform an advanced search like the following:

https://example.atlassian.net/wiki/search?cql=editinheritenabled%3D%22true%22

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

over-stress 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:

1. 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.

2. Please also check that the page missing an inherited edit permission does not have a view restriction hindering this as described here.

3. A sub-inheritance on a lower level descendant will stop the inheritance into that branch.

How to migrate from Server to Cloud?

Edit Permission Inheritance Migration Guide