Review incidents#

Incidents are player reports of other players breaking the rules of your online community or otherwise committing offensive behavior (committing an offense). Each incident has:

• A unique ID
• A timestamp
• An offense type
• A reporter
• An offender
• An assignee
• A status

If Safe Text is enabled, incidents can be automated detections captured by those services. Incidents will include the scoring of each services.

For more information about the different incident types, refer to Incident types

Safety Moderators and Admins can view, evaluate, and respond to all moderation reports from the dashboard. To access the incident reports from the Unity Dashboard, go to Vivox > Safe Text > Moderation queue.

Incident status#

The Moderation dashboard separates incidents into two groups based on their status:

• Unresolved incidents
• Resolved incidents

When resolving an incident, moderators can choose to:

• Perform an action against the offender.
• Perform an action against the reporter.
• Perform an action against both the offender and the reporter.
• Take no action.

Refer to Resolving incidents for the steps to resolve an incident.

Note: Moderators can apply different actions, and durations, to the offender and the reporter. They don't need to be the same.

Incident details#

Each incident report, whether it’s unresolved or resolved, has the following information:

• ID: The unique identifier of the incident.
• Timestamp: The time and date at which a player reported the incident.
• Offense type: The type of offense the incident reports. Refer to Offenses for a list of offense types.
• Reporter: The player who reported the incident.
• Offender: The player who committed the offense.
• Assignee: The Organization User assigned to the incident.
• Status: The status of the incident (pending, in progress, or resolved).

Note that Resolved incidents have a field for Actions that have been taken.

For more details on what's contained within an incident, refer to Incident details