> ## Documentation Index > Fetch the complete documentation index at: https://docs.pup.run/llms.txt > Use this file to discover all available pages before exploring further. # Member and message reports > Review reports, assign follow-up and link moderation cases. ## Submit a private report In Discord, use `/report member: reason: consent:True`. For a message report, add `message:` from the same server. You must still belong to the server, but you do not need staff permissions. The server's moderation module, command and audience controls must permit reports. Choosing **True** shares your identity and reason with authorized server reviewers. Pup retains the reason for **30 days**; report status and review history remain later. Choosing **False** submits nothing. Reports do not post publicly or notify the reported member. Five submissions per minute are allowed; the verified server owner is exempt from this quota. No message content or attachments are copied by this command. Describe the issue in the reason (up to 2,000 characters). Pup confirms receipt privately. Contact a server moderator directly if you need immediate help or Pup cannot confirm submission. ## Find the review queue Open **Dashboard → Moderation → Reports** with the **Administer moderation** permission. Search by category, subject member ID or assignee member ID, filter by status, and use **Next** and **Previous** to browse older reports. Urgent reports appear first, followed by high, normal and low priority. ## Review a report Select **Review report** to see its status, priority, assignment, consent and attachment count, plus the private reason and reporter identity while the reason is retained. The list itself does not reveal reporter identity or report text. Opening a report checks your current **Administer moderation** access again. Expired or older reports without retained text explicitly show that the reason is unavailable. An attachment count does not mean Pup retained the files. 1. For a new report, select **Triage report**. Choose its priority and optionally assign it using a Discord member mention or member ID. Add a short review reason and select **Save triage**. Assignment does not grant report access. 2. After triage, **Accept report** for follow-up or **Dismiss report**. A new report can also be dismissed without triage. Assignment and priority are set during triage and cannot be changed afterward. Dismissed reports remain in history and cannot be reopened from the dashboard. 3. For an accepted report, select **Link case** and paste the dashboard link or ID of an existing case from the same server. **Open case** takes you directly to the linked case. Linking another case replaces the current link. Each action requires a review reason of up to 80 characters. Keep private report content out of this reason. Actions are checked against your current permissions and the current report and server settings. If the report changed while you were reviewing it, discard the draft and reload before continuing. If Pup cannot confirm an action's outcome, reload and check the status before trying again. ## Evidence and reporter privacy Case content and evidence require their own permissions. Linking a case does not share its decision, staff notes or evidence with the reporter. Reports require explicit consent, a category and a member or message source. Message reports require both a Discord channel and message reference. A source reference does not guarantee the original message is still available. A report's reply permission records whether a generic acknowledgement is allowed; it does not confirm that Discord delivered one. Report text and attachment contents remain outside the general queue and member history. Use the separately authorized case-evidence workflow when evidence needs to be captured or reviewed.