You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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:
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?
Please try these steps:
For reference, please review:
I hope the steps work as expected, please let me know any obstacles you run into.
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.
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.
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?
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.
Ideally add a comment to this thread indicating the respective ticket ID.