Skip to main content
After a disclosure request is approved and a case becomes active, you may need to adjust which auditors are working on it. As an Application Administrator, you can add new auditors to give them access to the case workspace, or remove existing ones to revoke their access — all without affecting the case’s approved scope or investigation data. These adjustments are reflected immediately and tracked in the audit log.

​
Before you begin

Before managing auditors on a case, confirm the following:
  1. The case must be approved. Auditor assignments can only be managed on cases that have passed the approval stage. Pending or closed requests do not have a case workspace.
  2. You need cases:edit to use the add and remove auditor controls. Without this permission, the management controls on the Case Auditors tab are read-only or hidden.
  3. You need reports:view_transactions to view the case workspace and access the Case Auditors tab at all. This permission is part of the Auditor permission bucket and must be granted separately from cases:edit.
If you are missing either permission, contact your Organization Administrator to update your application permission buckets.

​
Manage case auditors

1

Open the application workspace

Sign in to the Arcane portal and select the application workspace that contains the case you want to manage.
2

Open Case Review and select a case

In the sidebar, click Case Review. Browse or search the list of approved cases and click the one you want to manage. Only approved cases appear in this view.
3

Navigate to the Case Auditors tab

Inside the case workspace, click the Case Auditors tab. You will see a list of all team members currently assigned to this case.
4

Add an auditor

To grant a team member access to this case, click Add auditor. Select the team member from the list of eligible users in your organization, then confirm the assignment. The auditor is immediately added to the case.
5

Remove an auditor

To revoke a team member’s access, find their row in the auditor list and click the remove control. Confirm the action if prompted. The auditor loses access to the case workspace right away.

​
How it affects access

When you add an auditor, they immediately appear in their case worklist and can open the case workspace. They can view transaction data within the approved disclosure scope for as long as the case access window remains active. When you remove an auditor, they lose access to the case workspace immediately. They will no longer see the case in their worklist. Their assignment record is soft-deleted — the history of their access is preserved for audit purposes, but they cannot open the case.
Having the reports:view_transactions permission on an application does not automatically grant access to every case in that application. An auditor must be explicitly assigned to each individual case before they can open it. Application-level permissions are a prerequisite, but case-level assignment is always required.

​
Relationship to team permissions

Access to case data requires two separate layers working together: Application-level permissions are set by your Organization Administrator through the Team management area. These permissions are grouped into buckets (Common, Administrator, Auditor) and determine which workspaces and features a team member can access within an application. For example, reports:view_transactions allows a user to view transaction data — but only on cases they are assigned to. Case-level assignments are set by you, the Application Administrator, on each individual case. These assignments determine which specific approved cases an auditor can open. Both layers are required for an auditor to review case data. A user with the right application permissions but no case assignment cannot open the case. Conversely, a case assignment alone does nothing without the underlying application permission bucket in place.