Important
The article is accessible to you as part of our New Policy Engine, which replaces the Transaction Authorization Policy (TAP). We are currently still updating the relevant documentation in the Help Center to reflect the recent changes to our New Policy Engine.
- After you finish creating, editing, or restoring a Policy, select Publish policy. You must have at least one edited, added, or removed rule to submit changes.
- A limited summary of the submitted policy details appears.
- Select Publish policy for your specific policy type (e.g., Transfer) to send the Policy to the assigned approval group for approval.
Approving a new or edited Policy
After you submit a new or edited Policy, the assigned approval group receives Fireblocks mobile app notifications. You can open this notification to review a summary of the Policy details. Users in the group will also see the Pending approval indicator in the Console.
To approve the new or edited Policy:
- In the Fireblocks Console, go to Policies and select the new or edited Policy. The yellow Pending approval badge indicates there are changes to review.
- Select Review changes. Rules will appear the same as when you are viewing draft changes.
- Select Approve policy.
- Complete the approval process using your Fireblocks mobile app. The Policy becomes active immediately.
If you select Deny changes, you can enter a reason that will be logged in the Audit Log.
When Policy changes are denied, the submitter can resubmit Policy changes based on the feedback in the denial notification.
- When the submitter enters the Policy Editor, the submitter’s denied changes still appear in the Policy Editor so they can pick up where they left off.
- After submitting a new request, the yellow Pending approval badge appears.
- The submitter can’t draft more edits until the new request is approved or denied.