People Management

People Management is available with Pro. Users with Manage settings can open Workspace Settings → Organization.

For detailed guides, see:

Teams and organization

Use Organization settings to:

Create teams or start from a template
Arrange parent and child teams
Assign members, leads, and managers
Add titles, departments, skills, and routing eligibility
Review the organization chart
Export the visible chart as PNG
Review team and member permissions
Find teams without an owner or eligible routing member

Child-team membership can provide access and assignment through parent teams. Review inherited permissions before changing a hierarchy.

Changes save automatically.

Invite people by email from Workspace Settings → Users. Recipients can create an account with the invited address and accept the invitation from User Settings. Admins can review or withdraw pending invitations.

Removing a member clears their direct task assignments. The tasks remain available for active members to reassign.

Capacity and availability

Capacity considers working hours, meetings, task and ticket workload, holidays, out-of-office events, and vacations. Admins can use this information in People view and ticket routing.

Members configure planned absence under User Settings → Calendar and can choose a replacement. During the absence, Bnder can hand directly assigned work to that replacement and return it afterward when the assignment was not changed manually.

See Vacation Handoff.

Discord role import

Discord workspaces with Pro can import Discord roles into Bnder teams. Import is a one-time copy, not a live sync. Review native Bnder permissions after import, because Discord role permissions do not carry over.

Managed bot and integration roles are skipped.

Ticket routing

Configure routing policies under Workspace Settings → Tickets. Policies can match project, type, customer, priority, SLA, or labels and target people or teams.

Assignment options include:

Capacity: choose an eligible person with available capacity
Rotation: distribute tickets through a preferred order
Fallbacks: use backup users, managers, team leads, or escalation users

Routing can run for a new unassigned ticket, a manual reroute, an SLA warning, or an SLA breach. If no eligible target exists, the ticket remains unchanged or unassigned.

Use routing preview before relying on a policy. After routing, Routing Insights explains the matched policy, selected person, skipped candidates, and fallbacks.

Clean up old references

Inactive or deleted people can remain visible where historical context matters. Organization settings identifies stale team, member, project, or routing references that an admin can safely clean up.