Policies FAQs

Policies FAQs

1. Who can create policies for all wallets or wallets by type?

   1. Enterprise admins can create policies of all wallets and wallets by type, but require approval from 1 other enterprise admin.

   2. View the Roles and Permissions Matrix for more information

2. Where do I set how many approvals are required for new policies and policy changes?

   1. Currently, in the wallet settings

3. What happens if I try to update a policy but I have fewer admins than the required # of approvals?

   1. Automatically rejected. This is what happens today as well.

   2. Additionally, there’s logic in the wallet settings for required # of approvals, so you can ensure the number you set is n - 1. To reach this edge case you must remove wallet admins from the wallet below that original threshold.

4. What happens if there’s only 1 admin on the wallet?

   1. This admin is able to build any policies they want on the wallet and there will be no approvals required.

5. What changes to a policy require approval?

   1. Any changes to a policy requires approval. E.g.,

      1. Name change

      2. Scope change

      3. Touchpoint change

      4. Condition change

      5. Action change

6. Are V1 wallets supported in the new Policy Engine?

   1. No, you continue to manage policies in the V1 wallet policies page

   2. Not even All Wallets policies cover V1 wallets

7. What about in-progress policy changes?

   1. BitGo only allows 1 in-progress change at a time

   2. Example:

      1. userA requests to unlock policyX

      2. policyX is now unlocked for 48 hours

      3. userA changes the spending limit of policyX from $50k to $100k

      4. userA submits and this goes to approval

      5. now while policyX is unlocked userB thinks they can also make a change, so they open the policy but are shown a message along the lines - “this policy has already been edited” and cannot make changes until the existing pending approval is approved/rejected

      6. If the change userA made is rejected and there is still remaining time before it gets locked, userB can now open policyX and submit changes, which then go to pending approval again

8. Can I build many policies that cover the same wallet?

   1. Yes, you can create any number of policies that cover a given wallet

9. What happens when a single transaction triggers multiple policies?

   1. The actions associated with each policy all apply

   2. BitGo aggregates and deduplicates. For example:

      1. Policy1 Actions: Get 2 approvals from userA, userB, userC, userD

      2. Policy2 Actions: Get 1 approval from userC, userE, userF

   3. Both policies need to be fully satisfied in order to let the transaction through.

   4. Scenarios:

      1. ☑️userA, userB, and userE approve

      2. ☑️userA, userC approve (userC satisfies ½ of Policy1 and all of Policy2)

      3. ✖️userC, userE, userF approve (did not satisfy Policy1)

10. What is  the order of actions?

    1. Currently, the only action that takes place after the other actions is the final approval

    2. Otherwise, all actions are handled at the same time - users are notified at the same time, any action can be resolved at the same time, etc.

11. What happens to my whitelist?

    1. Whitelists continue to exist in each wallet and at the enterprise level. However, you can customize the behavior of what happens when withdrawing to non-whitelisted addresses. For example:

       1. Scope: All Wallets

       2. Touchpoint: withdrawal

       3. Condition: destination - non-whitelisted address

       4. Action: Deny (or require approval.)

12.  What happens if the pending approval for a policy change is not approved before the unlock period ends?

    1. The pending approval will continue to exist and approvers can still approve or reject the policy change. If approved, the policy update takes effect.

    2. This is different from today where a user must unlock the policy again just to approve the changes.

13. Is the API for the new Policy Engine available to me? 

    1. Yes