User with View/Edit Privileges on a Page can view it but not edit it
Asked by Nicolas Richards:

*This question is in reference to Atlassian Documentation: [Page Restrictions](https://confluence.atlassian.com/pages/viewpage.action?pageId=139414)*

We have a Space where everyone can View, and a Page in that Space that has Viewing and Editing Restricted to a few users. None of that page's parents have any restrictions.

Yet one of the named users can see the page but can't edit it, despite being one of those explicitly named as having View and Edit privileges for that page.

The only way I can grant him edit privileges is to name him on the Space Permission level instead. But the Page Restriction should work. Any idea why it isn't when none of the parent pages have restrictions?


Answers:
author: Milo Test
body: You grant space Pages Add permission to any user or group that needs to edit a page in that space.

comments: author: Nicolas Richards
body: Thank you for the response, and that is how I got around the issue. But shouldn't this work instead:

* User A has View permission on the Space level
* User A has View/Edit restriction set on a particular Page in that Space

What we want is for that user to only be able to edit that one page, but view everything else in that space. If I do what you suggest, and what I already did as a workaround, gives that user edit permission throughout the space, and that is not what I want.

Why does giving Read/Write to a user for a page not allow them to edit that page?


author: Rodney Hughes
body: The "hierarchy of doing things is

The User must have edit capabilities associated with their Permissions level to the Space

If they have Edit capabilities in their Permissions, then you can Restrict which of those people can edit a particular page by using the Edit Restrictions

So if their Space Permission is view only, they cannot edit any page regardless of Page Restrictions.

Note that Page View Restrictions and Page Edit Restrictions work differently and independently.

Page View Restrictions are automatically inherited by its Child pages and hence you can create a "private" set of pages for a select set of Users of the Space - none of the other Space Users can see those pages exist

Page Edit Restrictions must be applied page-by-page but of course to edit you must be able to view so if Page View Restrictions have been set, the Editor must also be included in the Page View Restrictions. If no Page View Restrictions have been set, then all Users can see but you can still set Page Edit Restrictions to the select people


author: Milo Test
body: Think of it this way, anyone can look through your bathroom window, but for them to use your bathroom, you have to give them access to the house first.


author: Nicolas Richards
body: Thank you both, that explains it very well. I have a better understanding of the process now.


author: Jaydeep Bhati
body: Hi,

I am facing this issue as well where I cannot provide a user an EDIT permission on a page, given they have READ access to the Space.

There should be a capability to give the user READ access of the Space but only EDIT certain pages in that Space.

Thanks,

comments: author: StephanieC
body: The answers above give you the solution. You CAN give a user READ access to the Space and EDIT only certain pages, but you must let them "into the house" first, giving them "Add Page" permission on the Space level.

Keep in mind you will then have to ensure they are restricted FROM Editing (View Only) the other pages on the Parent Page Level. (children inherit parent permissions)


author: jasminperalta
body: You mean, if I want to let a user, who is part of another team and has no general edit permission in our space, let participate on a single topic, I will have to remove his edit permission on every other page by the and for every single page which will be created by anybody in the future?

If I got you right and that's the permssion logic here, that's no solution at all!


Tags: confluence-administration

restriction