nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why would a full admin in confluence be unable to see a page due to a restriction setting?

Erica Cunningham

A few of us have full administrative access/rights to Confluence, yet someone was able to restrict a page that required permission to access. We cannot understand how that happened when we are supposed to be able to see all content no matter what, or at least that is what I understood on the site

The Confluence permission scheme allows the following levels of site administrator permissions:

Super user – A 'super user' belongs to the confluence-administrators group, has full administrative access to Confluence, and can see all the content.

Is there a setting we overlooked that someone can help me with to prevent this from happening, or is it supposed to be possible for someone to restrict a page even to full admins?

Thank you for any help you can provide! : )

Accepted answers

Nic Brough -Adaptavist-

The doc is misleading. Not quite "wrong", but the section you've quoted is misleading.

A user with admin rights has, well, admin rights. Not the ability to see and do anything. They can grant themselves the ability to see and do anything, but the admin right does not grant them any "browse" rights automatically. They still have to be given those rights in the space permissions. (And of course, they can see and edit the space permissions, as it's their job)

All comments

Nic Brough -Adaptavist-

Erica Cunningham

Interesting, thank you for clearing that up Nic and so quickly! : ) So, there's no way to prevent that type of restriction from the Admin group? Seems a little risky, when we also need to ensure content is following proper protocol, and what happens if that person up and leaves that has the restrictions set on that page?

I wish there was an over-riding setting that we could prevent that from happening. Perhaps Atlassian will hear me. : )

Nic Brough -Adaptavist-

No, the point of the administrator's job is to administrate the system. If they're restricted from getting to parts of the system, they can't do that job.

If an a person leaves, that's exactly the case where you need your system admins to have admin rights - they can find and change the restrictions left behind.

This is not something that you'll find in any software. Your "root" admins can always do everything, one way or another. You have to trust your admins.

James Dellow

In Confluence Cloud, the "super user" System Administrator global permission is only available to Atlassian staff who administer your Confluence site. The highest level a user can be granted is Confluence Administrator, which doesn't do quite the same thing.

unknown

I have the same issue as Joe Cross but solved it by logging in (via the user admin page) as the user who put the page restrictions and then left the organization. That way I was able to see the page hierarchy and change the restrictions.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud