Access permissions in this structure:

• Category (allowed)
  • Forum (denied)
    • Sub-forum (allowed)

In other forum software I have used, access denied is not transferred from parent to child categories/forums. There are occasions where the content of a container should not be accessible, but access to the child container is allowed. It might be preferable to have open access to anyone who knows the URL without setting up a usergroup for access. It allows for retaining access but not have forums take large amounts of page real estate (a list of links might be preferable in some situations). Navigation to the space might be via the main menu, or (privately) via PM, or in a sticky post, for example.

Alternatively, inheritability of the access denied permissions to child containers is arguable of course, even if not fully consistent (and certainly less flexible).

So, is this intended behaviour, an oversight, or a bug?

Applies to v4 and v5.

Edited October 16, 2024Oct 16 by Como

This is intended behavior. If the Parent forum is not accessible, so will the child. As the structure is hierarchal.

I would just make them two parent forums under the same category as that will be hierarchal and navigational sense which will limit confusion of users.

Nothing in our software is merely accessible by URL without some form of customization. Member groups and hierarchal settings play a role in permissions, navigations, etc... This is best for user experience and structural integrity. As you wouldn't want someone accessing something they shouldn't.

 

Hi @Jim M

Yeah. I figured that it was probably intended behaviour (especially as it applies to both v4 and v5). But thought it worth asking the question since I've seen it operate differently in other forum software. I still think there is utility in denied access not being inherited, but there are arguments in the other direction too.

Thanks for the reply.