> 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/reporting-and-analytics/audit-trail-and-logs/audit-logs-overview.md). # Audit Logs Overview When multiple administrators, CSRs, or partners manage one tenant, configurations can change without everyone's knowledge. The **audit log** records those changes — giving a transparent, accountable history you can review for troubleshooting, security reviews, and compliance. Open it from the **user menu** (your name, bottom-left) → **Settings → Audit Logs** (under **Observability**). ## Reading an entry Each entry captures: * **Time** — when the change was made. * **Actor** — the user who made it. * **IP address** — where the change came from. * **Item** — the record or field that changed. * **Type** — the kind of change (for example *Created* or *Field Updated*). * **Before / after** — the previous and new values (From → To). ## How events are categorized Behind the scenes, every event is bucketed into a category so it can be reviewed and retained sensibly: * **Authentication** — sign-ins, sign-outs, and impersonation events. * **Security** — permission, policy, and API key changes. * **Admin & Configuration** — tenant settings, users, profiles, and integration changes. * **Data Access** — reads, downloads, exports, and views. * **Data Changes** — creates, updates, deletes, and other business activity. * **System** — background jobs and platform-emitted events. These categories drive retention: each can keep entries for a different length of time. ## Retention Entries don't accumulate forever. Control how long they're kept under **Settings → Audit Log Retention** — see [Audit Log Retention](/product/settings/observability/audit-log-retention.md). For a field-by-field reference of an entry, see [Viewing Audit Logs](/product/using-peakcommerce/authentication-and-security/viewing-audit-logs.md). > **Gotcha:** older entries are pruned automatically once they pass their category's retention window, so export anything you need to keep for long-term records before it ages out. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.peakcommerce.com/product/reporting-and-analytics/audit-trail-and-logs/audit-logs-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.