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

Audit Log

Overview#

The Audit Log records operations within your Team: who did what, when, from which device, and to which object. It exists for after-the-fact investigation and compliance evidence. Records are generated automatically by the system and cannot be edited or deleted.
The Audit Log is available in the Web Console only.
image.png

What is recorded#

The log covers both Team governance and asset operations. Records are grouped by the object acted on — commonly users, transactions, whitelists, Approval Nodes, policies, and approval items.
A single event can produce several records. An Approval Node change, for example, records the submission first, then each decision-maker's approval.

Viewing and filtering#

Records are listed newest first. Each row shows the time, the object, the action, and who performed it.
You can filter by date range, object, action, and user, and search by transaction identifier or address.

What a record contains#

Expanding a record reveals two groups of data.
General data records the environment the action came from: IP address, region, device model, operating system, and app version.
Secondary data records the object and the type of action: the audit record identifier, the action type identifier, and the identifier of the object acted on.
Together these form a complete trace — confirming both the circumstances of an action and exactly which object was changed.

Recommended practice#

Review the Audit Log regularly, paying particular attention to three kinds of record: sign-ins outside working hours, actions from unfamiliar devices or unexpected regions, and changes to permissions or policies.
If you find evidence of unauthorized activity, check your Team's members and permission settings in the app immediately and contact DeepSafe through an official channel.
Modified at 2026-08-26 02:51:05
Previous
Policy Engine
Next
API Key Management
Built with