Nested Group Directories

LiveWhale
1

Just noticed something I never did before and not sure if it is by design or not.

We have a group, Group A, whose group directory is /group-a/. Obviously, users in that group can edit pages in /group-a/.

We have another group, Group B, whose group directory is /group-a/group-b/. Obviously, users in that group can edit pages in /group-a/group-b/ (but cannot edit pages in /group-a/).

But it seems that users in Group A can edit pages in /group-a/group-b/. I can’t decide if that makes sense or not, and don’t know if it is by design.

  • On one hand, it can be assumed that Group A can edit anything under their group directory, and the /group-b/ subdirectory is. In a sense, Group A is a parent group to Group B.
  • On the other hand, that subdirectory belongs to a unique group that it can be assumed users in a different group should not have access to.

Is this working the way it was intended, or is this a bug? It hasn’t really been a problem yet, but it might be nice to know for future reference.

2

Hi Jon,

I checked with the team and I gather this is working as intended—that is, setting

• Group A (/group-a/) gives all its users access to edit all pages underneath /group-a/
• Group B (/group-a/group-b/) gives all its users access to edit all pages underneath /group-a/group-b/

And the above setup doesn’t “box out” Group A users from editing pages in group-a/group-b/ or its subdirectories.

If you did have a need for this kind of behavior (say, certain people who needed access to edit /academics/index.php but you didn’t want them with access to /academics/biology/index.php or /academics/music/index.php), you could experiment with giving them specific Page URL Editing Permissions at the user level, rather than putting them in the Academics parent group. Hope this helps!

3

Thanks for clarifying that. Appreciate it.