Nembl
Admin Guide
Company Settings
Org Structure

Org Structure

The Org Structure builder is a visual canvas for arranging your Company's Organizations into a hierarchy: Divisions contain Departments contain Teams, etc. It's the same drag-and-drop surface as the workflow builder, but applied to your org chart instead of process flow.

Open from Admin → Organizations → Org Structure.

Concepts

Org Levels

Every Organization sits at one Org Level (e.g. Division, Department, Team). Levels are ordered by depth — depth 0 is the root, depth 1 is one tier below, and so on. You define the levels and their colors yourself; common patterns:

  • 2-level — Department → Team
  • 3-level — Division → Department → Team
  • 4-level — Group → Division → Department → Team

Set up levels in Admin → Organizations → Level definitions. The Org Structure canvas uses the level color for each org node so you can read the hierarchy at a glance.

Parent / child rules

A child Org must sit at a lower level than its parent (i.e. higher depth number). The canvas enforces this on drop:

  • Dropping a Department onto a Division ✅
  • Dropping a Department onto a Team ❌ (depth 1 onto depth 2 is invalid)
  • Dropping the root level onto another node ❌ (must drop onto canvas)

Teams within Orgs

Each Organization holds Teams (configured in Admin → IAM → Teams, surfaced here as part of the Org node). Teams are where Users actually sit and where Responsibilities are assigned.

Using the canvas

  • Drag an Org Level chip from the left palette onto the canvas (drop on parent node, or on empty canvas for root level)
  • Edit a node — click to open the property panel; rename, change manager, change level
  • Connect / re-parent — drag the connector from a child onto a different parent
  • Auto-layout — the toolbar's auto-layout button re-runs Dagre to keep the chart readable
  • Save — persists the canvas to the DB (OrgStructure records the parent-child edges)

Why bother?

The org chart drives several downstream behaviors:

  • Notification routing — escalation paths ("notify my manager's manager") resolve via the Org Structure
  • Reporting — aggregate views (Open Requests by Department) need the hierarchy
  • Responsibility resolution — when a Team is assigned, members come from the Org chart
  • B2B representation — the chart's top-level node defines the Company that connected B2B partners see

If you only have one Org and one Team, you don't need this page. Larger Companies with managers and divisions get most of the value.

Related

OrganizationsMembers & Invitations