Confluence children page permissions
Asked by Jonathan Smith:

Hi all,

I am still struggling a little bit securing pages. ++View restrictions are inherited by children pages++, however in my example below, the child page allows the test user to edit. Why?

**I need someone to be blunt with me :)**

![HELP.jpg](/t5/image/serverpage/image-id/23857i503C33A758BBA725/image-size/large?v=v2&px=999 "HELP.jpg")


Answers:
author: Jonathan Smith
body: [@Bhakti Paranjpe](/t5/user/viewprofilepage/user-id/1188201) No special plug in. Created a new space because my personal space was imported via XML.

New space permissions: confluence-users have page add permissions (for this test).

Results: Restricted "can view" to Confluence Test user on **level 1 a** : Inherited**level 2 a** page allows user to edit.

Breaking the inheritance and choosing "editing restrictions" will make **level 2 a** page read only. This doesn't seem correct that I would have to restrict all children pages to carry down the read only permissions. Even if I restrict the parent with "Editing Restrictions", those restrictions don't carry down and the user can edit all child pages.

![a.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/24058iCE9FEF715D08D450/image-size/large?v=v2&px=999 "a.jpg")

comments: author: AnnWorley
body: Hi Jonathan,

I am coming in late but I hope I understand the thread. Please note:

[Page Restrictions](https://confluence.atlassian.com/doc/page-restrictions-139414.html):
> View restrictions are inherited, which means a restriction applied to one page will cascade down to any child pages. Edit restrictions are not inherited, which means pages need to be restricted individually.

Hope that helps,

Thanks,

Ann


author: Jonathan Smith
body: [@AnnWorley](/t5/user/viewprofilepage/user-id/502040) So "can view" is not necessary "read only". Apologies, I still have the SharePoint mind-set.

So there is no "read only" restrictions that will carry down. To restrict editing, I would need to break inheritance and choose "editing restrictions" for each desired children page.


author: AnnWorley
body: Yes, edit restrictions have to be applied individually as you say.


author: Bhakti Paranjpe
body: Hi [@Jonathan Smith](/t5/user/viewprofilepage/user-id/1254033),

Have you installed and configured any plugins that import spaces?

[This article](https://confluence.atlassian.com/confkb/inherited-page-permissions-are-not-being-respected-933080204.html) suggests that, post import, such plugins delete all rows in the CONFANCESTORS table, which are used to determine inherited page permissions.

The article gives an example of a specific plugin, but there could be other plugins who might cause the same issue.

Please check.


author: Fabienne Gerhard
body: Hi [@Jonathan Smith](/t5/user/viewprofilepage/user-id/1254033)

my first idea would be - is Confluence Test part of a group that has special space permissions?

Like they mentioned [here](https://confluence.atlassian.com/doc/permissions-and-restrictions-139557.html).

![grafik.png](https://community.atlassian.com/t5/image/serverpage/image-id/23872iB7ED5D6F3A5D1A4F/image-size/large?v=v2&px=999 "grafik.png")

comments: author: Jonathan Smith
body: Confluence-users is the only group in space settings. They have page add permissions. I would still think restricting a page to view only would trump the add permission in space permissions.

Here is the page restriction break down and results for Confluence Test user.

**Any child page under Permissions Test (Can View) would have page edit ability unless I broke inheritance and switched to "editing restricted". Is this how it is supposed to work?**

![help1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/23922i7C4A86D709D8C1B6/image-size/large?v=v2&px=999 "help1.jpg")


Tags: permission