What is it?
The Edit Permission Inheritance App allows to inherit the edit permissions defined on a page down to all of its child pages. The app does not introduce an additional permission level. It basically copies the edit permissions to all child pages and takes care of added pages.
Legal documents
Getting started
Please follow the below steps to define your first edit permission inheritance:
Step | Screenshot |
|---|---|
Navigate to the parent which shall be the starting point of your "edit permission inheritance". | |
Define the edit permission as needed | |
Click on the Edit Permission Inheritance Icon |  |
Turn on "Edit permission inheritance" at the top of the dialog. |  |
Select additional options if needed (for details refer to the next section). |  |
Click "Apply". |  |
The app now starts inheriting the edit permissions to all descendants of this page.
The app is applying the inheritances intentionally slow. Please consider ~1 second per descendant before the inheritance is completed.
Due to the Confluence Cloud architecture you might not see inherited edit permissions on descendants without reloading a descendant page.
The edit permission inheritance options
Option selected | Inheritance behavior |
|---|---|
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. |
Understanding the way the app works
What the app does:
The app adopts all edit permission on child pages to match the parent page (the page the edit permission inheritance starts). The options selected modify the way the app does this.
When pages are added to the branch covered by an "edit permission inheritance" their edit permission set is modified to match the inheritance.
When pages are moved into a branch covered by an "edit permission inheritance" their edit permission set is modified to match the inheritance.
The app uses the closest active "edit permission inheritance". This allows you to define additional "edit permission inheritances" below other ones.
What the app does not:
The app does not hinder you from changing the edit permission on child pages. However when you re-apply the "edit permission inheritance" your changes might be lost depending on the selected options.
The app does add an additional layer of permissions.
Some additional use cases
Use case | Solution |
|---|---|
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. |
Frequent support cases
Observation/Question | Explanation/Answer |
|---|---|
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. | 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. |
To be continued… |
Getting support
Please use our ticketing system to create a support ticket regardless whether you found a bug, have a feature request or questions.