Staff Tools

The duty system helps server owners track which staff members are actively moderating. Staff members toggle their duty status using /duty on and /duty off. When on duty, all of their moderation actions (bans, kicks, warns, mutes) are tracked and attributed to their duty session.

The dashboard provides a duty log that shows when each staff member clocked in, how long they were on duty, and a summary of actions taken during each session. This data is invaluable for identifying your most active staff, ensuring coverage across different time zones, and addressing staff burnout before it becomes a problem.

You can configure duty reminders — if a staff member takes a moderation action while off duty, the bot can send them a gentle reminder to toggle duty on. This ensures accurate tracking without being punitive. Staff can also set a duty schedule from the dashboard, indicating their typical availability windows.

Duty statistics are visible to all staff members via /duty stats, which shows personal metrics, and /duty leaderboard, which shows team-wide comparisons. Server owners can view detailed reports from the dashboard with exportable data.

When a member submits a staff application (via the ticket system), it appears in your designated staff applications channel. The bot posts an embed with the applicant's answers, account creation date, server join date, and any mutual servers with existing staff members for context.

Reviewing an application follows a structured workflow. Use /applications to see all pending applications ranked by submission date. Clicking an application shows its full details. From there, staff can discuss the application in a private thread that is automatically created and linked to the application.

To approve an applicant, use /accept @user. You can optionally specify a trial period duration — the applicant receives a temporary staff role that automatically expires after the trial. To reject, use /deny @user <reason>. The reason is sent to the applicant via DM, and the application is marked as closed.

Approved members are automatically granted the configured staff role. If you set a trial period, the temporary role converts to a permanent staff role after the trial ends, at which point the bot notifies the new staff member with onboarding information.

Recognizing staff achievements is important for team morale. Use /promote @user <role> to promote a staff member to a higher role. The promotion is logged and announced in your staff channel. You can attach a reason or commendation that appears in the promotion announcement.

The /award command lets you grant recognition badges to staff members. Awards are displayed on the staff member's profile in the dashboard and can be seen by other staff. Built-in awards include 'Top Moderator' (most actions in a month), 'Fastest Responder' (quickest ticket closure), and 'Most Helpful' (most thank-you reactions).

From the dashboard, you can create custom awards with custom icons and criteria. For example, 'Crisis Manager' could be awarded for handling a significant server incident, or 'Mentor' could be awarded for training new staff members. Awards can be one-time or renewable (e.g., monthly awards).

All promotions and awards are recorded in the staff audit log. The dashboard provides analytics showing promotion timelines, award distributions, and staff retention rates to help you make informed leadership decisions.

Staff members can request time off using /loa start <duration> <reason>. This pauses their duty tracking for the specified duration — while on leave, their off-duty period is not counted against their activity metrics. When the leave ends, duty tracking resumes automatically.

Server owners and administrators can view all active and past leaves from the dashboard's Staff > Leaves page. The page shows who is currently on leave, when they are expected to return, and a history of past leaves. This helps with scheduling coverage and ensuring you are never short-staffed.

You can configure leave policies from the dashboard: maximum concurrent leave duration, minimum notice period, and whether leave requires manager approval. If approval is required, leave requests are sent to a designated channel where managers can /loa approve or /loa deny them.

When a staff member returns from leave, the bot can optionally send a welcome-back message to the staff channel and reset their duty status to off (so they can manually clock in when ready). LOA history is visible on the staff member's profile for performance review context.