The organization tree

The left column of the Users & Teams page is the organization tree. Every member, role, and permission override exists in the context of one of the tree's nodes. Selecting a node loads its detail (members + roles) into the right column.

The three node types

Level fixes the hierarchy at three levels:

• Organization (icon: building). Exactly one per workspace — the tree's root. Always expanded.
• Team (icon: users). Children of Organization. Use for top-level groupings — usually departments or business units (Performance team, Creative team, Strategy team).
• Sub-team (icon: git-branch). Children of Team. Use for further drilldowns — typically channels or sub-disciplines (Google Ads, Meta, TikTok under Performance team).

Sub-teams cannot have children. Three levels is the maximum — by design.

Adding nodes

Select a node, then click Create team at the top of the team detail panel. The Create Team modal opens:

• Name (required).
• Description (optional).

The node type is determined automatically:

• Selected Organization → creating a Team.
• Selected Team → creating a Sub-team.
• Selected Sub-team → the action is hidden (no further nesting allowed).

Selecting nodes

Click a node in the tree to select it. The right column re-loads with that node's:

• Members tab.
• Roles & Permissions tab.
• Reports tab (only if the node has a clientId and you have manage roles).

The badge next to each node is the count of members at that node.

Renaming and editing

Open the team detail header and click Edit unit. The edit modal lets you change the name and description; the node type and parent are not editable here.

To move a node, you'd have to delete it and re-create it under the new parent. That cascades — see deletion below.

Deleting a node

The team detail header has a Delete action (only visible if you have manage teams). The behaviour:

• All child nodes of the deleted node are deleted too.
• All members at the deleted node lose their assignment to it. They keep any assignments at other nodes.
• All roles defined at the deleted node disappear.
• All permission overrides scoped to the deleted node disappear.

There's a confirmation dialog. There's no undo.

Permissions to manage the tree

Two top-level capabilities gate this section:

• permission to manage teams — required to create, edit, or delete nodes; required to add or remove members; required to send invitations.
• permission to manage roles — required to create / edit roles, edit role permissions, and apply permission overrides.

These two are the most powerful permissions in Level — assign them only to people who should be able to reshape the workspace.

A regular member without these:

• Sees the tree (read-only).
• Sees the members of nodes they have access to.
• Sees their own roles in the Roles & Permissions tab (but not other people's).
• Cannot create, edit, or delete anything in this section.