Hey @Shannon Ng ,
Not sure if the plugin that Patrick recommended did the trick, but if not, my team here at K15t just added this feature into our Scroll Documents app. Again, another plugin so not always ideal, but the way the app works is you’re can define a page tree or a collection of pages in Confluence as one unit and then manage these pages together.
So in your case, you could containerize that parent page and its children, and then set the restrictions across all the pages inside of a single UI. If you need to update the view or edit restrictions, it then applies to all the pages at once. 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.
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)
Hi @Shannon Ng welcome to the community!
Unfortunately out of the box "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."
As you can see here: https://jira.atlassian.com/plugins/servlet/mobile?_ga=2.76599574.2019710780.1545018989-1760366298.1538725681#issue/CONFSERVER-5095
This has been an open ticket since 2006 and Atlassian still aren't sure if they will implement it or not!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
An option I just found from this answer: https://community.atlassian.com/t5/Confluence-questions/Making-edit-restrictions-inherited/qaq-p/889917
Is using power scripts for confluence, that would require buying a plugin though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not sure why Atlassian take so long to implement this request since it have been open for more than a decade. It is very painful to have to set the edit restrictions for every single.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you read the comments on the ticket, you'll see that there are good arguments for each side (to inherit or not inherit edit restrictions). Some people feel strongly each way. It's difficult to make a decision when opinions are so split. In the meantime a good option is using a plugin, therefore the users who want the feature can have it and those who don't want it, don't have it forced on them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the answer I linked above is the script and here is the marketplace app itself:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.