Organizations

Edit online

An organization is the top-level container for all resources in IBM Digital Asset Haven. It represents your company or project and holds your wallets, users, policies, and credentials. Each organization is fully isolated from all other IBM Digital Asset Haven customers.

What an Organization Contains

An organization includes the following resource types:
  • Wallets and keys: All wallets created in your organization and their underlying cryptographic keys.
  • Users: Team members and end customers who access your application.
  • Permissions: Access controls that define what actions each user is allowed to perform.
  • Policies: Rules that govern transaction approvals or workflow conditions.
  • Service accounts: Machine identities used for API-driven automation.

Organization ID

Your orgId is the unique identifier for your organization . You receive one organization when you sign up for IBM Digital Asset Haven. You can find your organization ID on the Account page of the dashboard.orgId

Segregating Your Customers

If you are building an application for end customers, you can choose how to isolate their data and resources. IBM Digital Asset Haven supports two approaches.

EndUser Accounts With Delegated Wallets
For most applications, create EndUser accounts for your customers inside your organization. Each EndUser can access only the wallets delegated to them. They cannot see other users' wallets or your organization's internal wallets. This isolation is enforced at the platform level regardless of permissions.This option is best when:
  • You want your customers to have direct ownership of their wallets.
  • You need wallet-level isolation between customers.
  • You want to manage all customers from a single dashboard.
Multiple Organizations
If you require complete separation of environments, you can create multiple organizations. Each organization has its own users, policies, wallets, keys, and configurations. Organizations do not share resources.This option is appropriate when:
  • You need different business units or environments to be fully isolated.
  • Regulatory requirements require complete data separation.
  • You want independent administrator teams for each environment.
Users belong to a single organization. However, the same email address can be used to create separate user accounts in different organizations.
Note: Contact IBM Digital Asset Haven support for multi-organization setup assistance.