Staff directory
Review server-team membership and visible staff profile context without confusing directory visibility with effective authority.
- Audience
- moderator · senior reviewer · team lead · server admin
- Availability
- private beta access
- Maturity
- alpha · partial
Last reviewed
On this page
Understand who can do what
The Staff Directory lists server-scoped staff profile information and can synchronize supported Discord role context. Management controls for profiles, notes, roles, promotion, or removal require their own permissions.
Read roles, teams, and presence carefully
Viewing requires staff_directory.view. Administrative details and management actions are exposed only when the viewer has at least one relevant management permission.
Open Staff Directory in the selected server, review the visible roster, and use role synchronization only through the supported server-scoped control.
- The intended server selected.
- Permission to view the staff directory.
- A concrete roster, profile, role, promotion, or removal question.
Find the right person for a handoff
Review the roster
Confirm the staff member's Discord identity, displayed profile, and current visible status.
Check: The viewer identifies the intended server-team member.
Compare effective access
Use the operation's permission result or administration team mapping rather than inferring authority from a label.
Check: Directory display and permission authority remain separate.
Use guarded management
Open only the profile, note, role, promotion, or removal control your permission allows.
Check: Sensitive staff actions remain least-privilege and attributable.
Refresh stale role context
Use supported role synchronization and then recheck the live operation.
Check: Cached directory context is updated without becoming a permission bypass.
Staff handoff examples
Authorized viewers can locate server staff and their visible profile context while management actions continue to enforce independent permissions.
- Find the reviewer assigned to a case by exact Discord identity.
- Treat a displayed team role as context, then verify the action-specific permission.
- Include removed staff only when the current view and permission intentionally support it.
Understand directory fields and authority
| Field | What it means | What it does not mean |
|---|---|---|
| Discord identity | Current resolved account/name/avatar for this server. | A permanent global identity label. |
| Mapped team/role | Current directory context from configured server roles/teams. | Automatic permission to every team function. |
| Enabled/active status | Whether the server’s staff profile is active in the directory workflow. | Proof the person is online or available now. |
| Visible specialties/profile fields | Server-authored staff context. | An enforcement permission or formal credential unless server policy says so. |
| Basic activity | Recorded server-scoped actions where the viewer may see them. | A quality score, ranking, or performance verdict. |
Find the right staff member for a handoff
Identify the required capability
Name the missing permission or expertise: restricted evidence, appeal decision, ban execution, settings, export, or voice evidence.
Check: The handoff asks for a specific job.
Find an appropriate team/person
Use the directory and team mapping to locate an authorized candidate.
Check: The request does not go to every staff member.
Confirm current availability elsewhere
Use the server’s established staff coordination channel or process.
Check: Directory presence is not treated as live availability.
Send a minimum-data handoff
Share the record link/ID, current state, unresolved question, and next action.
Check: Private evidence remains in the guarded record.
Record ownership
Claim/reassign the Case or note the next owner where supported.
Check: Work does not disappear in chat.
Use role synchronization cautiously
| Check | Reason |
|---|---|
| Mapped Discord role ID | Names can change or collide. |
| Team enabled/order state | Order and enabled state can affect effective context. |
| Protected/admin roles | High-privilege roles must not be added or removed casually. |
| Bot hierarchy | The bot cannot manage roles above or managed by integrations. |
| Representative permission test | A refreshed directory does not prove action authority. |
Changing staff-performance features remain reserved
Changing staff-performance scorecards, rankings, evaluations, and unfinished intelligence workflows are intentionally outside this guide. Their existence in branch code, tests, or internal planning does not create an approved staff-management procedure.
| Need | Documented alternative |
|---|---|
| Understand one action | Open the action record and linked Case. |
| Review a shift or date range | Use /modhistory, /modstats, and Moderation Log with source-record review. |
| Balance workload | Use Case assignment/claim/reassign and server coordination practices. |
| Correct permissions | Use Moderation Teams and operation-specific tests. |
| Discuss staff conduct | Use the server’s authorized human supervision process outside undocumented scoring controls. |
Do not infer availability or authority
Role caches and resolved Discord identity can become stale. The directory is server-specific and does not create a global staff roster or authority model across servers.
Something is missing or looks wrong
What you see: The current view does not contain the record, field, source, or output you expected.
What may be happening: Server scope, viewer permission, filters, source availability, feature gates, or stale state can change what the product may show.
What to do
- Confirm staff_directory.view and the selected server.
- Refresh supported role context.
- Recheck the permission at the intended action.
- Ask a server administrator to correct team membership instead of relying on a display label.
Protect staff review data
Directory membership and ordinary activity are not the same as administrative notes, evaluations, or a Performance Scorecard. Those records require narrower permissions. Scorecards are a default-off controlled preview and must not be used for automatic role, promotion, assignment, or removal decisions.