How to Better manage Parent Groups

[Community Alums]

The User Membership of our working groups (where assignments, approvals, etc are made) is managed through our Catalog and Active Directory and works well - I'll call those "Assignment Groups (ASM)" for purposes of this discussion.

- All our ASM Groups have a "Parent" group.  Each Parent also has higher level Parent - all the way up to our CIO level.  The top level Parent Groups are considered "Level 1".  The Parent Group names are all the different Department Names.  

- Similarly, Parent Groups are "owned by" the Department Heads.   

- Currently we manage all Parent Groups and their associations manually.  This manual process is a BEAR when we start re-organizing.   I am searching for a way to automate. 

One approach I am considering (but open to suggestions) would be to (Step 1) find the Department Names/Managers who are direct reports to our CIO so as to create the top level (Level 1) of Parent Groups as per their Department Name and set the Owner field to be Dept Manager.

Repeat Step 1 until arriving at the first line supervisors

The First Line Supervisors will not be the Owners of any Parent Groups.  However, they will be the owners of all ASM groups

Hopefully the attached screen shot will help clarify?? 

Any Ideas are truly appreciated.

StacyLen

(my apologies that this is a partial overlap of an earlier post.  That earlier post got all discomboblated due to my updates being held for approval (something I had never seen before)

V/R

StacyLen 

[Dave Becker]

Agreed, the snowunderground blog article suggest to stay far away from using parent groups.  That was 2022, though.  However, we ran into some issues where adding roles to the parent did not properly cascade to the child groups where the parent was HR. Could be a scope issue or update set issue, but I've also seen problems with child groups not inheriting or having duplicate roles.