Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions concepts/reports.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ description: "How suspicious or safe activity gets submitted to ChainPatrol for
A **Report** is how suspicious or safe activity gets submitted to ChainPatrol for review. Each report bundles together one or more assets, like websites, social profiles, or crypto addresses, along with the evidence needed to evaluate them.

<Info>
When you create a report, you're proposing that specific assets should either be **blocked** (because they're malicious) or **allowed** (because they're safe).
When you create a report, it starts in **NEEDS_REVIEW** status (waiting in the review queue), then moves to **IN_PROGRESS** (actively being reviewed), and finally **CLOSED** (review complete).
</Info>

### What a Report Contains
Expand Down Expand Up @@ -71,7 +71,7 @@ Even after ChainPatrol's team approves a report, the changes won't be applied to

Reports move through three stages as they're processed:

- **TODO** - The report is waiting in the queue for review
- **NEEDS_REVIEW** - The report is waiting in the queue for review
- **IN_PROGRESS** - ChainPatrol staff or automated systems are actively reviewing it
- **CLOSED** - The review is complete and decisions have been made on all assets

Expand All @@ -97,7 +97,7 @@ Creating a report in ChainPatrol is straightforward:

### What Happens Next

**Immediately** - Report enters TODO status, you receive confirmation, report appears in your dashboard, and ChainPatrol team is notified.
**Immediately** - Report enters NEEDS_REVIEW status, you receive confirmation, report appears in your dashboard, and ChainPatrol team is notified.

**During Review** - Status changes to IN_PROGRESS, assets are scanned and analyzed, evidence is evaluated, and decisions are made.

Expand All @@ -118,4 +118,4 @@ Creating a report in ChainPatrol is straightforward:
- Multi-asset reports capture campaign scope: Grouping related threats in one report helps reviewers understand attack patterns and makes blocking entire campaigns more efficient
- Context accelerates review decisions: Reports with screenshots, explanations, and evidence of harm move through review faster than bare URLs with no context
- Three submission methods serve different needs: Manual reports for ad-hoc discoveries, API reports for automated detection systems, and portal reports for community submissions
- Report status tracks progress without micromanagement: TODO, IN_PROGRESS, and CLOSED states provide visibility while letting the security team work without constant updates
- Report status tracks progress without micromanagement: NEEDS_REVIEW, IN_PROGRESS, and CLOSED states provide visibility while letting the security team work without constant updates
4 changes: 2 additions & 2 deletions getting-started/how-it-works/review.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ description: "How ChainPatrol evaluates and approves threat status changes throu
In order to block malicious threats or allow official assets, we use the Review process. To change an Asset's status (from `UNKNOWN` to `BLOCKED`/`ALLOWED`, or in special cases between `BLOCKED` and `ALLOWED`), we create a **Proposal**.

<Info>
Each Proposal is evaluated by either human reviewers or our automation, who can make one of four decisions: **Approve**, **Reject**, **Skip**, or **Escalate**.
Each Proposal is evaluated through our review process, which moves reports from **NEEDS_REVIEW** (waiting in queue) → **IN_PROGRESS** (actively being reviewed) → **CLOSED** (review complete). Proposals are evaluated by either human reviewers or our automation, who can make one of four decisions: **Approve**, **Reject**, **Skip**, or **Escalate**.
</Info>

### Proposal Decisions
Expand Down Expand Up @@ -101,4 +101,4 @@ Since automation only handles Proposals to block Assets with high confidence sco
- Legitimacy rules protect you from overblocking: If a Very High confidence legitimacy rule passes, the proposal goes to human review regardless of risk score
- Escalate unclear cases strategically: Use "Skip" when you need more information, "Escalate to Team" for expertise, and "Escalate to Customer" when brand context matters
- Automation learns from humans: Every manual review decision feeds back into the system, improving future automatic detection accuracy
- The four-decision model prevents deadlock: Unlike binary approve/reject systems, Skip and Escalate ensure unclear threats get proper attention without forcing premature decisions
- The four-decision model prevents deadlock: Unlike binary approve/reject systems, Skip and Escalate ensure unclear threats get proper attention without forcing premature decisions