The audit log is your organization’s tamper-evident record of who did what, when, and to which object across every module of Beelocity. It captures every authoritative action — creating a sales order, approving a purchase requisition, inviting a member, adjusting inventory, signing in — and records the result as an immutable entry.
What the audit log captures
Each entry has five facts:
| Field | What it tells you |
|---|---|
| Date and time | The exact moment the action occurred. |
| Action | What happened — Record created, Record viewed, Record modified, Record deleted (in red), or an event of its own such as Signed in or Invitation accepted. |
| Object | The kind of thing that was acted upon — Sales order, Member, Stock movement, etc. — with the record itself beneath it. |
| Actor | The person who performed the action — their full name and email. System-generated entries (e.g. background workers) appear with an empty actor. |
| Details | What the entry adds to the two columns before it: the status the record moved from and to, such as Draft → Approved; the reason given for it, word for word as it was typed — why an invoice was voided, a work order held, a requisition rejected; and any other record the entry names — the order an approval request decided, the permission and the role of a grant. A dash when there is nothing more to say. |
Every record an entry names is shown by its number, code or name, and is a link to it wherever you may open that page — a document’s line takes you to the document. A record with no name of its own, such as a stock movement, reads as its kind and still links to it. If the record has since been deleted, the entry reads (record unavailable) in its place.
Everything in the log is written in your language, from what the entry recorded: the act, the kind of record, its statuses. The one exception is a reason someone typed, which reads exactly as they wrote it — a reason typed in French reads in French on an Arabic screen. It stays in the log even after the record forgets it: a work order that resumes clears why it was held, and a requisition reopened clears why it was rejected, but the entry for the hold or the rejection still says why. The organization you are working in is not repeated on every line — every entry you see belongs to it.
Entries are partitioned by organization. You only see entries written within the organization you are currently working in.
Where to find it
Open your user avatar menu → Settings, then click Audit Log under Access Control — or jump directly to /audit-logs. The most recent entries appear at the top.
Searching and filtering
The search bar matches the actor’s name and email, and the number, code or name of every record an entry names — every record except your organization itself, which every entry belongs to. Typing an order’s number finds the order’s creation, each of its lines, every change of its status and the approval that moved it — even though none of those entries repeats the number itself. So you can answer questions like:
- “What did Amina do today?” — search by her name.
- “What happened to order SO-2026-000123?” — search by its number.
- “Who touched the Setif warehouse?” — search by its code or its name.
It also finds an entry by the words of the reason given for it.
The search also reads the internal note each entry keeps of what happened. That note is in English and never shown on screen, so an English word such as line or created can bring back entries where no column shows that word.
Click a column header to sort by it, and use the filter button beside the search box to narrow by Action, Object (the list offers only the kinds of record that appear in your trail), Actor or a Timestamp window (Working with lists).
Permissions
Two permissions gate access:
| Permission | What it grants |
|---|---|
IAM_AUDIT_LOG_VIEW |
Read the audit log for the current organization. |
IAM_AUDIT_LOG_VIEW_ALL |
Read entries written by any member, used by audit and compliance roles. |
Grant these to the roles you want to give visibility — typically Administrators, Compliance, and Internal Audit.
What you cannot do
The audit log is intentionally append-only. There is no edit, no delete, no bulk-purge. This is the point — an audit trail you can rewrite is no audit trail.
If you need to retain history for compliance reasons, no action is required: entries persist indefinitely.
Tips for everyday use
- Diagnosing a mistake. When a teammate asks “what happened to that sales order?”, filter by the object type or by the actor and walk the timeline.
- Onboarding investigations. When a new member needs context on how a process unfolded, the audit log is often faster than asking around.
- Compliance reviews. Auditors usually want a date range and a focused activity — filter by the relevant action (Delete) and bound the dates in the filter panel.