> ## 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.

# Creating Cases

> Open a case from a user, business, verification session, or transaction, manually or automatically through AML screening, transaction rules, and the workflow builder.

A case can be opened from any of the entities you already work with, or created automatically as your rules and workflows run.

***

## Manual creation

The same **Create case** dialog appears from every entry point:

* **Case title**, prefilled as `Manual - <subject name>`
* **Case blueprint** (required), with a **Manage blueprints** link if you need to set one up first
* **Assign to** (optional), with the current user shown first as `<your name> (Assign to me)`

Entry points:

* A user's detail page (overflow menu, and the user's **Cases** tab with **+ Create case**)
* A business's detail page (overflow menu, and the business's **Cases** tab)
* A KYC session's detail page (overflow menu)
* A KYB session's detail page (overflow menu)

Creating from any of these anchors the new case to that user or business automatically, satisfying the [one-subject-per-case](/console/case-management/cases#one-subject-per-case) rule without any extra steps.

## From a transaction

From a transaction's row menu, **Add to case** either:

* Attaches the transaction to one of the subject's existing open cases, or
* Creates a new case anchored to the transaction's subject and attaches the transaction to it.

Attaching a transaction that belongs to a different subject than the case is rejected, the console shows "belongs to a different profile" and the API returns a 400.

## Automatic creation

Three connectors open cases without an officer in the loop, each recorded with a distinct **source**:

| Source             | Trigger                                                                     | Configured in                           |
| ------------------ | --------------------------------------------------------------------------- | --------------------------------------- |
| `AML screening`    | An ongoing-monitoring AML hit, when the toggle is enabled on the AML config | AML settings, per verification workflow |
| `Transaction rule` | A transaction rule match with the **Create case** effect                    | The rule's effect configuration         |
| `Workflow builder` | A session completing a **Create case** node                                 | The workflow graph                      |

### AML screening

Enable **Create cases from ongoing monitoring hits** on a workflow's AML configuration and pick a blueprint. A second hit against a subject that already has an open case attaches to that case instead of opening a duplicate.

### Transaction rules

Add the **Create case** effect to a [transaction rule](/console/transaction-monitoring) with:

* **Blueprint** to route the case to
* **Grouping**: **By applicant** (reuses the subject's open case across every rule) or **By rule and applicant** (opens one case per rule per applicant)
* **Attach matched transaction**, to link the triggering transaction automatically

### Workflow builder

Add a **Create case** action node to a workflow graph, configured with a blueprint, priority, and due date. When a session reaches that node, a case opens with source `Workflow builder` and the session's user as its subject.

### Where connectors are visible

A blueprint's detail view lists every connector currently routing cases into it (**Connected sources**) and any blueprints that escalate into it (**Receives escalation from**), with shortcuts to the AML config, rule editor, or workflow builder that owns each connection.

## Manual vs. automatic sources

Manually created cases always carry source `Manual`. This distinction feeds the [analytics](/console/case-management/analytics) Creation source table, so you can see at a glance how much of your caseload originates from each channel.