nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Making edit restrictions inherited

Ng Ken Jo

Hi, i'm trying to find out how I can can lock an entire sub-tree from being edited, I refer to this page: https://confluence.atlassian.com/doc/page-restrictions-139414.html

Which says "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. "

Is there a reason why Edit restrictions do not cascade with no option for them to do so? And is there any workaround to make edit restrictions inherited as well?

Accepted answers

Grigory Salnikov_0hffsd

Hi!

It's an interesting and quite old question. Discussion concerning this functionality dates back to 2006. You might be interested to know what other people think, please, take a look:

CONFSERVER-5095

The're a lot of pro- and counter- arguments.

Hope this helps.

All comments

Grigory Salnikov_0hffsd

Hi!

It's an interesting and quite old question. Discussion concerning this functionality dates back to 2006. You might be interested to know what other people think, please, take a look:

CONFSERVER-5095

The're a lot of pro- and counter- arguments.

Hope this helps.

Grigory Salnikov_0hffsd

Oh, there's a bunch of workarounds and suggestions as well.

Ng Ken Jo

Wow seems I opened a big can of worms, thanks for the info i'll have a look.

Davin Studer

Power Scripts for Confluence (free app) was just released recently and I set this script up in our environment. I've set the script to run as a listener (see below screenshot). Whenever a page is created, updated, or moved and is under a certain tree in the navigation an editors restriction will be added to the page for a specified group.

string parentPageSpaceKey = "{spacekey}";
string parentPageName = "{page name at top of tree}";
string editGroup = "{group name}";

integer parentPageId = getPage(parentPageSpaceKey, parentPageName);
string parentPageIdStr = formatNumber(parentPageId, "#");

string cql = "(space=\"" + parentPageSpaceKey + "\" AND title=\"" + parentPageName + "\") OR (ancestor=\"" + parentPageIdStr + "\")";
number[] allPages = selectPages(cql);

for(number aPage in allPages) {
    if(aPage == parent) {
        addGroupToContentPermission("Edit", id, editGroup);
        break;
    }
}

Shannon Meehan _K15t_

Hi @Ng Ken Jo ,

As Davin said, there are some apps out there that can help you accomplish this. One of those is our Scroll Documents app that allows you to define a page tree as a single unit – a document – and then manage those pages together.

One of the management features is being able to set the restrictions on the page tree from a single UI. When you update the view or edit restrictions for the document, those updates reflect one all of the pages – edit restrictions as well. You can read more about it here.

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.