Restrict Access To Specific Pages in Space - Valid Use Case

[Kush M]

I have hundreds of spaces, each with multiple pages and sub pages structured by project. Each project should be visible to vendors who are allocated to the project but NOT to all other vendors who are not allocated to the project page and subpages. 

The way the permissions seem to work this is a nightmare to do with security administration and is almost a non starter because by default everyone in the space has view access to all content. 

Is this still correct or is there a solution to this valid use case?

Thanks

[Kush M]

Probably this will not work as the home page has content we don't want vendors to see. 

[Kush M]

Thanks. yes this will work but the challenge here is that we will need to do a lot more administration if we don't restrict from the home down for vendors. If we restrict from the home down for a group where all vendors are, then they don't see anything and at the project level we just give them access

Lot easier than putting page restrictions at every level. 

[Nic Brough -Adaptavist-]

Again, the view restrictions cascade down.

[Kush M]

Thanks for your answer. I'm not sure this will work as the only section we want vendors to see in the space is their specific project.

Here is a structure of space

• Home
  • Many sections like business strategy, operations etc here which the vendor should not see
  •  Project 1
    • Subpages in project 1
  • Project 2 
    • Subpages in project 2

I am thinking one way to do this will be to create one group for all external vendors and on the Home page restrict the external vendors group to not see anything so this will cascade on the whole tree. Then on each Project Page i.e. Project 1/2/3 we explicitly grant view access to each vendor so they can see content under that Project only. 

Will this work? 

[Nic Brough -Adaptavist-]

I described a simple set of restrictions done at the top layer.  It works further down as well.  So you can do

• Home (unrestricted)
  • Business strategy (view restricted to only internal users)
  • Operations (view restricted to only internal users)
  • Docs for application X
• Internal (view restricted to only internal users)
• Vendor 1 (view restricted to vendor 1, and internal users)
• Vendor 2 (view restricted to vendor 2, and internal users)
• etc

Then vendors would see "home", "Docs for app X", and their vendor pages, but nothing else.

[Nic Brough -Adaptavist-]

The usual approach to this is to divide pages near or at the top level of a space.

For example, we often see spaces with two top-level pages, such that:

• Home (unrestricted)
• Internal (view restricted to only internal users)
• Vendor 1 (view restricted to vendor 1, and internal users)
• Vendor 2 (view restricted to vendor 2, and internal users)
• etc

View restrictions cascade down, so all you have to do in this structure is make sure documents are put under the right top level page.