> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/using-peakcommerce/authentication-and-security/viewing-audit-logs.md).

# Viewing Audit Logs

The **audit log** is a tamper-evident record of who changed what across your tenant — configuration edits, user and permission changes, security events, and commerce actions. It's the first place to look when you need to answer "who did this, and when?" for a security review, a support escalation, or a compliance request. Every entry is scoped to your tenant, so you only ever see your own organization's activity.

Open the log from the **user menu** (your name, bottom-left) → **Settings → Audit Logs** (under **Observability**).

## What each entry records

| Field          | Description                                                         |
| -------------- | ------------------------------------------------------------------- |
| **Time**       | When the change was made                                            |
| **Actor**      | The user who made the change (system actions appear without a user) |
| **IP Address** | The IP address the change came from                                 |
| **Item**       | The record or field that changed (resource type and id)             |
| **Type**       | The kind of change (Created, Field Updated, Deleted, …)             |
| **Action**     | The before/after values (From → To) and any additional detail       |

## Working with the log

Entries are listed newest-first. Open any entry to see its full detail, including related events — other actions taken by the same actor from the same IP address around the same time, which helps you reconstruct a sequence rather than a single change. You can export the log (CSV or JSONL) for offline review or to hand to an auditor.

## Retention and categories

Entries are grouped into categories — authentication, security, admin, data access, data change, and system — and each category can keep records for a different length of time. A background sweeper purges entries once they pass their cutoff, so retention is enforced automatically rather than relying on manual cleanup. Control how long entries are kept under **Settings → Audit Log Retention** (default 90 days; configurable from 1 day up to 10 years per category). Security and admin events default to a longer 365-day window; short-lived access events default to 30 days.

## Related

* [Audit Log Retention](/product/settings/observability/audit-log-retention.md)
* [Audit Trail and Logs](/product/reporting-and-analytics/audit-trail-and-logs.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/using-peakcommerce/authentication-and-security/viewing-audit-logs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.