...
Message | Further explanation | ||
|---|---|---|---|
| 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:
💡 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.also note the section below describing the behavior of the app in case of view restrictions. | ||
| 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. |
...
The “no view permission” case
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.
💡 View restrictions of the starting page of your edit permission inheritance or any ancestor of this starting page to not influence the way the app works.
Advanced 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:
|
...
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. | There are a couple of things to check:
|
How to migrate from Server to Cloud? |
...