Inherited restrictions only for viewing - not for editing

This question is in reference to Atlassian Documentation: Page Restrictions


We set up page restrictions.We want to manage our meeting minutes. All Project members should be able to see (outside the project nobody should be able to see). And 3 people should be able to change the minutes.


So we set it up:

Some people should be able to view and a part of them should be able to edit.

If you create a sub-page the restrictions should be Inherited.

But it seems, that only the view rights Inherited into the sub-pages. As all user, who have viewing rights can edit the sub page (whereas the main page can only be edited by some defined ones).


It that the correct behaviour or is it a bug?


thank you

1 answer

Yes, it is working as designed. However, there is an issue that discusses changes - CONF-5095. I would add that it is one of those things that have use cases that need both behaviors.

Thank you for the link Bob. I've been wracking my brain trying to understand why child pages weren't inheriting editing restrictions. Just when I think I understand how Confluence works, I find myself bitten again by another "feature".  

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Feb 06, 2019 in Confluence

Try out the new editing experience

Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...

783 views 33 5
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you