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 customers
  • 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 root key quorum of organization members

Next, create a root 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 root key quorum should be an extremely locked-down set of users. The root key quorum may provision lower-privilege access to other users as well.
3

Create wallet(s) owned by the organization's root key quorum

Finally, create wallet(s) for the organization, setting the owner to the root key quorum for the organization. This ensures that the root 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).