page permission/restrction structure and automation

[Scarlett Qi]

hi everyone

we would like to achieve this in our confluence

1. have some pages viewable by all (internal and external readers), and the rest only by internal users, example 1,

• internal users can view page group X and Y
• external users can view page group X only

then further divide internal users, example 2,

• user group A can view page group A and C
• user group B can view page group B and C
• user group C can view page group A, B and C

having read some dicussions, I understand that we need to--

• either divide the user by spaces, or divide the pages by parent pages
• then duplicate the public pages into the private space/page tree by page include/excerpt

wondering if this is correct and if anyone could share any best practices to this?

2. given the complexity and ever growing content, we are also keen to automate the page restriction settings by intergrating with page metadata , e.g.,

• if targeted audience (metadata) is internal only, then auto restrict page to internal users group (for example 1)
• OR if targeted audience is user group A, then auto restrict page to user group A and C (for example 2)

having read some discussions, it is not very clear to me if it is possible, we are in server right now and in the midst of deciding whether to move to data center (more likely) or cloud. 

anyone knows how to achive this? 

thank you in advance!

[marc -Collabello--Phase Locked-]

Hi @Scarlett Qi ,

From my experience, restrictions and permissions are complex to handle and mistakes are easily made.  That said, I think it makes sense to divide content within spaces, and have relatively uniform permissions/restrictions within a space.

I would not recommend to change restrictions based on metadata in general.  I think it's much more obvious to move pages between space in order to restrict them.