Purpose of operation logs
Operation logs help answer who performed an operation, when it was performed, where it came from, which object was affected, what action was executed, whether the before and after states changed, and whether the operation succeeded.
These records give institutions a clearer view of back-office management behavior.
Operations that can be recorded
Depending on the module, operation logs can record actions such as creating users, editing user profiles, deleting users, creating roles, changing permissions, changing data permissions, changing feature permissions, creating or deleting APIs, updating API settings, changing IP whitelist rules, changing security settings, changing system settings, creating notifications, editing notifications, listing or delisting products, changing trading parameters, changing market settings, changing product profiles, changing organization information, exporting data, and other back-office management operations.
The actual recorded content depends on the modules and features enabled by the institution.
Log information
A single operation log can include operation time, operator, User ID, Organization ID, action type, feature module, operation object, Object ID, result, source IP, device or browser information, notes, and request identifier.
For important operations, before and after values can also be recorded.
Before and after records
For configuration changes, logs can track data changes.
For example: Before = Maximum order quantity 100; After = Maximum order quantity 200; Operator = Admin A; Operation Time = 2026-08-28 15:32:10.
Recording before and after values helps institutions understand how system configuration changed.
Log query
Institutions can query operation logs by time range, operator, feature module, action type, operation object, IP address, result, and Organization ID.
For example, an administrator can query all operations performed by a specific administrator in the past 30 days, or check who recently modified a product parameter.
Security audit
When an abnormal situation occurs, operation logs can provide important evidence for investigation.
Examples include abnormal permission changes, API configuration changes, mistaken product delisting, user profile changes, security setting changes, IP whitelist changes, and data exports.
Administrators can use operation logs to trace the operator, time, and source of the related action.
Working with the permission system
Operation logs work together with the organization and permission system.
The permission system controls who can perform an operation. Operation logs record who actually performed that operation.
For example: an employee has Product Management permission -> modifies a product parameter -> the system records an operation log -> administrators can view that change in logs.
This improves traceability for internal management.
Difference from login logs
Operation logs mainly record management behavior after a user signs in, such as what was changed, created, deleted, configured, or executed in the back office.
Login logs mainly record login time, login account, login IP, login device, and login result.
Used together, the two log types can reconstruct a more complete activity trail for back-office users.
Log retention
Operation logs can be retained as part of internal audit and security management.
For financial institutions or other organizations with higher compliance requirements, the retention period should be set according to internal policy.
Retention should consider information-security policy, compliance requirements, audit requirements, data-retention policy, and applicable laws or regulations in the relevant region.
Example
For example, an administrator changes the price precision of a trading product.
The system can record: Operator = Admin A, Action Type = Update, Module = Product Settings, Object = AAPL, Changed Field = Price Precision, Before = 2, After = 4, Operation Time = 2026-08-28 18:20:32, Source IP = 203.0.113.10.
If a configuration issue appears later, the institution can quickly confirm the source of the change through operation logs.
Notes
Operation logs are mainly used to record back-office management behavior and improve Finger Manager traceability and internal-control capability.
Logs support audit, security investigation, and troubleshooting, but do not replace an institution's own compliance, audit, or data-retention policies.
Institutions should use and retain operation logs according to their business nature and regulatory requirements.
Operation logs provide an audit trail for important Finger Manager back-office actions.
By combining operation logs with login records, roles, permissions, and data-retention rules, institutions can trace changes, investigate issues, and confirm responsibility more efficiently.
