Define node types (region, office, department, team) and the parent-child rules between them. Canopy enforces your schema: you can't accidentally put a team under a team if your schema doesn't allow it.
Users see only the parts of the hierarchy they have access to. A regional manager sees their region and everything below it, but nothing outside. This isn't filtering: it's enforced at the API level.
Grant temporary access with effective_from and effective_to dates. Contractor access that auto-expires, planned promotions that activate on a future date, with no manual cleanup.
effective_fromeffective_toBuild and manage your organizational tree through the Developer Console. Create nodes, drag to reorder, and assign identities. Operators can manage the full structure without engineering involvement.