> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revexscanner.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How it works

> From scan request to evidence report.

## The flow

1. **Staff creates a scan** in the panel (or through the API) and receives a PIN.
2. **The player approves.** They enter the PIN in the scanner and accept the consent text.
3. **The scanner collects evidence** from the computer: file signatures, execution traces, deleted files, event log checks, loaded modules, services and more.
4. **A report is built.** Findings are ranked by severity and grouped by category.
5. **Staff reviews the evidence** and records a decision (ban or clear).

## What a report is and is not

> [card] It is
>
> A ranked list of findings with the evidence behind each one.

> [card] It is not
>
> An automatic ban. The report never bans anyone; the decision stays with your staff.

## Severity levels

| Level | Meaning |
| - | - |
| Critical | Strong evidence of cheating software or a bypass tool. |
| High | Serious signs that need a close look. |
| Medium | Worth reviewing; may have an innocent explanation. |
| Low | Weak signals; read them in context. |
| Info | Context only; does not count toward the result. |

> [!WARNING]
>
> A single weak signal is not proof. Always read findings together with their evidence before deciding.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.