An application is an organization-scoped boundary for private transaction data, application access, audit cases, reports, and activity records. Each application has a stable workspace identifier and is associated with an existing privacy contract. Application routes and records are resolved within the current organization, preventing a user from addressing an application in another organization.
The current organization is taken from the authenticated session. It is not selected or supplied when an application is created.

​
What an application defines

Workspace identity

A unique workspace identifier, display name, description, and application type.

Contract association

The privacy contract that supplies transaction data for the application.

Application access

A primary contact and explicit permission assignments for organization members.

Audit boundary

Application-specific audit identity and public integration material when required by the selected privacy system.

​
Access required

Application management uses two organization-level permissions:
PermissionAllowed action
applications:readList applications and open application details for the current organization.
applications:createCreate, update, and revoke applications for the current organization.
The organization owner receives these permissions through the owner access policy. Other members can receive only the access explicitly assigned to them.

​
Before creating an application

Confirm that:
  • the associated privacy contract already exists in the current organization;
  • the workspace identifier is unique within the organization;
  • the application type matches the intended privacy integration;
  • any selected primary contact is already an organization member.
The supported application types are:
Application typeIntended association
stellar-poolA Stellar privacy pool contract.
solana-confidential-tokenA Solana confidential-token contract.

​
Create an application

1

Open Applications

Open the organization workspace and select Applications.
2

Start application creation

Select Add Application.
3

Define the workspace identity

Provide a unique workspace identifier, application name, and optional description. The workspace identifier is used as the application route segment and cannot be changed later.
4

Select the application type and contract

Choose the application type and associate the application with an existing contract from the current organization.
5

Assign a primary contact

Optionally select an existing organization member as the primary contact. The selected member receives application-administrator permissions for the new application.
6

Create the application

Confirm the application. The platform creates the organization-scoped record and adds an Application registered event to the activity history.
After creation:
  • the application creator receives application-administrator permissions when the creator has an organization member record;
  • the selected primary contact receives application-administrator permissions;
  • the application appears in the organization’s application list;
  • its detail view includes the members who currently have application access.
For a Stellar privacy pool associated with a Stellar contract, the platform creates an application-specific audit identity and public audit key. Private audit decoding material remains server-side and is never returned in the application response.

​
Review applications

The organization application list is paginated and includes the information needed to identify and route work:
  • workspace identifier and application name;
  • application type and contract association;
  • optional description and primary contact;
  • number of members with application access;
  • creation timestamp.
Open an application to review its full metadata and current access members.

​
Update an application

The current application management model allows the following fields to be updated:
  • application name;
  • description;
  • primary contact.
The workspace identifier, application type, and contract association are not changed through the application update operation. A new primary contact must belong to the same organization. Assigning a new primary contact grants that member application-administrator permissions. The primary contact can also be cleared.
Changing or clearing the primary contact does not automatically revoke access previously granted to another member. Review that member’s application assignment separately in User management.

​
Manage application access

Application access is stored per organization member and per application. Each assignment contains common, administrator, and auditor permission groups. Use User management to:
  • grant a member access to an application;
  • update the member’s permissions for that application;
  • remove one application assignment without affecting other assignments;
  • review every application currently available to the member.
An application appearing in the organization registry does not by itself make the integration ready for production. Confirm the associated contract, access assignments, integration configuration, and operational controls before use.

​
Revoke an application

Revoking an application performs a soft deletion within the current organization. The application is removed from active application queries, but the revoke action remains represented in the activity history.
The current management interface does not expose an application restore operation. Confirm the application identity and downstream dependencies before revoking it.

​
Next steps

User management

Assign organization and application access to team members.

Create a case

Request controlled access to evidence inside an application.