Creating a case starts an approval request. It does not provide immediate
access to private evidence. The case opens only after an authorized
application administrator approves the request.
Before you begin
Confirm that:- you are working in the correct application;
- your application assignment includes the
cases:createpermission; - at least one eligible auditor is available for assignment;
- the requested review period, access duration, and disclosure fields are proportionate to the stated purpose.
reports:view_transactions permission for that application.
What the request defines
| Field | What to provide |
|---|---|
| Basis | Select Internal Investigation, External Audit, or Regulator Request. |
| Reason | State the investigative purpose, the evidence required, and why the proposed boundary is sufficient. |
| Review period | Set the first and last dates of the historical transaction activity to be reviewed. |
| Access duration | Set how long assigned auditors may access the case after approval. The duration begins when the approved case is created. |
| Assigned auditors | Select one or more eligible auditors from the current application. Only assigned auditors can access the approved case. |
| Disclosure scope | Select the elevated identifiers or address fields required for the review. Unselected sensitive fields remain hidden. |
| Application scope | The current application supplies the default contract boundary for the case. |
Create a case request
Open the application
Select the application that owns the transaction evidence. Case requests,
approvals, assignments, and approved cases remain isolated to this
application.
Record the purpose
Select the request Basis and enter a clear Reason. The reason should
allow an administrator to assess the purpose and proportionality of the
requested disclosure without relying on information outside the request.
Define the review period
Set Period From and Period To. Only interpreted transaction evidence
within this inclusive date range can appear in the approved case.
Set the access duration
Define the temporary access period required for the review. Access begins
only after the request receives the required approval and ends when the
configured duration expires.
Assign auditors
Select at least one eligible auditor. The assignment is retained with the
request and transferred to the case when the request is approved.
Select the disclosure scope
Start with the standard masked view and enable only the additional fields
required for the stated purpose.
Disclosure scope
The approved case always includes the transaction information required for a scoped review, such as date, operation type, amount, asset, chain, and contract context. Sensitive identifiers remain hidden unless they are explicitly included in the request.| Option | Effect after approval |
|---|---|
| Full transaction hashes | Reveals complete transaction identifiers for in-scope records. |
| Full counterparty addresses | Reveals sender information for in-scope records when that information is available. |
| Withdrawal destination details | Reveals recipient or withdrawal-destination information when that information is available. |
Selective disclosure changes which fields are visible; it does not expand
the application, contract, review-period, assignment, or access-duration
boundary.
What happens after submission
| State | What it means |
|---|---|
Pending | The request is waiting for an application administrator with cases:approve_creation to review it. No case evidence is available yet. |
Active | The required approval has been recorded, the case has been created, and assigned auditors can review the approved evidence until access expires. |
Closed | The request was rejected or withdrawn before it created an accessible case. |
Expired | The approved case reached the end of its access duration. Transaction and analytics access is blocked. |
Next steps
Manage users
Assign the application permissions required for case review and approval.
How the platform works
Review the complete disclosure and approval model.