Skip to main content

User-submitted reports

The reports surface lets viewers flag downloads, comments, or reviews for moderator attention. Flagged content lands in the same Reports queue as flagged threads and posts.

Reporting from the public surface​

Any logged-in user with the relevant report permission can submit a report.

Reporting a download​

  1. Visit the download view.
  2. Click the menu (three-dot icon) next to the title.
  3. Choose Report.
  4. Pick a reason and optionally add a note.
  5. Click Submit.

Reporting a comment​

  1. Hover over the comment.
  2. Click Report.
  3. Same reason flow.

Reporting a review​

  1. Click the menu on the review.
  2. Choose Report.
  3. Same flow.

Where flagged content lands​

AdminCP > Reports.

Reports for downloads-manager content can be filtered by content type. Use the filter dropdown to pick "Downloads manager: Download", "Downloads manager: Comment", or "Downloads manager: Review".

Resolving a flag​

The standard report flow applies:

  1. Open the entry from AdminCP > Reports.
  2. Read the submitter's note and the content snapshot.
  3. Choose:
    • Resolve. Mark as handled and close.
    • Reject. Mark as not actionable and close.
    • Add comment. Discuss with other moderators inline.
    • Take action. Use the standard inline-mod controls on the linked content.
  4. Optionally notify the submitter when resolving.

Permissions​

Submission permissions for downloads and comments use the standard "report content" permission. The Reviews user group has its own Report permission for reviews.

Moderators need the "manage reports" permission to resolve reports, granted at AdminCP > Groups & permissions > Permissions > Moderator permissions.

Audit log​

Resolving and rejecting flags is recorded in the standard moderator log, not the add-on's audit log. Any actions taken on the flagged content (such as soft-deleting a flagged download) are recorded in the add-on's audit log as normal.

What is not flag-able​

  • Categories.
  • Versions individually (flag the parent download).
  • Files individually (flag the parent download).

Spam vs user flags​

User flags are submitter-initiated. Spam handling is automatic: the spam check fires on comment and review submission, and flagged-as-spam content routes through the moderated state without a user flag ever being filed. The two paths are independent.