> For the complete documentation index, see [llms.txt](https://docs.ggwp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ggwp.com/dashboard-user-guide/incidents-list.md).

# Incidents List

<figure><img src="/files/B00y5G8krYLBUxkRzUlG" alt=""><figcaption></figcaption></figure>

You can find the incidents list by clicking on the `Incidents` option in the left nav. At the top you'll see high level stats from the past 30 days, including:&#x20;

* Total incidents - number of incidents detected&#x20;
* Filtered messages - number of messages filtered&#x20;
* Auto-moderated incidents - incidents reviewed by automod, regardless of whether or not a sanction was applied
* Auto-sanctioned incidents - incidents reviewed by automod that resulted in an automatic sanction being applied
* Priority review incidents - incidents flagged by automod as recommended for manual review&#x20;

The incidents list is a list of detected incidents, and the table view includes the following information:&#x20;

* Incident ID - clicking on this will bring up the incident information modal. From here you can update the incident status, provide feedback, and view more details.
* Player - clicking on the player's username will open the player details page
* Score - the player's reputation score
* Incident type - the type of incident that occurred (ex: identity hate, threat)
* Severity - the severity of the incident (low, medium, or high)
* Confidence - how confident we are that the detection is accurate, based on factors like player history and other contextual information
* Time - the time the incident occurred in UTC (or your personal timezone setting)
* Incident status - for manual review workflows, you can select an incident status from the dropdown to mark which tickets are in the process of being reviewed, have already been reviewed, have been escalated, or archived.&#x20;
* Assignee - dashboard user assigned to review the incident. You can select an assignee from the dropdown here, which also features a search option.&#x20;

#### Filtering incidents&#x20;

If you have incidents from multiple sources (chat, voice, Discord, usernames, image, or player reports), you can select which source you'd like to view by using the `Source` dropdown in the upper left side of the page.&#x20;

The prioritized toggle to the right of the source dropdown will show a list of incidents for priority review.  Note that the logic for this view will be different depending on whether or not you have automod enabled. If automod is enabled, the logic will be based on your custom settings (please contact your GGWP rep to set this up). If automod is not enabled, this view will show incidents from the last 72 hours and selects a mix of high/medium severity and confidence incidents.&#x20;

You can filter by various criteria, such as date range, severity, and confidence. Clicking the plus button to the right of the main filter dropdowns will bring up even more filtering options, including assignee, incident status, incident type, language, and rep score. You can also reset or save your filter anytime.&#x20;

<figure><img src="/files/VHAOo4nmjs50BtmeGjm4" alt=""><figcaption></figcaption></figure>

To export a CSV of your incidents list view, click the `Export CSV` option in the upper right corner of the page and you'll receive an email with a downloadable link. Note that this feature supports a maximum of 10,000 rows.

#### Assigning incidents

Use the dropdown in the `Assignee` column of the list to assign a moderator to an incident. If you don't see an assignee in the dropdown, you will need to grant that person dashboard access from the [manage users](https://app.gitbook.com/o/4MoKWbNqD8YSWD6I9R0e/s/vWnBBbfoDLATxCkzTDNt/~/changes/143/dashboard-user-guide/admin-features#adding-and-removing-users) page (admin only).&#x20;

Tickets assigned to you will also appear in the `My Tickets` page, accessible from the option in the left nav.&#x20;

To bulk assign tickets, you can select multiple incidents in the list using the checkboxes to the left of the table.

<figure><img src="/files/SzFnEHXcMgl6EzZNC3mO" alt=""><figcaption></figcaption></figure>

**Incident information modal**

<figure><img src="/files/Jj913EmRxeKLfkhmstzr" alt=""><figcaption></figcaption></figure>

Clicking on an incident ID in the incident list will bring up the incident information modal. From here, you can update the incident status or give feedback on the accuracy of the detection. Using the incident accuracy dropdown, you can report false positives (when something should not have been flagged as an incident) and inaccurate labels (the incident was valid but was mislabeled). Reporting false positives and inaccurate labels helps train our models for improved performance over time.

If you are viewing a voice incident, the audio will be shown as transcribed text for easier review, and you also have the option to play the original audio or download the audio file. Discord incidents include a link to the original message in Discord as well. For image incidents, images open blurred by default, and moderators have options to progressively reveal them, so they’re only exposed to harmful content to the extent needed to make a moderation decision.

To make incident review as efficient as possible, several keyboard shortcuts are available when viewing the incident information modal:&#x20;

* `N` - go to next incident
* `P` - go to previous incident
* `F` - update incident accuracy to False Positive
* `A` - update incident accuracy to Accurate
* `U` - open “update label” model options (from there you will need to move your mouse to update the form and submit)
* `L` - (if applicable) open Discord message link / open linked URL
* `Enter`/`return` - submit
* `esc` - close/dismiss

### Incident details&#x20;

Clicking on `View Details >` from the incident information modal will open the incident details page.&#x20;

<figure><img src="/files/P0STDEX03dMAhhrTugoN" alt=""><figcaption></figcaption></figure>

From here, you can view additional information about the incident that occurred, as well as a summary of the player's history, including past incidents, sanctions, and reputation score history.&#x20;

For chat incidents, you'll see the session conversation history to view the incident within the context of the conversation. For player reports, you'll see information about how many other reports have been received for that user by month and by category of report.&#x20;

You can also sanction the player by clicking on the `Sanction Player` button in the upper right of the page. Select one or more channels you want the sanction to apply to, select the duration the sanction should be in effect for, and then click to confirm.&#x20;

Sanction ladder dropdowns are in the upper right corner of the page. Click the dropdown and select an option to change a user's position on each ladder.&#x20;

Note: A sanction ladder is a system of progressively stricter sanctions for players who are repeat, high-severity offenders. The ladder kicks in when automod is switched on, but moderators can manually override a user's position on the ladder using this dropdown. When automod is on, a player's position on the ladder determines the duration of the sanction they will receive for certain types of incidents.&#x20;
