Skip to main content
At a high-level, there are two ways to provision access for an organization wallet to a new user.

​
Option 1: Add the new user to the default key quorum

In this approach, your app updates the organization’s default key quorum to include the new user. This effectively makes the new user an “administrator” of the organization’s wallets, and gives them the ability to approve or partially approve sensitive actions such as wallet configuration updates and policies. Generally, this approach grants “administrator privilege” to the new user. Updating the default key quorum requires a sufficient threshold of signatures from the existing default key quorum. View the reference for updating the key quorum.

​
Option 2: Add the new user as an additional_signer

In this approach, your app should:
  1. Create a new key quorum containing the new user. Alternatively, if your app has existing lower-privilege key quorums for other users, you may simply update those quorum(s) to include the new user.
  2. Create a policy defining the scope of signatures and transactions the user should be able to take.
  3. Add this key quorum as an additional_signer to the wallet with the policy from step 2.
This grants the new user the permission to transact from the wallet within the scope of the policy, but does not give them administration privileges such as wallet configuration updates.
View the full guide for configuring conditional policies for different users.