Skip to main content
An organization (or “org”) represents your company or project in Dfns. It is the top-level container that holds all your wallets, policies, users, and credentials. Your organization is completely isolated from other Dfns customers.

​
What’s inside your organization

Your organization contains:
  • Wallets and keys - All your wallets and their underlying cryptographic keys
  • Users - Your team members and end customers
  • Permissions - Access controls that define what each user can do
  • Policies - Rules that govern transactions and require approvals
  • Service accounts - Machine identities for API automation

​
Your organization ID

Your orgId is the unique identifier for your organization. You receive one organization when you sign up for Dfns. You can find your organization ID in your dashboard Account page.
Direct link: https://app.dfns.io/v3/account/account

​
Segregating your customers

If you’re building an application for your own customers, you have two options for segregation:

​
EndUser accounts with delegated wallets

For most use cases, create EndUser accounts for your customers within your organization. Each EndUser can only access wallets delegated to them - they cannot see other users’ wallets or your organization’s wallets. This isolation is enforced at the platform level, regardless of permissions. This approach is ideal when:
  • You want to give your customers ownership of their wallets
  • You need wallet-level isolation between customers
  • You want to manage all customers from a single dashboard
See Wallet delegation to get started.

​
Multiple organizations

If you need complete environment separation with independent users, policies, wallets, and configurations, you can set up multiple organizations. Each organization is fully isolated and would need to be configured separately. This approach is useful when:
  • You need completely separate configurations for different business lines
  • Regulatory requirements mandate full data separation
  • You want independent admin teams for each environment
Contact Dfns support to discuss multi-organization setups.

​
Organization isolation

Organizations in Dfns are fully isolated from each other:
  • Wallets, keys, and credentials cannot be shared across organizations
  • Policies in one organization do not affect another
  • Users can belong to multiple organizations, but must authenticate separately to each
Users are the only entity that can span multiple organizations. A single person can be a member of several organizations with different roles and permissions in each.