How can edit restriction be distributed / inherited to child pages Edited

Is there a way do (automatically)  distribute a "not edit" restriction to all child-pages of a certain page? Or do I have to change that attribute at each single page manually?

2 answers

0 votes
Davin Studer Community Champion Jan 25, 2018

View restrictions are inherited, but edit restrictions are not. You must manually make the restriction. There are ways to automate it, however. For a while we used the Confluence Command Line Interface to do this. You could set up a scheduled task that would run on a certain period that could apply the edit restriction to a page and all its children. It worked well for us for a while till we decided that we would change up how we do some stuff and it was no longer needed.

I have the same concern. When we need to restrict edit permission on one page, we would in general restrict on all its child pages. Is some one knows the reason for what Altassian made the different behaviour between View and Edit functions ? Would be it better Altassian make the evolution so that the same behaviour is applied to these two functions ? That's to say, by default, restrictions are automatically inherited ?

Davin Studer Community Champion Aug 31, 2018

View restrictions being inherited makes sense because how would you even see a child page in the nav tree if you cannot see the parent. As for edit restriction being inherited it doesn't make sense for them to assume you want it to be inherited. I have many pages that have a restriction on a parent page, but I would not want the children to have the same editing restriction. So, the functionality as it is intended, it's logical, and is not a bug.

However, it might be nice if they added a checkbox or something when setting and editing restriction to opt into having is cascade down to the children as well. But, it doesn't seem that they have the desire to make that change. Also, there are a couple add-ons that can give you that functionality. My hunch is that one of the reason for them not adding it in is because it would essentially make those add-ons unnecessary. Which is great for customers, but not so great for the people that spent time coding the add-on to add the functionality that Confluence doesn't have. Below are a couple add-ons that can give you inherited edit restrictions.

ScriptRunner for Confluence

Confluence Command Line Interface (CLI)

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 24, 2018 in Confluence

Atlassian Research opportunity with Confluence templates

Do you use templates with Confluence? Take part in a remote 1-hr workshop. You'll receive USD $100 for your time!   We're looking for people to participate in a   remote 1-hr workshop...

1,524 views 25 14
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