"inherited view restrictions" - always supersede individual page permissions? Edited

[Alex Gerulaitis]

Do "inherited view restrictions" for a Confluence (on-prem Data Center v.7.4.4) - have precedence over individual page permissions?

I.e. no way to grant a specific user read access to just one page in an otherwise restricted (no read access to anyone except certain groups and users) space?

Context: we have a restricted space within an enterprise with no read access to anyone except certain groups. We'd like to give read access to just one page within that space to a specific user.

Adding that user to that specific page and giving them read access - lists that user as having view access - yet the user reports "404 page not found", and is not listed among "people who can view".

To reiterate the really confusing parts in this:

• A user is listed as having read access in page permissions - yet has no access due to inherited permissions; there is no straightforward indication of it in the UI: nothing like "while this user is listed it as having access, this is superseded by inherited permissions and thus has no effect". One has to go to "People who can view this page" (a separate UI element), to view effective permissions.
• I don't see any mention of inherited permissions always having precedence over individual page permissions in "Understanding Permission in Confluence". Shouldn't it be there in big bold letters?

Thanks!

P.S. Apologies if this has been asked a gazillion times.

[Henning van Ackeren · Accepted solution]

Your assumptions are correct, and I agree it could be more clear in the documenation. Here it is more explicit: https://confluence.atlassian.com/doc/page-restrictions-139414.html

[Alex Gerulaitis]

Thank you! (Really hoping the UI can be clearer. I am far from the only one in our Confluence instance bumping my head into this.)