Skip to main content
This documentation assumes your business serves other businesses or organizations as your end customers. For clarity, we use the terminology:
  • organization to refer to the business/organization that is your end customer
  • user or member to refer to an individual within an organization
At a high-level, setting up wallets for an organization requires the following steps.
1

Create Privy users for members of the organization

For each user that will need to take action with an organization’s wallet(s), create a Privy user to represent that member. This user can then be assigned specific roles and permissions for the organization’s wallet(s).
2

Create a default key quorum and organization

Next, create a default key quorum of users in the organization representing a strict, highly-privileged group of users that will by default administer the organization’s wallets (including provisioning access, policy updates, and more). You can always modify this later on a per wallet basis.The default key quorum should be an extremely locked-down set of users. The default key quorum may provision lower-privilege access to other users as well.Then, create an organization to represent the business in the Privy API, setting its default_key_quorum_id to the default key quorum created above.
3

Create wallet(s) for the organization

Finally, create wallet(s) for the organization, setting each wallet’s entity to the organization.Privy assigns the organization’s default_key_quorum_id as the wallet’s owner. This ensures that the default key quorum is exclusively responsible for managing the wallet’s configuration and access.
These steps should be completed for each organization (each of your end customers). For an end-to-end implementation, follow the organization wallets recipe.