---
title: "Audit Log"
description: "The audit log is your organization's tamper-evident record of who did what, when, and to which object across every module of Beelocity."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.beelocity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Audit Log

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**      | The verb — `create`, `read`, `update`, `delete`, plus domain-specific events like `sign_in`, `invitation_accepted`, or `password_reset`.        |
| **Object**      | The kind of thing that was acted upon — Sales order, Member, Stock movement, etc.                                                               |
| **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**     | A human-readable summary of what happened, e.g. "Created sales order SO-2026-0418" or "Approved level 2".                                       |

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 action name, object type, description text, actor name, and actor email. So you can answer questions like:

- "What did Amina do today?" — search by her name.
- "When was that price list updated?" — search by `price list` or `update`.
- "Who deleted the Setif warehouse?" — search by `warehouse` or `delete`.

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](../getting-started/working-with-lists.html#narrowing-the-list)).

## 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.

Source: https://docs.beelocity.com/en/access-control/audit-log/index.mdx