This question is in reference to Atlassian Documentation: Page Restrictions
What does "Edit" mean exactly? I'd like to allow users to "Lock to Edit" and upload new revisions, but not delete. Would I accomplish this by restricting their ability to edit?
If you look at Space tools --> Permissions, in the Pages column is Add and Delete. In this case, Add means create and change pages, and Delete means delete pages.
In Page Restrictions, when you restrict editing to someone (or a group), the extent to which they can edit is still governed by the space permissions.
Thank you, that is exactly my question, differentiating between Atlassian's jargon: restrictions vs permissions.
Apparently I am not a Space Admin because this is not available to me. Now that I know, I can request that the space admin changes the "Permissions" NOT "restrictions" on these pages. Thanks again.
Sounds like you 'got it', but since you didn't say it - and Milo and Davin did give great answers by the way, good articulation of this topic - one thing I do to help our internal users get up to speed on this distinction is to include the adjectives for each, that is:
1.) It is SPACE Permissions. Keep in mind one has to first be in the space to have access to see/do anything..
2.) It is PAGE restrictions, which takes from the population of those already in the space to determine who can view or edit particular pages. As you may know, 'View restrictions' are inherited by any child pages, those pages that lie beneath the view-restricted page in the hierarchy, so don't have to be added for numerous pages if you set up your page hierarchy right.
NOTE: Currently edit restrictions are not inherited (there is a feature request for that), but keep in mind that if a view restriction is in place, edit restrictions will be limited to that smaller group. You CAN further define who can edit from a view-restricted group for a particular page or page hierarchy from the view restricted group.,
Or, if there are no view restrictions sets, you can limit editing via the page-level edit restriction to an individual or individuals for that particular page. A use case for the latter is 'everyone' can see the home page (no view page restriction), but only an individual or two are listed via page restriction as editors and can change home page content.
Finally, consider asking for space admin rights. We have a few hundred wikis and for practicality and efficiency, we allow the team owning the wiki to determine who should have space admin rights and have had no issues - the 'reward' seems to be much greater than the 'risk' in this case, and it is a way of 'democratizing' and gaining efficiency for a tool that after all, is built for collaboration.
Hope this helps. Good luck!
"Edit" means exactly that ... those who can change the contents of a pge. Edit restrictions says among those who already have edit access to the wiki space via space permissions can edit this specific page. By default anyone who has edit access to the space can edit any page. This will limit that to a subset for the particular page that the restriction is one. It is possible to give an edit restriction to a page for a user that doesn't have edit access to the space. In that case the edit restriction does nothing as the user needs the base space edit first ... it won't grant editing for that one page alone.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...
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!
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