Nesting is neither good nor bad; it is leverage. The same mechanism that grants access once at the right level also propagates mistakes at the same scale. These working rules keep the leverage and limit the blast radius.
Rules that hold up#
Distilled from how group sprawl actually happens:
- Cap depth deliberately, commonly at three to five levels, and enforce the cap continuously rather than annually.
- Keep licensing groups flat: group-based licensing applies only to direct user members, so nesting a group under a licensed parent licenses nobody in it. Licensed groups should contain users, not groups.
- One purpose per group: groups that serve access, licensing, and mailing simultaneously become unremovable.
- Name for navigation: a name should say what the group is for and who owns it.
- Require owners, and treat ownerless groups as incidents rather than backlog.
Structures to avoid#
Some shapes are trouble regardless of intent: loops, obviously, but also broad groups nested into narrow ones, which invert the intended containment and sweep large populations into whatever the narrow group grants. Both appear gradually and are invisible in flat lists.
Verify the intent survives contact with reality#
Best practices decay unless checked: the structure you designed and the structure you have diverge one change at a time. Whatever rules you adopt, the operational question is whether you can see violations this week rather than at the next audit.
VisualizerEngine
How VisualizerEngine enforces them
The policy engine encodes your nesting rules, from depth caps to structural constraints, and scores every violation into a live compliance percentage with drift over time. The hierarchy views show the shapes these rules exist to prevent, and alerts fire when a change breaks a rule.