Page Permissions

[Michael Confessore]

I have a private space setup with a group of team members who are the only ones given view/edit permissions in the space. On a particular sub page within the space, I’d like a few additional people (not in the group) to also have view/edit permissions to only that page and it’s children. When I add those specific people individually to the page permissions, the original group loses access to the page event though it says permissions are inherited. Is this desired behavior?

[Brant Schroeder · Accepted solution]

Permissions are inherited until you override those with specific permissions to the page. The page permissions will trump space permissions or permissions on a parent page.

[evanbartlett]

How do you do this?  My page permissions say "Anyone can view and access" , which is super confusing because it's not true.

When I click "Inspect Permissions" and view a particular person that I'd like to give access to this page, but not the space, I just see that they are inheriting permissions from the space.

I don't see where to override them at the page level?

[Michael Confessore]

It’s extremely confusing...my solution was to make a user group for members that will have permission to everything (called “core”) and then a second group that will only have permission for specific pages (“additional”). Both groups have their permissions set in the “Space Permissions” tab and then on the pages that need additional access, I give core view and edit permissions and additional only edit permissions...I feel like there has to be a better way, but I haven’t found it yet.

[evanbartlett]

Yeah, I've been spinning trying to figure out how to make this work.  What happens to "additional" with only edit permissions?  They can't see any of the pages, unless you specifically give them view?

Thanks!

[Michael Confessore]

My apologies, I meant to say that “additional” only has view permissions. With that configuration (core with view/edit on both the space and page and addition with view on both the space and page) the result is that core can access/edit everything in the space and additional can only view the specific pages they’re added on, everything else is restricted to them.

[evanbartlett]

How are you able to set the page permissions to be different than the space?  I have a core group added to the space, and I'm trying to get that "additional" group added to a specific page.  Sounds like I need to add them to the space first, and then block all the other pages except the one they need to see?

Does that mean all new pages that get added, are visible to the "additional" group by default?

[Brant Schroeder]

You are correct the group has to have access to the space and they would have access to any new pages that are created at the top of the space level but not all new pages created.

For instance if I had a space that had information for our IT, HR and Finance team in it and I had it broken up as follows:

Confluence Space

• General Page - No security everyone has access
• ITS - Locked down to the ITS group
• HR - Locked down to the HR group
• Finance - Locked down to the Finance group

In this example I create a new page in the space that everyone will see:

Confluence Space

• General Page - No security everyone has access
• New Page - No security everyone has access
• ITS - Locked down to the ITS group
• HR - Locked down to the HR group
• Finance - Locked down to the Finance group

In this example I create a new page in the space that ITS will see:

Confluence Space

• General Page - No security everyone has access
• ITS - Locked down to the ITS group
  • New Page - Only ITS has access
• HR - Locked down to the HR group
• Finance - Locked down to the Finance group

So pages created under a page that has security inherit the security.