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

# Case Management

> Investigate users, businesses, verifications and transactions in one place — with blueprints, load-based assignment, 4-eyes review, and regulatory reporting.

Case Management is the investigation hub of the Didit Console: every alert, flagged verification, or suspicious transaction can become a **case** that your compliance team works from open to resolution — with a full audit trail.

***

## Cases

A case links any mix of entities — users, businesses, KYC/KYB verifications, transactions, payment methods, devices, network addresses — into one investigation with a status (**Open**, **Under review**, **Awaiting user**, **On hold**, **Pending approval**, **Resolved**), priority, severity, typologies, comments, evidence, and a checklist.

Create cases:

* **Manually** — from the Cases page, or directly from a session, business, or transaction.
* **Automatically** — add the **Open case** action to a transaction-monitoring rule. The case is created once per transaction and linked automatically.

Filter the list by status, and by what the case is **about** (users, businesses, transactions, verifications). Select several cases to bulk-assign them to an officer.

## Blueprints and team workflows

Blueprints define how a category of cases is handled:

* **Assignment** — manual, or **load-based**: the case goes to the pool member with the fewest active cases. Officers currently online in the console are preferred.
* **Max active cases per officer** — pool members at the limit are skipped; when the whole pool is saturated, new cases queue unassigned and are pulled automatically as soon as an officer resolves a case or comes online.
* **Auto-route typologies** — rule-created cases whose typologies match are routed to this blueprint (and its team) automatically.
* **4-eyes review** — see below.
* **Escalation blueprint, checklist, SLA due hours, and automatic regulatory-report drafts.**

## 4-eyes review (maker/checker)

On blueprints with 4-eyes review enabled, resolving a case does not close it: it moves to **Pending approval** with the proposed resolution attached. A **different** officer must approve (the resolution applies, credited to the submitting officer) or reject it (the case returns to Under review). The submitter cannot approve their own resolution — enforced by the API.

## Acting on linked entities

From a case's **Linked entities** tab you can act without leaving the investigation:

* Set a linked user or business to **In Review**, **Flagged**, **Blocked**, or **Active**.
* Open the full user, business, verification, or transaction view.
* Every action is recorded on the case timeline.

## Notifications

Each team member controls their own case notifications in **Account settings → Notifications**: case assigned to you, mentions, comments, status changes, and resolutions awaiting your approval — per channel (email, in-app, Slack, Telegram). "Assigned to you", mentions, and approval requests are on by default.

## Reports

* Generate **SAR/STR and other regulatory reports** from a case — see [Regulatory Reports](/console/regulatory-reports).
* Export **all cases** or the **SLA report** (timing metrics per case) as CSV from the Cases page; files are delivered through the Reports page.