Handle reports and sanctions

A report is a situation to investigate. A sanction records a decision. Internal warnings about a staff member belong to their staff profile and are separate from player sanctions.

The Reports and Sanctions screens require sanction-management permission.

Open and investigate a report

Create a report with the player’s name, Discord ID when known, category, factual description and useful evidence links. The new record starts open.

Claim or assign the report, check the evidence, write a resolution note explaining the checks and decision, then resolve or reject it. Converting it to a sanction creates a linked decision; review its type, reason and duration first.

A completed report usually needs a final status and explanation, not deletion. This lets other managers understand what happened.

Record a sanction

Open Sanctions, create a record, choose its type and target, enter a clear reason and any required duration, then save and inspect the result. Temporary bans need a valid Discord ID. Staff hierarchy can prevent sanctions against equal or higher ranks.

Recording is different from applying a Discord action

Creating a sanction in the panel records the decision and notifications. It does not directly execute a Discord kick, ban or mute. Open the saved sanction and confirm Apply on Discord, or use the appropriate /sanction flow, then inspect its result. Game connectors are not currently an available path for applying these sanctions.

Find history and lift a sanction

Search the sanctions list by name or Discord ID, then filter by type, staff member and period. The player record combines sanctions, reports and internal notes. Prefer Discord IDs to names that can change or be shared.

Removing a sanction may require lifting its corresponding Discord restriction. If lifting fails, StaffNest keeps the record so the action can be retried. Check the real outcome before repeating anything. See the Discord command reference.

Warn a staff member

For an internal staff warning, open their Staff profile and use Warn. This follows the profile’s warning history rather than the player-sanction history.

If an action is denied, check your StaffNest permissions, the target’s rank and, for Discord actions, the bot’s permissions and role hierarchy. A recorded decision or notification alone does not prove Discord applied it.

Check the Discord outcome

The detail distinguishes Recorded, Applying, Applied, Failed and Uncertain outcome. After a confirmed failure, correct the permissions and retry from the same record; it does not create another sanction. Lost responses and historical records without confirmation are never automatically replayed.

Temporary-ban expiry checks the current Discord ban before lifting it. If its reason cannot be linked to the StaffNest record, the ban is preserved for a manager to review. Historical bans require the old StaffNest attribution and the saved reason/duration to match.

The report command’s optional member selector saves the targeted Discord account’s ID. Without a selected account, the report remains associated with the entered nickname.

Keep private investigation notes

Open a report and use Investigation notes to record checks, reviewed evidence and next steps. These notes require the same management permission as the report. They stay in its investigation history and are not sent to Discord or to the reporter. Their text is excluded from the activity log.

Each note keeps its author and timestamp. Newest notes appear first; use Older notes to load more. The author and the owner can delete a note after confirming: a “Note deleted” marker remains without its text. Notes do not replace the report’s final resolution.