...
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. 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. |
Understanding the way the app works
...
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.
...
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. | ||
I want to know on which pages an edit permission inheritance is configured. | Perform an advanced search like the following:
|
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… |
...