Skip to content

Discord command reference

Find StaffNest commands, required parameters, date formats and permission requirements.

Type / in a server channel and choose StaffNest. Discord shows the registered commands and required parameters. The names and parameters below are those displayed by Discord when your Discord app is in English. Discord displays their French equivalents when its language is French; both refer to the same commands.

There are thirteen top-level commands. /sanction contains four subcommands. Seeing a command does not guarantee authorization to perform every action: Discord permissions, configured restrictions and StaffNest permissions all apply.

Private menus and confirmations follow your personal language preference, or your Discord language when no preference has been saved. Shared posts follow Settings → General → Bot language. Use /staffnest → Preferences to choose your personal language.

Command Parameters Purpose
/staffnest None Personal profile, tasks, absences, departments, meetings, summary and preferences.
/tasks None Task status, comments and creation according to permissions.
/departments None Accessible departments and teams, with management actions for authorized people.
/meetings None Meetings, invitation responses and authorized creation.

These commands open personal menus in the server. See the Discord workspace guide.

Command Parameters Purpose
/setup None Activation, staff role import and channels; requires Manage Server on Discord.
/absence Required: start, end, reason Submit an absence for a recognized staff member.
/absence-setup None Post an absence-request button in the current channel; requires authorization and Discord Manage Roles or Administrator.

For /absence, use DD/MM/YYYY. Optional times use DD/MM/YYYY HH:MM on both dates, or neither for a full-day absence. Times are interpreted in Europe/Paris, even if your account uses another timezone. The start cannot be a past day. The end cannot precede the start; with times it must be strictly later.

/absence start:05/11/2026 09:00 end:07/11/2026 18:00 reason:Planned unavailability

The form in /staffnest avoids remembering the syntax. Requests follow the team’s approval settings.

The confirmation is personal, but the request and reason can be posted to the configured absence channel, or the current channel if none is configured. Use a staff-only channel. If saving succeeds but notification fails, check the saved request before resubmitting it.

Approval buttons in Discord require a recognized staff account and Manage Roles. A department absence delegation alone permits the relevant panel flow, not this Discord permission. See absences.

Command Parameters Purpose
/staff None Post staff grouped by rank in the channel; includes active, warned and on-leave members, excluding inactive and former staff.
/staff-info Required: member Personal response with the selected member’s profile and authorized management actions.
/report Optional: period, channel Publish a weekly or monthly activity report; defaults to the week and current channel.

Weekly and monthly report periods cover the past 7 or 30 days. Headcounts and pending requests are current states; total-action rankings retain their own meaning. The target must be an accessible text or announcement channel. /report requires Manage Roles and the relevant StaffNest authorization.

/staff and /report publish information to the channel. Choose their audience before running them.

Command Parameters Purpose
/report-player Required: player, reason; optional: category, evidence Report a player to staff. Server members outside staff may use it when the module is available.
/record Required: member Personally view accessible player records, sanctions and notes; requires sanction management.
/sanction add Required: player Choose a sanction type, then complete the reason and any duration.
/sanction history Required: player Review the player’s sanction history.
/sanction stats None View sanction statistics.
/sanction remove Required: player Choose a sanction to lift; requires sanction management.

For reports, player is the player name and evidence accepts a link or evidence description. Categories cover cheating, toxicity, bug exploits, non-RP and other reports.

The sanction menu supports warnings, kicks, mutes, temporary mutes, bans and temporary bans. Choose a temporary type to specify duration; accepted examples include 30min, 24h, 7d and 2w. Discord history shows the ten latest sanctions and a total; use the panel for a broader view.

The initial sanction choice is personal, but the confirmed result may be posted in the channel. If the result says the sanction was recorded but the Discord action failed, inspect permissions and the record before repeating it. Recording a sanction in the panel or an automation is not equivalent to executing a Discord command. See sanctions and reports.

Check the server, bot presence, your staff profile, Discord permissions and Settings → Permissions → Bot commands. Reopen an expired menu.

Tickets use their Discord button or the help flow; there is no /ticket command in this reference. Use troubleshooting if the problem remains.