Member Approval
Some Discord workspaces are large or public, but only a smaller group should appear in internal assignment workflows. Member approval lets admins keep those internal pickers focused.
When the setting is enabled, admins explicitly approve the members who should appear first in Bnder's internal user lists.
Where to configure it
Open Workspace Settings -> Users and enable the option to only show manually approved users in internal member selectors.
After it is enabled:
- approved users are grouped at the top of the users tab
- all other members remain visible below the approved section
- expanded user rows stay in their current section while you edit them, so the list does not jump around
What approval affects
Approval affects internal assignment-style pickers, including:
- task assignees
- ticket assignees
- ticket assignee filters
- ticket SLA escalation users
- ticket routing and reassignment selectors that depend on member eligibility
Approval does not delete members, remove permissions, or hide users from audit views. It only keeps internal assignment workflows from accidentally targeting unapproved people.
How it works with Organization
Organization teams can still contain approved and unapproved members. In People views and permission review surfaces, approved members are shown ahead of the remaining members so admins can scan the active internal group first.
For team-based work, keep both the approval list and Organization Structure current. Approval controls whether a person is offered in internal selectors; team membership controls how Bnder understands team ownership, permissions, capacity, and routing.
When to use it
Use member approval when:
- a public Discord server has many community members
- only staff should receive task or ticket assignments
- support escalation lists should contain a curated internal team
- admins need a clear separation between workspace members and operational users
For smaller private teams, leaving this setting off is usually simpler.