Audit & Logs Overview
The Audit & Logs module is your organization's complete, tamper-evident record of who did what, when, and from where. Every meaningful change across the system — a new sales order, a partnership holding adjustment, a unit status change, a failed login — is captured as an audit event and kept in a single, searchable trail.
This page explains what the audit trail is, why it matters, what gets recorded, and how the Audit & Logs page is laid out so you can find an event quickly.
Why the audit trail matters
The audit trail exists to give you accountability and compliance without relying on memory or chasing people for explanations:
- Accountability — every create, update, delete, and approval is tied to the user who performed it (or to System for automated actions), so there is always a clear answer to "who changed this?"
- Compliance & governance — ownership changes, financial activity, and data exports are recorded with timestamps, making it straightforward to satisfy internal reviews and external audits.
- Investigation — when something looks wrong on a record, you can trace its full history: what the value was before, what it became, who made the change, and the reason they gave.
- Security monitoring — login failures, account lockouts, and blocked actions are all logged so suspicious activity stands out.
:::note Read-only by design Audit events are a permanent record. You can view, filter, and export them, but you cannot edit or delete an event. This is what makes the trail trustworthy. :::
Who can see it
The Audit & Logs page is permission-controlled. Users without audit-view access are redirected away and see an Access Denied message. Exporting is governed by a separate permission, so some users can read the trail but not download it. See Organization Roles for how these permissions are assigned.
What gets logged
The trail spans the whole application. The most common events you will see are:
| Category | Examples |
|---|---|
| Record changes | Create, Update, and Delete on parties, partners, units, stock, sales orders, documents, and more. |
| Status changes | A unit moving from Available to Booked, a stock status advancing, a sales order being completed. |
| Ownership changes | Holdings updates on partnerships, projects, and units. |
| Approvals | Approve and Reject decisions in workflows. |
| Authentication & security | Login, Logout, Login Failure, Account Lockout, Password Reset, Sign Up, and Invite. |
| Structural operations | Unit Split, Unit Merge, Unit Switch, and SVG (layout) remaps. |
| Data access | Exports and document downloads — including exports of the audit log itself. |
| Blocked attempts | Actions the system refused (for example a delete that was guard-blocked) are recorded as a Failure so the attempt is never invisible. |
Each event also captures supporting context: the actor and their role, the module and entity affected, the outcome (Success or Failure), a plain-language summary, an optional reason/comment, the IP address, and — for updates — a field-by-field record of exactly what changed.
:::tip Timestamps follow your organization's timezone All times on the page are shown in your organization's configured timezone (for example Asia/Kolkata), so the trail reads consistently for everyone. :::
How the page is laid out
When you open Audit & Logs, you see three things from top to bottom:
- The header — the page title plus the Presets, Recent Exports, and Export actions (the export actions appear only if you have export permission).
- The filter bar — search, dropdown filters, and a date range with quick presets, with active filters shown as removable chips beneath.
- The events table — columns for Time, Actor, Role, Module, Entity / ID, Action, Outcome, Reason, and IP. The newest events appear first, and you can sort by any column and page through the results.
The basic workflow
Using the audit log follows a simple drill-down pattern: narrow the list with filters, then open an event to read its full story.
From here, continue to:
- Using the Audit Log — the full guide to filtering, saving filter presets, reading the detail drawer, and interpreting the diff view.
- Exporting Logs — how to export the trail to CSV or Excel and re-download past exports.
Related reading
- Glossary — definitions of the entities and terms that appear in audit events.
- Notification Catalog — many of the same events also trigger notifications.