Organization workspace
Your central management hub is the organization owner workspace. This workspace is separate from any application workspace and gives you a cross-application view of your entire Arcane Compliance environment. The organization workspace is organized into four main areas:| Area | What you do here |
|---|---|
| Applications | Create and manage application records linked to deployed contracts |
| Team | Invite team members and configure their permissions |
| Activity | Review organization-scoped audit events |
| Reports | Access organization-scoped compliance reports |
Manage applications
Each application in Arcane Compliance represents a deployed smart contract environment — for example, a Stellar liquidity pool or a confidential token program. Applications act as containers for disclosure requests, cases, reports, and audit logs. To create a new application, you need theapplications:create permission. To view existing applications, you need applications:read.
Provisioning a new application requires linking it to a deployed contract. Contact Arcane support to set up a new application and register the associated contract before it appears in your workspace.
| Field | Description |
|---|---|
foreign_id | A stable identifier used in portal routes and API calls — this is the segment that appears in /workspace/application/:foreignId |
name | The display name shown in the portal for this application |
application_type | The contract type — either stellar-pool or solana-confidential-token |
association.contract_id | The on-chain contract address registered to this application |
Manage team members
Team members are the people in your organization who use Arcane Compliance — auditors, application administrators, and other stakeholders. You control who can access which workspaces by assigning permission buckets when you invite or update a team member.Go to Team in the organization workspace
In the organization workspace, click Team in the sidebar to open the team management area. You’ll see a list of all current team members and their permission assignments.
Invite a new team member
Click the Invite button and enter the team member’s email address. They will receive an invitation to join your organization in the Arcane portal.
Assign permission buckets
For each application the team member needs to access, assign one or more permission buckets:
- Owner permissions — grant organization-level access (applications, team management, org reports)
- Common — grants activity log access for the application
- Administrator — grants disclosure request approval and case auditor management
- Auditor — grants the ability to submit requests, view transactions, and generate reports
Permission buckets
Application permissions are grouped into three buckets. Each bucket contains a specific set of permissions that you assign per application. A team member can hold any combination of buckets across any number of applications. Common| Permission | What it allows |
|---|---|
logs:view_activity | View the application activity log |
| Permission | What it allows |
|---|---|
cases:approve_creation | Review and approve or close disclosure requests |
cases:edit | Add and remove auditors on approved cases |
| Permission | What it allows |
|---|---|
cases:create | Submit new disclosure requests |
cases:withdraw_pending_request | Withdraw a pending request before it is reviewed |
reports:view_transactions | View transaction data in the case workspace |
reports:create | Generate compliance reports from a case workspace |
reports:list | List reports at the application level |
reports:download | Download application reports |
You can assign multiple buckets to the same team member on the same application. For example, a senior team member who needs to both submit requests and approve them should receive both the Auditor and Administrator buckets for that application.