Account Settings

Enterprise Policies 

Policies are security measures that protect wallets. Policies are applied at the organization level (for BitGo Enterprise accounts) or at the wallet level (for all BitGo accounts).  It is good practice to think through the policies carefully before defining them. Conflicting policies can lead to failed transactions and needless work for administrators.

Note:  Setting any policy starts a 48-hour timer.  Once the timer expires, all policies at that level are locked.  For example, once a policy is defined for a particular wallet, all policies for that wallet are locked after 48 hours. This is a security feature to protect digital assets in the event that an account is compromised.  The locked policy prevents an attacker from changing wallet policies (such as removing a daily velocity limit policy).

Creating a Policy

• Name – Custom recognizable name for the policy
• Scope – Should the policy cover all, some, or just one of your wallets?
• Touchpoint – What specific user operation are you trying to regulate?
• Condition – What conditions must be true in order to require the actions

Example Policies

For all transfers greater than $100k, require 2 admin approvals.

• Scope – All wallets
• Touchpoint – Withdrawal
• Conditions – Spending limit above $100k
• Action – Require 2 admin approvals

For all BTC transfers initiated by UserX, require approval from UserY or UserZ.

• Scope – All Custodial wallets
• Touchpoint – Withdrawal
• Conditions – Asset = BTC and initiated by Bryce
• Actions – Require approval from Daniel or Luis

Learn more about the creation of Enterprise Policies utilizing our API.

To request the unlock of an Enterprise or Wallet policy, please contact support@bitgo.com to start a Support ticket.  Policy Unlocks are only provided to contracted Institutional customers.

Note: BitGo recommends that all organizations have at least two or more owners and that all wallets have two or more administrators. In the event one administrator or owner is incapacitated, this provides redundancy for administration approvals for transactions, user management, and changes to policies.