Page History

...

1. Similar to COUs, membership in a parent Group will not automatically imply membership in any child Group.
2. Because colons (:) are already used to denote special Groups, slashes (/) will be used to denote hierarchy. Neither colons nor slashes will be permitted in Group names.
   1. Slashes (and colons) could be replaced on a per-Provisioning Target basis using a Data Filter.
3. The full name of the Group (eg: as provisioned) will be constructed using any parent Groups. For example, if Pizza Aficionados is a child group of Lunch Societies, the full name of the Group will be Lunch Societies/Pizza Aficionados. There will be no leading slash so that flat Group structures are not affected.
   1. Note that because Group names must be unique within the CO (see below) it's not actually a requirement that Group names include the leading portion of the hierarchy. This could potentially be configured, either via CO Settings or per Provisioning Target.
4. Only CO Administrators can set or change a parent Group ID. Because this will effectively result in the Group being renamed.
   1. The Self Service widget might offer more flexibility.
5. Group Nestings will continue to operate as is, with no direct relation to Group hierarchies.
6. In order to avoid unnecessary complications, moving a COU within the COU hierarchy will not move the corresponding automatic Group. Automatic Groups will remain in a flat name space.
7. Similarly, Owners Groups can not be given parents or children.
8. Owners Groups names will use the base Group name only, eg CO:owners:Pizza Aficionados. As such, Group names must continue to be unique within the CO (not just within the leaf).
   1. The unique name constraint might be too limiting, in which case the base Group name would need to be eg CO:owners:Lunch Societies/Pizza Aficionados, Alternately, perhaps a Data Filter could rename "duplicate" group names (eg: Lunch Societies/Lunch Pizza Aficionados gets renamed at the Provisioning Target to Lunch Societies/Pizza Aficionados).

Summary of Related Concepts

	Applies To	Affects Memberships	Cascades Permissions	Enforces Namespace
COU Hierarchy	PersonRole
Group Hierarchy	GroupMember
Group Nesting	GroupMember

See Also

• CFM-316 Groups Dashboard Widget
• CO-1223 Group Hierarchy
• CO-1606 Private vs Public Groups
• CO-1637 Disable Non-Admin CO Group Creation
• Registry PE Group Ownership