Audit trail

本頁尚未翻譯成中文，以下為英文原文。

An audit trail records important changes so Lim & Co can understand how a record reached its current state. It supports accountability without requiring the team to rely on memory.

Why it works this way

History can capture record creation and edits, deactivation, ownership transfers, lifecycle changes, and changes to permissions or settings. It records changes rather than every time a person reads a record.

Financial documents need an explainable sequence. An issued invoice remains in history; voiding or crediting it records the correction instead of erasing and replacing the original charge.

Other records can be deactivated when they should no longer be used. Keeping their history preserves the context for records that already refer to them.

Organisation-wide audit access requires System View permission. Level 1 covers organisation events, while level 2 limits a user to their own events; record-level History also depends on permission to view that record.

How it relates

The audit trail connects ownership, status and financial corrections over time. Lim & Co can use the organisation view to examine changes across easySales and record History to understand one item in context.

Terms

Audit trail: A chronological record of important changes.
History: The audit information shown for one record.
Changed by: The user associated with a recorded change.
Deactivate: Stop a record from active use without removing its history.
Lifecycle change: A meaningful status transition such as issuing or voiding.

Common misunderstandings

The audit trail is not a list of every record view.
Deactivation or voiding does not erase earlier history.
Access to a business record does not by itself grant organisation-wide audit access.

Where to find it

Financial corrections follow the approach in Fix mistakes without rewriting history. Who may see history follows Roles, permissions and sharing.