How to grant privileges to one specific page - desperately looking for help

[berecom]

Hi everyone,

I’m trying to grant specific privileges (e.g., view, edit) to a single page within a Confluence space, while maintaining different permission settings for the rest of the space. I’m aware that Confluence handles space-level permissions, but is there a way to configure permissions on a page-by-page basis?

Here’s an example of my scenario:

I have two spaces: "Sales" and "HR."

• The "Sales" space is restricted to the Sales team (Sara, Sven, and Steve) and is confidential to the rest of the company.
• The "HR" space is restricted to the HR team (Hanna, Harry, and Helen) and is also confidential.

Now, I want to grant Sara (from Sales, not part of the HR group) access to a specific page in the "HR" space, but I can't seem to find an option to give her permission for just that one page.

Is there a way to do this within Confluence? Any advice or steps would be greatly appreciated!

Thanks in advance for your help.

Cheers, Bernie

[Shawn Doyle - ReleaseTEAM]

Hi @berecom 

In Confluence permissions are positive (granting) and restrictions are negative (limiting).

You need to grant Sara access to the HR space, then restrict all pages from Sara in HR except the one you want her to view, if that page is a child page you need to give her view access for that entire tree. You need to at least add this restriction on all top-level pages.

I would suggest you create a group for Salespeople who need to peek in HR, and add Sara to this group, set the above using the group. This way when Sara no longer needs access, you can remove her from the group without adjusting the restrictions, and if another salesperson needs access you can add them to the group.

[berecom]

Hi @Shawn Doyle - ReleaseTEAM , Thank you for the suggestions. We did try implementing the solution, but I believe it may lead to complications down the line.

Currently, we have Sara working on this, but next week it could be someone else, possibly from the IT team or a different department, handling another page.

This approach might not scale well with multiple contributors.

[Kristian Klima]

Hi @berecom 

Try the following.

On that specific page, click the padlock next to the chain and Share icon/buttons.

Select Only Specific people can view and edit.

Here, you can specify the HR team (as a Group or as individuals) + Sara.

If that doesn't work, you will have to tweak permissions/restrictions in terms of arranging user groups/individuals in such a way that will give Sarah access to space thru Space permissions but will restrict her access via pages' restrictions. Then you'll simply let her to view the specific page ad hoc.

Having said that... if Sara needs an ad hoc access, you'd better of conducing her contribution elsewhere to avoid disrupting your permissions setup.

[berecom]

Hi @Kristian KlimaThank you for your response.

That was actually my initial approach as well. However, if Sara doesn’t have access to the site, I’m unable to select her, as shown in the screenshot. As a result, her permissions on that page won’t be applied.

Is there no alternative, or am I missing something?

Apologies for the additional questions—I'm just a bit puzzled.

[Kristian Klima]

I see... 

OK, so just to clarify...

You have ONE Confluence site with multiple spaces, including HR and Sales.

You need to combine mine and @Shawn Doyle - ReleaseTEAM 's answers :) 

Now, working with the details that you provided reply to Shawn...

1. Create a user group with all HR folks in it.
2. Restrict HR space pages to that group only (you can use an app like 'Pages Manager' by Ricksoft to change restrictions en masse, Pages Manager is free...)
3. Create another user group, such as 'HR-external'. You will assign individual sales folks like Sara to this group as needed.
4. As needed, you will expand restrictions for individual pages in the HR space to that specific group. 

So, Sara needs to edit Page A in HR. You grant her permissions to be in the HR but as she's not in the HR user group, she won't see anything. Then you grant HR-external group access to the specific page via Restrictions. Then you assign Sara to HR-external group. She does what she needs to, then you remove her from the group and revoke the groups' access to Page A.

When Sheldon from Sales needs to access Page B in HR, you repeat the process.

I hope it makes sense :) But Shawn's description of how Permissions and Restrictions work is great, and you can use those concept in tandem to achieve a really granular and flexible access control.

[berecom]

Hi @Kristian Klima , @Shawn Doyle - ReleaseTEAM 

Thank you both for your responses. I really appreciate it! 👍

Yes, we have only one Confluence site with multiple spaces.

I tested your solution, and it works—so thank you for that!

However, I must admit that this approach may not be very practical for our situation. We're soon reaching over 1,000 employees, and this method could lead to overly complex groups, especially as the number of "externals" requiring access to more pages within a site increases.

For example:

Site: HR
👥 group-HR-employees
👥 group-HR-externals
👥 group-Sales-externals
👥 group-Production-externals
👥 group-IT-externals
👥 group-Research-externals
...

Site: Sales
👥 group-Sales-employees
👥 group-HR-externals
👥 group-Production-externals
👥 group-IT-externals
👥 group-Research-externals
...

Site: Production
👥 group-Production-employees
👥 group-HR-externals
👥 group-Sales-externals
👥 group-IT-externals
👥 group-Research-externals
...

Site: IT
👥 group-IT-employees
👥 group-HR-externals
👥 group-Sales-externals
👥 group-Production-externals
👥 group-Research-externals
...

Site: Research
👥 group-Research-employees
👥 group-HR-externals
👥 group-Sales-externals
👥 group-Production-externals
👥 group-IT-externals

I am new to this topic of granular permissions on Confluence sites for "externals." From my perspective, this approach doesn’t seem very "enterprise-ready" as it would create a substantial workload for our Atlassian admins to manage centrally.

Apologies if these questions seem basic, but I feel like I might be missing something here.