How To Add Groups to Groups

[MrDevanWright]

How can I add an already established group with roles and users to another group? Groups don't appear in the member list, you can only assign one parent group, and the Edit option isn't available on the Groups tab as it is on the Group Members tab.

I'd like Alpha Group to be a member of Beta Group and Charlie Group, so if anything is assigned to Beta Group it'll be viewable by Alpha Group. Instead of moving users in/out of auxiliary groups they need access to, I'd like to change who is in the one primary group that'll give them access to whatever assignments or roles are granted by the auxiliary groups.

[MrDevanWright]

If a task is assigned to a child group, is the parent group notified of and has access to the child group task?

What about approval requests? Can a Parent group approve/deny on behalf of a Child group?

[jMarshal]

The OOB notifications will NOT trigger a notification to a "child group", if an item is assigned to the "parent group". This goes for any type of OOB notification. 

I believe the ability to specify a "child group" is for visual/organizational purposes only. There may be some features that take advantage of that platform structure in some way, but groups in ServiceNow do not function with "inheritance" attributes like you are describing/looking-for. Each user group is a group in and of itself. However, there are a lot of ways to accomplish an "embedding" structure, that you may benefit from.

The best one which comes to mind is to use an LDAP integration and set up multiple transforms to put users in multiple groups (the "parent" and the "child") so that it will benefit from the configuration(s) of both/either. This way you only have to put them in a single group, but they "inherit" attributes of many.

You can also write business rules that will simulate the approach described here...but nothing oob really works that way, with groups...and in my opinion, that is a good thing because you can (relatively) easily simulate the "inheritance" like I'm describing here, but you couldn't "simulate" the "removal of attributes" ("de-inheritance", if you will?) so easily.

[jMarshal]

For further reference: Groups | ServiceNow Developers

developer.servicenow.com wrote:

...use the All menu in the main ServiceNow browser window (not Studio) to open User Administration > Groups. Click the New button. Configure the group:

• ...
• Parent: Other group of which this group is a member. The child group inherits the roles of the parent group. So, if a group has a parent, it inherits the roles of the parent group. However, the members of the child group are not members of the parent group.
• ...

---

[LearnUseThrive]

System Security > Groups, locate the group and Parent is a default OOB field you can fill. I don't know about the tasks or approvals.