Restrict access to user groups so that they do not modify the basic structure created

[Jems GOMEZ _X_]

Hello,

We're having trouble securing a page structure.

We'd like to block modifications to certain pages within the structure that contain child pages, but this isn't working.

What we'd like to do is :

Parent page [Blocking modification to prevent adding a Child Page 4] (User group is restricted to read only)
=> Child Page 1 [Allow modification for add more Child Page, 1.3, 1.4 etc...]
      => Child Page 1.1
      => Child Page 1.2
      => Child Page 1.3 [Authorized to add]
=> Child Page 2 [Allow modification for add more Child Page, 2.3, 2.4 etc...]
      => Child Page 2.1
      => Child Page 2.2
      => Child Page 2.3 [Authorized to add]
=> Child Page 3 [Allow modification for add more Child Page, 3.3, 3.4 etc...]
      => Child Page 3.1
      => Child Page 3.2
      => Child Page 3.3 [Authorized to add]
=> Child Page 4 [Not auhtorized to add but works] 

Is this because the user group was added to the access rights at the space level with the right to modify ? Because even with restrictions added to Parent Page, users are still able to create child pages like Child Page 4 within the restricted pages.

Thank you for your help or answer

[Barbara Szczesniak · Accepted solution]

@Jems GOMEZ _X_ Please refer to this page for a description of how view permissions and edit restrictions are inherited from the parent: https://support.atlassian.com/confluence-cloud/docs/add-or-remove-page-restrictions/ 

[Jems GOMEZ _X_]

Hello Barbara,

Thank you for your response.

Unfortunately, this doesn't solve our problem.
Even if we try to prevent the user group from modifying certain pages by giving them view-only access, they still manage to create pages within the structure we want to lock down.

It's as if the permission granted at the space level overrides all restrictions on child pages.

[Barbara Szczesniak]

@Jems GOMEZ _X_ The ability to Add a page is a space permission and has nothing to do with the content-level permissions or restrictions. 

On the page I linked to, it says:

How inherited restrictions work

If someone can’t view a parent content item, they won’t be able to view any child content items under it. In this sense, a view restriction has been added to the parent item that inherits down to all content items nested under it, without exception.

Editing doesn’t work this way. Even if someone is restricted from editing a parent item, they won’t automatically be restricted from editing the child content.

However, if someone is restricted from editing at the space level, they will be restricted from editing any and all content in that space.

This refers to the ability to edit a page that already exists. The last sentence above doesn't make much sense, however, as the only way to restrict editing at the space level is to not grant the Add permission—there is no explicit Edit permission at the space level. Basically, if you give someone the ability to add pages to the space, they can add them anywhere in the space.

From https://support.atlassian.com/confluence-cloud/docs/what-are-space-permissions/ :

Add

User can add new pages, live docs, blogs, comments, or attachments in your space. You can assign "Add" permissions individually by content type. If assigned, the user can also edit all of that content type in your space, except when restricted from doing so on individual content items.