---
title: Triage player reports
description: Handle challenge and platform reports from players through reply threads to resolution.
---

Players can flag problems from inside your event site: a broken challenge, a login issue, a slow page. Every report lands on the **Reports** page of your event dashboard, where you reply and close it. If your event's Discord server runs the Athena bot, tickets raised there land on the same page.

## How reports reach you

Players file two kinds of report:

- **Challenge reports**: the **Report** button on a challenge page. The player picks a preset reason and can add details. The presets are *"Flag does not work or was rejected incorrectly"*, *"Challenge instance / environment will not start"*, *"Description is wrong, missing, or confusing"*, *"Downloadable files are missing or broken"*, *"Offensive or inappropriate content"*, and *"Something else..."*. Choosing **Something else...** makes the details field required.
- **Platform reports**: **Report a problem** in the player's account menu. The player picks an affected area, then a preset for that area. The areas are *Login / account*, *Challenge list*, *Challenge pages (general)*, *Leaderboard*, *Profile / settings*, *Speed / errors*, *Announcements*, and *Other*.

Each report opens a thread. Players follow theirs on a **My reports** page, where they can post updates to open reports, so a thread can hold player updates and your replies interleaved.

## Get emailed when a report arrives

New reports don't announce themselves in the dashboard; fill in **Report notification emails** to hear about them as they land. The field holds up to ten addresses: type one and press Enter or comma to add it, or paste a comma-separated list. It sits on the create-event form under **Registration &amp; notifications**, editable any time in **Settings → Organizer alerts**. Every new report is emailed to all of them with the subject, the reason, any details the player wrote, who filed it, when, and the report's ID. Leave the field blank to turn the emails off.

Only the report that opens a thread is emailed; later updates a player posts to their own open thread are not. If a player still has an open report on the same challenge or platform area, a new submission joins that thread; it never starts a second.

## Find the report you need

The Reports page lists every report with its subject, reporter, status, and opening time. To narrow the list:

- **Search** by reporter name, `@username`, email, or subject.
- Filter by **scope** (*Challenge* / *Platform*), **status** (*Open* / *Closed*), or **area**. The area filter applies to platform reports.

Closed reports stay in the list, dimmed. Click any row to open its thread.

## Reply to the reporter

The thread pane shows every message with its author (**Player** or **Organizer**) and, for challenge reports, an **Open challenge** button that jumps straight to that challenge's edit page.

While a report is open, write in the **Organizer message** box and click **Add message**. Your reply appears in the player's thread on their My reports page. Once a report is closed, no one can add to the thread; replying to a closed report is rejected.

## Close a report

When a thread is done, pick a **Close reason**: **Resolved**, **Duplicate**, **Spam**, or **Not actionable**. Then optionally add a **Message on close**, and click **Close report**. A close message, when provided, is appended to the thread as a final organizer reply.

:::note[Resolved requires a reply]
Closing a report as **Resolved** requires at least one organizer message, either already in the thread or written in the close form. You'll see *"Resolved reports require an organizer message."* until there is one. The other three reasons don't require a message.
:::

Closing is one-way; there is no reopen. The player sees the outcome on their report: *Resolved*, *Closed as duplicate*, *Not actionable*, or simply *Closed* for reports you marked as spam.

## Discord tickets

On a Discord server with the Athena bot, a member with a linked account presses **Open a ticket** on the ticket panel. The bot walks them through the same choices the in-app report form uses: challenge or site, which challenge or which area, what went wrong, and the details. It then opens a **private thread** visible only to the reporter and staff, pinging the staff role.

**A Discord ticket is a report.** It appears on the Reports page like any other, and the two stay in step: what the reporter writes in the thread is added to the report, and a reply you post from the Reports page is relayed back into the thread shortly afterwards.

One exception to watch: a Discord ticket does **not** send the report-notification email described above. If you triage from your inbox, check the Reports page too.

A player can have one open report per challenge or area across both surfaces, so an in-app report blocks a Discord ticket about the same thing and vice versa. The bot links the existing thread where there is one.

The challenge picker in Discord lists up to 25 live challenges, so on a large event some reports will only be filable from the site.

Closing the thread with its **Close** button locks and archives it. That does not close the report; close it from the Reports page as usual.
