Confluence Page Individual Restrictions

Hello Everybody,

i do have a confluence space and in there is a Page, which i want to unlock for an individual user out of our company who already is registered as a Atlassian User. 

Now this user is free to see every page in that confluence space and thats not good. 

Is there a way to handle the restriction?

Hope to hear from you! 

Greetings from the sunny Hamburg, Max

2 answers

This widget could not be displayed.

So you want to restrict the whole space except one page?

In my opinion it is easier to move this page to another space, where he has access.

You surely checked with the documentation?

https://confluence.atlassian.com/display/DOC/Space+Permissions+Overview

This widget could not be displayed.

Hi Paul, thank you for your prompt answer,

Yes thats correct. Only one Page should be visible for him. 

But from my point of view it doesn't make a sense to move that page to an other space, because we want to hold the documents by one place and do not want to switch between them. Your idea would be the easy way but also the dirty way from my point of view

I read the documentary but there is no part where these case are described with a solution. 

sad

I'm afraid I'd go with Paul's answer too - Confluence has a simple top-down permissive access model - you need to let him have access to the space first, then restrict him from seeing *everything* else in the space. There is a slight variation you could do - keep the page in the space, but rearrange the hierarchy so that you have two main "branches" in the space. Let's call them "public" and "private". For your case, all the pages except the one you want him to see would be in the "private" branch, and that one page would be "public". You then set the space permissions to "let everyone see it" and restrict the "private" page to "everyone except my odd user". The permission will cascade down the private branch and hide all the pages in it from him. As an aside, that probably breaks the heirarchy too, so I'd probably add the "public" page into the private branch with an "include" in the appropriate place.

I see that this seems like a dirty solution to you. But it is the most simple approach to reach your goal, with not too much pain. You surely could give access to the space and restrict every page except the one the user should see. But I would not maintain that, even if there should be more user able to see the page etc.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 17, 2018 in Confluence

Why start from scratch? Introducing four new templates for Confluence Cloud

Hi my Community friends!  For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...

569 views 7 6
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you