Restriction inheritance for folders is wonky

[Björn Busch-Geertsema]

Hi,

it seems that the permission/restriction inheritance of folders is really wonky. Is there some documentation for when restrictions get inherited or not?

To illustrate I took a screenshot of the "Inspect permissions" screen.

Our structure looks like this:

• Level 1: My Confluence Space (censored in screenshot)
  • Level 2: Folder "Public"
    • Level 3: Folder "Produkte"
      • Level 4: Folder "My Product Name" (censored in screenshot)
        • Level 5: Page

For some reason, the restrictions on level 2 and level 4 are deemed to be "irrelevant" and do not affect their children, but the restrictions on level 3 do?

When we put edit restrictions on level 3 they affect the page on level 5.

Why is this so random? Is there a way to change this behavior?

Any help appreciated. This just seems completely broken.

[Edson B [Atlassian Support]]

Looks like this is the documentation you're looking for:

• https://support.atlassian.com/confluence-cloud/docs/add-or-remove-page-restrictions/#Interpret-content-level-access-settings

Unlike view restrictions, if someone is restricted from editing on parent content, they'll still be able to edit any child content, unless they're restricted from editing on the specific child content.

[Björn Busch-Geertsema]

Thanks. I did not find that when I looked for it. It does explain the behavior, but you have to admit this is completely non-sensical.

Why would inheritance for permissions work differently for viewing and editing permissions. 

What is the purpose in even allowing to set edit permissions on a folder???? As far as I can tell there is no use case where this might have any benefit at all.

Getting more frustrated with Confluence every day…