Basics of a Policy and Pending Approvals

Basics of a Policy and Pending Approvals

If a wallet has more than one admin, any new wallet policy or change proposed by one admin must be approved by another admin. 

Once a policy is created, a transaction that violates a policy must then be approved by an admin for that wallet in order to proceed. This is called a pending approval: 

1. When a pending approval is generated, all admins on that wallet are notified via email that there is a transaction waiting to be approved 

2. After an admin logs in and approves the transaction, it will be broadcasted to the blockchain 

3. If an admin denies the transaction, the transaction will be canceled 

See here for more information on the approval process.

If an individual wallet policy differs from policies applies across all wallets, the more restrictive policy takes precedence. 

Managing Your Pending Approvals

Pending Approvals Creation

Whenever a wallet policy is violated, a pending approval will be created for an admin to approve the transaction. There are additional circumstances when pending approvals will be created as well:

Auditing Policies

Activity Log

You can view the Activity Log by going to the Policies page and clicking on Activity Log on the left hand side of the navigation bar. 

 The Activity Log provides a full history of all actions performed on a policy. For example:

• Creation

• Changes

• Approvals for changes

• Archival

For each event, you can view:

• Who performed the action

• When the action took place

• Name of the policy

• Policy ID

• Associated pending approval ID

• IP address of the account that performed the action

The Activity Log also tracks activity across the following areas:

• Transactions

• Users 

• Wallet 

• Enterprise 

• Login

Searching by Evaluation ID

Every transaction has an associated evaluation ID. This ID corresponds to all of the policies that were evaluated when the transaction was initiated. A single withdrawal can trigger multiple policies, depending on how they’re configured. Searching by the evaluation ID in the Policies page shows you exactly which policies were involved, and therefore why you’re seeing the resulting actions in the timeline.

To locate a policy by ID, find the ID listed beneath the policy name and click the copy icon to its right. Then paste the ID into the Search bar to pull up the associated policy. 

Note: Some policies are internal to BitGo and are not surfaced to the user. These policies will not show up when searching by Evaluation ID.

Last Triggered

The Last Triggered column in the Policies table tells you the last time that the policy was evaluated and that the conditions of the policy is evaluated to be true. It is possible that multiple policies are triggered by a single withdrawal. This can give you some insight into how the policies are behaving:

• If the policy has never been triggered - has the policy been set up correctly?

• This policy always has a very recent Last Triggered date - is this policy overly sensitive?

Note: The Last Triggered timestamp resets when a policy has changed.