Ran across a potential issue with group administration and although it does not cause a security concern it poses some confusion with regards to parent/child folder membership inheritance. The purpose of my post is to understand if this is expected behavior and if so what's the rationale.
If you create a group named parent, then add new child group then add user to child group membership the child group shows as direct member type and user1 shows was inherited membership type when viewing the parent group. For example:
If you edit the child relationship and remove parent reference the memberships update accordingly which results in expected outcome of
If you however you just remove the child group form the parent the parent group, membership updates correctly however when viewing the child group the parent relationship is still present.
For future group maintenance this could be a bit confusing as one would expect if you added members to child group it would reflect in the parent membership inheritance but it no longer will.
Is there feature reasons the child group parent relationship is not broken when child group is explicitly removed form the parent group's membership?
Discussion posts and replies are publicly visible
I think I see the issue you're talking about, however (just FYI) it makes it a bit confusing to read when you refer to "folders", since Groups are not Folders in any sense (other than being a logically similar grouping device). But in terms of Appian objects, Groups have nothing at all to do with "folders".
I have updated the post to remove references to "folder" terminology to make it clear I was referring to group hierarchy.
Cool, thanks I've re-read it and it's quite a bit more clear now, at least for me.