AuditEncodedDigest events, decrypts and indexes the audit payloads, and provides structured workflows for requesting, approving, and reviewing transaction disclosures. Your auditors never touch raw on-chain data — they work through a governed workflow where access is always tied to an approved disclosure case, scoped to a specific application, and limited to the data fields your organization has authorized for disclosure.
What the portal does
Automatic indexing
The Arcane Scanner monitors the Stellar ledger for audit events from every registered contract. Audit data is indexed continuously, so it is available for disclosure review whenever a case is opened — even for historical transactions.
Disclosure workflows
Auditors create disclosure requests for specific transaction periods. Application administrators review each request and either approve it (opening a case) or close it. Approved cases are time-bound and scoped to the requesting auditor.
Scoped transaction review
Once a case is approved, the assigned auditor can review the interpreted transaction data for that case — and only that data. Access is limited to the fields approved during the disclosure decision.
Reports and audit logs
Auditors and administrators can generate and download transaction reports for approved cases. Every compliance action — request creation, approval decisions, case access, report generation — is automatically written to an immutable activity log.
Disclosure workflow
A disclosure case follows a structured lifecycle from request to review. No auditor can access transaction data without an administrator first approving their request.Auditor creates a disclosure request
An auditor submits a disclosure request specifying the transaction period and the data fields they need access to. The request enters a pending state and notifies the application administrator.
Administrator reviews the request
The application administrator reviews the request and either approves it or closes it. When approving, the administrator sets the access window (how many days the case remains open) and assigns the auditor to the case.
Case opens and auditor is notified
Once approved, a case is created and the auditor gains access to the interpreted transaction data for the specified period. Access is strictly scoped to the approved fields and expires automatically when the access window closes.
Auditors can withdraw their own pending requests before an administrator has acted on them. Once a case is approved, only the administrator can modify case access.
Access model
Data access in the Auditing Portal is controlled at three levels, each narrowing the scope of what you can see.| Access level | What it controls |
|---|---|
| Organization | Which organization workspaces and organization-level reports you can access |
| Application | Which application workspaces appear in your portal and what actions you can perform within them |
| Case | Which specific approved cases you can open and review as an auditor |
Access to interpreted transaction data also respects the disclosure flags set at case approval. If an administrator approves a case without enabling sender information disclosure, you will not see sender details even if you hold
reports:view_transactions permission.Activity logging
Every compliance action you take in the Auditing Portal is automatically recorded in the activity log — no manual logging required. The log captures request creation and withdrawal, administrator approval and closure decisions, case access events, report generation, and report downloads. Activity logs are available at both the organization level (for organization administrators) and the application level (for administrators and auditors with thelogs:view_activity permission). Logs can be exported for use in external compliance systems.
For a full breakdown of who can perform which actions, see Roles & Permissions.