Skip to main content
Once you’ve created the root key quorum for an organization, create the organization’s wallet(s).
View the API reference to inspect the types for wallet creation directly.

​
Setting the wallet owner

When creating the organization’s wallet(s), you must set the owner of the wallet to the root key quorum of the organization. By assigning the root key quorum as the wallet’s owner:
  • Your app associates the wallet with the organization, by way of the root key quorum
  • Your app ensures that only the root key quorum has permissions to administrate over the organization’s wallet(s), such as configuring policies or access control

​
Configuring policies

In addition to configuring the wallet’s owner, you may also create policies for the organization and assign them to the wallet via the policy_ids field of the wallet creation request. This enables you to configure guardrails around the signatures and transactions that can be executed by an organization wallets. After a wallet is created, organizations may update the policy for their wallet, but it will require approval from the root key quorum for the organization (the wallet owner).

​
Configuring access control [optional]

To provision access to organization members beyond the root key quorum, your app may create additional key quorums to model other users within the organization. You might consider creating a key quorum for each distinct permission you’d like to assign (e.g. permission to send < 1000 USDC), and can add the users that should have that permission to the corresponding key quorum. Then, when creating a wallet, the organization may specify these lower-privilege key quorums as additional_signers, with scoped permissions defined by their override_policy_ids. These key quorums have the ability to authorize signatures and transactions within the scope of their policy, but not to manage the wallet’s configuration.