Organization Structure

Use Workspace Settings -> Organization to keep teams, members, reporting lines, and permissions in one place.

Start the structure

If the workspace has no People teams yet, choose one setup path:

• Create a team when you already know the first group you need.
• Apply a template for common agency, support, engineering, or operations structures.
• Import Discord roles on Discord workspaces when existing roles are a good starting point.

Templates and imports add normal Bnder People teams. They do not replace your existing structure. After adding them, rename teams, move them, assign members, and review permissions like any manually created team.

Discord role import is a one-time copy. Bnder does not keep the imported teams synced to Discord roles afterwards.

Work in the org chart

The organization chart shows team nodes and members together.

You can:

• Drag a team onto another team to make it a child team.
• Drag a team onto a sibling drop line to reorder teams at the same level.
• Drag a person onto a team to add that team membership.
• Drag a person onto another person to set a manager.
• Search for teams or people.
• Filter by department, routing eligibility, inactive members, or people without a team.
• Collapse large teams so the chart stays easier to work with.
• Export the visible chart as a read-only PNG.

Team hierarchy affects more than the diagram. Members of child teams can count as effective members of parent teams for permissions, assignment filters, event invites, capacity, and routing.

Edit teams

Open a team to edit:

• Name and description
• Parent team
• Lead and manager
• Routing eligibility
• Team members
• Team permissions

Teams that are routing-enabled should have at least one active, routeable member. If a team has no lead or manager, Bnder shows a reminder so ownership does not stay unclear.

Edit member profiles

Expand a member row to edit:

• Display name
• Title and department
• Manager
• Team memberships
• Skills
• Routing eligibility
• Backup users
• Vacation replacements
• Admin notes

Inactive or deleted people may stay visible for historical context. They are not used for new routing or capacity decisions.

Manage permissions

The permission matrix lets admins review direct and inherited access for teams and members.

Choose a global or project scope, then inspect permissions across modules such as Tasks, Tickets, Calendar, and Knowledge. Filled cells are direct grants. Inherited cells show access that comes from team membership or global grants.

Click a cell to add or remove the direct grant for that row. Inherited access remains visible until the source team or global grant is changed.

If the workspace uses manual member approval, approved members appear ahead of the remaining members in people-focused Organization views. See Member Approval for the assignment-picker behavior.

Clean up stale references

The Organization page can highlight stale references such as deleted teams, inactive members, missing projects, or broken routing targets.

Use cleanup actions when you want Bnder to remove invalid references without disturbing valid teams, permissions, or routing policies.