Confluence inheritance page restrictions
Asked by Simon Rummel:

Hi all,

I would like to restrict the edit-option for a parent page and all its child pages. As described in the documentation "View restrictions are inherited, which means a restriction applied to one page will cascade down to any child pages."([see here](https://confluence.atlassian.com/doc/page-restrictions-139414.html)).

I would expect that when I set a parent page as "Can View", it is not be possible to edit child pages. Why are the settings not inherited and have to be set manually page by page?

Regards

Simon


Answers:
author: James Dellow
body: [@Simon Rummel](/t5/user/viewprofilepage/user-id/2471717) I think the reason for this approach is that for a user to be able to edit a page, they first have to be granted edit (add) permissions in the space. Restricting who can view a page or set of pages doesn't change the underlying space permissions. So the ability to restrict who can edit a page is about supporting exceptions.

However, can you tell us more about your use case and why don't you restrict this through the space permissions so that the group you don't want to be able to edit simply aren't given edit rights?


author: Bill Bailey
body: I think you want to restrict editing not set can view.

comments: author: Simon Rummel
body: Yes, you're right. I want that users can only view one parent page and its child pages. But I do not want to change the restrictions page by page (as this is a lot of redundant work).


author: Merve Nur Bas
body: Hey Simon,

when a user cannot view a page, then he/she also cannot view its child pages. Pretty clear I guess. Edit options are rather different. You may want a static home page (or something similiar) which can be edited by only a space admin and still want to be able to let other team members edit the child pages.

I hope I could explain it properly.

My best

Merve


author: Simon Rummel
body: We have got several parent pages representing different customer projects. Users shall be able to edit some parent pages and its child pages.

Now if I want to set one specific parent page and its child pages as read-only, meaning that no one is able to edit a page, I would expect that I only have to change the restriction for the parent page and it will be inherited by its child pages. But this is not the case..

comments: author: Merve Nur Bas
body: If you do not have to "collect" all of these customer projects in one single space you could create dedicted spaces for each project and manage permissions on space level - like "view-only" permissions for confluence-users in that specific space.

My best

Merve


author: Shannon Meehan _K15t_
body: Hey [@Simon Rummel](/t5/user/viewprofilepage/user-id/2471717) ,

Depending on how you're managing the customer project pages, our [Scroll Documents app](https://marketplace.atlassian.com/apps/1217608/scroll-documents-for-confluence?hosting=cloud&tab=overview&_ga=2.23634488.360078089.1573381583-1743865367.1572885248) might help you out with this.

With the app you can define a parent page and all of its children as one unit of content which then becomes a single document. We provide a separate restrictions UI for this document where you can update the view / edit restrictions in one go, all in one place.

So in your case, if you're trying to make the page tree read-only, you would just need to change the edit restrictions of the document to view-only and all of the pages of the document would respect that. You can [read more about it here](https://www.k15t.com/blog/2019/11/how-to-manage-restrictions-across-multiple-confluence-pages).

Of course, this isn't the only functionality of the app. You can also version page trees, set workflow statuses, send read requests, and export to PDF or Word with our Scroll Exporter apps, and more.

If you have any questions, we'd be happy to help or show you a demo of the app. Just get in touch with us: hello@k15t.com.

Cheers,

Shannon (K15t)


Tags: child-page

inherit

permission

restriction