How to grant access to a specific page(s) without granting access to anything else

[Stefan Götz]

Hi. 

We are working with an external collaborator and what him to see and work on some specific pages we created in some general spaces (e.g. sales, marketing, etc.). 

I want to expose only a specific page, not the whole space which already contains a lot of pages. 

What we did is:

1. register the user
2. create and added to the group "externals"
3. removed him from the group "confluence user"
4. assign under page restrictions access to this specific person

This does not work. But if I leave him in the group "confluence user" he can see everything which is already created.

Is there a way to hide everything from a specific group or users and only grant permissions to a specific page? 

Thank you. 

S.

[AnnWorley]

Please try these steps:

1. Create the user account
2. Add it to the group "externals"
3. Remove user from the group "confluence-users" (or whichever group you use to grant Use Confluence global permission)
4. Grant Use Confluence global permission to "externals" group
5. Grant appropriate space permissions to "externals" group
6. Add to page restrictions if desired

For reference, please review:

• Permissions and restrictions
• Space Permissions Overview
• Global Permissions Overview

I hope the steps work as expected, please let me know any obstacles you run into.

[sk1030mag]

Only 128 votes so far...

[Stefan Götz]

Hi Ann, 

Thank you for the answer. 

I followed the steps. I checked and do have the "external" group added to the Use Confluence global permission. 

I'm not sure if I understand point 5 so. 

You say: Grant appropriate space permissions to "externals" group.

But this is exactly what I want to avoid. I want to let users, belonging to the group externals (which have global confluence permissions), to see just some pages of a space not the whole space. And I also do not want to have to restrict all other pages for all other external users. I guess I miss something. 

I hope I explained well and you can clarify or help further. 

Best

S. 

[Pavel Potcheptsov]

This is not possible with current permissions model in Confluence.

You have to grant to specific user "View pages" in space permissions and restrict all pages in this space by including those who need access except specific user. And leave page for that user unrestricted.

[Nick]

So from what I've gathered, as of today there is still no way to elevate or override the top-down permission of a single page. So if I want the user to contribute to a certain document I have to grant them editing access to the entire space, correct?

If that's the case can someone from Atlassian help me understand the sense to this architectural approach? What really is the point of page level management, by the time you get to it you've already restricted your user's abilities. The expectation is that I grant users access to the entire space and then I must manage every page individually to limit the access I want throughout?

[Marcel]

Also needing this specific permission. Want to give access to anonymous user but only to one page, not the entire space. 

[Andrea Jacobson]

I want to be able to do this same thing.

[Simon Huprich]

Me Too!

[jeroentja]

We also! Please fix this.

[brock]

We also need this.

As a suggestion, maybe Atlassian should just remove "restrictions" altogether  - since as it is currently implemented, it is nearly pointless. Maybe that would get us closer to a solution some day?

[Henry Chad Apale]

Agreed, please implement specific page access instead of granting to a whole space and then applying restrictions to all the pages. This can be cumbersome if the Space already has multiple pages

[Scott]

I agree. It is painfully cumbersome to restrict access.  

[Marco De Santis]

If you want the chance of something happening on this topic, you need to make sure a bug or feature suggestion ticket for the according Confluence product exists.

https://jira.atlassian.com/secure/Dashboard.jspa?selectPageId=10440

Ideally add a comment to this thread indicating the respective ticket ID.

[jeroentja]

Hi Marco, is there already a request? It's quite overwhelming al the options at the link you posted.

Honestly, I think this is a design flaw and should be reported as a bug.

[Marco De Santis]

Hi @jeroentja . I have not checked. I just stumbled upon this thread and wanted to share my experience. Reporting a bug or requesting a new feature in the community section is usually not going to be picked-up by Atlassian (there might be exceptions, of course).

[Scott]

I didn't find a similar issue so I created one https://jira.atlassian.com/browse/JSDSERVER-11299 Please vote!

[Alex Rada]

also looking for this feature for ages.

[Deepan]

We too..

[Kari]

We too... and I agree with jeroentja it seem to be BUG 

[Myles]

Add me to the list as well.The lack of this functionality is painful.

Thanks