This question is in reference to Atlassian Documentation: Page Restrictions
I have a structure setup under a space for IT. I've granted everyone view permissions to the space. I've granted the IT group edit permissions on the top page and then created a bunch of child pages. The IT group can't edit anything. What's the deal? It seems like only space permissions apply to allow editing and not page permissions.
From this page- https://confluence.atlassian.com/doc/page-restrictions-139414.html
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." (my bold)
So how are people handling large amounts of pages? I only want people to be able to view our pages, and only some people to edit a subsection of the space. If one of those subsections has 1000 pages underneath it, I have to manually go to all 1000 pages and grant them edit?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yep my problem too. My solution is pretty bad but I'm adding it here to show that there's a problem. Editable pages were moved to a separate space where users had space edit permissions. I then added a redirect from the initial uneditable space to the new editable space.
Looking forward to hear a better solution, or plans to make inheritance for edit restrictions an option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, if the amount of pages are that large, put it in a separate space and use the space permissions as Adrian suggested.
If you don't have a scenario with external registration from the internet, for example in a corporate environment, where you know your users, I suggest to just leave it open to edit for anyone. People are scared at first, that some unauthorized person is going to edit their pages, from my experience this rarely happens. After all, everything is versioned and tagged with names / dates, so if there will ever be an incident, you can just revert the page and give the person a call.
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.