DeepSafe
User Manual
Updates & Announcements
User Manual
Updates & Announcements
  1. Security
  • About DeepSafe
  • Quick Start
    • Core Concepts
    • Account Security Principles
    • Getting Started
  • Using DeepSafe
    • Accounts & Teams
      • Teams & Members
      • Decision Mode
      • Roles & Permissions
      • Account & Security Settings
    • Wallets & Transactions
      • Wallets & Assets
      • Key Shards
      • Sending Assets
      • Receiving Assets
      • Transaction Records
      • Gas Service
    • Security
      • Approval Workbench
      • Address Whitelist
      • Approval Nodes
      • Policy Engine
      • Audit Log
    • Developer
      • API Key Management
  1. Security

Approval Workbench

Overview#

The Approval Workbench brings together everything waiting for you to handle. Final confirmation for every approval happens in the app — including changes submitted in the Web Console.
image.png

Two kinds of approval#

Pending items are grouped by what they concern.
Transaction approvals cover individual transfers. Whether a transfer needs approval is determined by the Policy Engine; who approves it and how many approvals are required is set by the Approval Node. Once approved, members holding key shards complete MPC signing, and only then is the transaction broadcast.
Other approvals cover changes to Team configuration: members joining and permission changes, policy changes, Approval Node changes, whitelist changes, API Key changes, Decision Mode changes, and similar. These are governed by your Team's Decision Mode, and the participants are all Admins.
The two kinds are evaluated differently and involve different people. A given member may only ever see items in one of them.

Viewing items#

The Workbench separates items into Pending, Handled, Submitted by me, and All.
Approval details show the submitter, submission time, what is being changed, and the approval method, and present progress as a sequence — completed stages display who handled them and when, while pending stages list who is expected to act.
For transaction approvals, the details show the full transaction information and the policy that was matched. Check the token, network, source and destination addresses, and amount individually before confirming.

Approving and rejecting#

Items can be approved or rejected.
Independent verification before signing. For transaction approvals, each member participating in signing independently verifies that the content to be signed matches the transaction information shown at approval; if they do not match, signing stops. This is the second line of defense after approval.
Cross-client approval. Changes submitted in the Web Console — a policy change, for example — require the Web Console to generate a QR code that an Admin then scans in the app. The approval method shown in the details makes this explicit.

Things to note#

Approval is the decisive point for asset security: once approved, an item moves into signing. Do not confirm in bulk without reviewing the transaction details.
If you have doubts about a transaction or a change, reject it and check with the submitter rather than leaving it unhandled — a pending item occupies the approval flow for as long as it sits there.
Modified at 2026-08-26 02:51:05
Previous
Gas Service
Next
Address Whitelist
Built with