Skip to main content

Hierarchy

Purpose: Represent multi-level organizational structure (departments, regions, product divisions) to scope policies and delegate admin responsibilities.

Build organizational tree​

  • Step 1: Create top-level nodes representing business units.

  • Step 2: Add child nodes reflecting teams or regions.

  • Step 3: Assign role bindings to nodes enabling delegated administration (see Roles & Permissions).

Move users or nodes​

  • Move node: administrative operation requiring confirmation - be mindful of policy inheritance.
  • Move user: reassign user membership to different nodes (re-evaluate role bindings for Users).

Policy design & governance​

  • Use hierarchy to target policies such as session duration, MFA strictness, or access restrictions by organizational unit.
  • Avoid overly deep hierarchies to reduce complexity in role inheritance.

Troubleshooting​

  • Role binding appears not to apply:
    • Confirm whether the binding is inherited by child nodes and if user membership aligns.

Best Practices​

  • Model after real-world reporting structure for easier governance.
  • Document node ownership and intended policy scope.