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're using confluence spaces for collaborating and/or communicating with clients. There are constellations when a client should access only certain pages within a space.
I'm not able to figure out how to handle this. I'm aware of the permission system and that it all starts with permission to access the space and further down the page restriction.
This means in more detail (for grant someone access to only one or several pages):
It feels cumbersome to handle it that way although I'm not sure if I miss something.
How to deal with such a scenario? Any thoughts are welcome.
It's a bit more clever than that, as view restrictions cascade, but the way it works may not suit the way you want to structure your pages within a space.
I find it easier to explain this with a worked example. Imagine you have
Now lets say you put the following restrictions in place for Alice and Bob:
With that setup,
You only need to restrict two pages to protect the six partially hidden pages.
What you need to do is place your pages into two trees - one tree visible to your clients, and the other not.
You could segregate the client-accessible information to a separate space.
If you have information that needs to be segregated more per client, you might consider creating a space per client.
If you need to have both client specific information and information shared across clients then you could use the inherited page restrictions concept that @Nic Brough -Adaptavist- described with a single client space.
If the same information needs to be visible in a space accessible only to your internal personnel, you could grant the internal personnel access to the client space(s) and then use something like the Page Include macro to display information from the client space(s) in the internal personnel space. If you had set up page restrictions in the client space(s) you also need to make sure the internal personnel are include so they can view everything.
Hi @Volker Jakob - Without possibly using a plug-in the steps you have listed out is what I have done/seen done in the past. It is cumbersome but it does give you level of control you are wanting using the application functions.
Hi @Bryan Trummer , good to know, that I don't have a misunderstanding regarding the permission structure. I already started to research for potentional plug-ins but as @Nic Brough -Adaptavist- mentioned, the key for my scenario could be a different page structure and use the built-in permission cascade.