A case is a time-limited review boundary for private transaction evidence in one application. It records why access is required, which historical period is in scope, which fields may be disclosed, and which auditors may review the approved evidence.
Arcane evaluates the applicable authorization policy when you submit the request. An approval-gated request remains pending. A request that matches a preauthorization can open immediately without bypassing policy.

​
Before you begin

Confirm that:
  • you are working in the correct application;
  • your application assignment includes the cases:create permission;
  • at least one eligible auditor is available for assignment;
  • the requested review period, access duration, and disclosure fields are proportionate to the stated purpose.
An auditor is eligible for case assignment when they belong to the same organization, have access to the current application, and hold the reports:view_transactions permission for that application.

​
What the request defines

The Review period and Access duration serve different purposes. The review period limits which historical transactions are included. The access duration limits how long assigned auditors can inspect that evidence after the case is approved.

​
Create a case request

1

Open the application

Select the application that owns the transaction evidence. Case requests, approvals, assignments, and approved cases remain isolated to this application.
2

Open Case Review

Open Case Review and select Request Investigation Case.
3

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

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

Set the access duration

Define the temporary access period required for the review. Access begins when the authorization policy creates the Case and ends when the configured duration expires.
6

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

Select the disclosure scope

Start with evidence metadata and enable only the confidential fields required for the stated purpose. Amounts remain hidden unless you select them.
8

Review and submit

Review the application, basis, period, duration, assigned auditors, and disclosure fields. Confirm that access is time-limited and logged, then select Submit Request.

​
Disclosure scope

The approved case always includes non-secret evidence metadata such as date, operation type, asset, chain, and contract context. Confidential values and sensitive identifiers remain hidden unless the request explicitly includes them.
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

The requester can withdraw a pending request if it is no longer required. An authorized approver can approve or reject it with a decision reason. When the stored authorization policy is satisfied, Arcane creates a stable case ID, applies the approved application and Asset scope, and activates the recorded auditor assignments. All request creation, approval, rejection, withdrawal, and auditor-assignment changes are recorded in the activity history.

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