> 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/user-audit-history.md). # User Audit History Sometimes you need the history for one person rather than the whole tenant — for example to confirm who changed a user's email, role, or profile, or to investigate unexpected access. The audit log lets you narrow the full trail down to a single user. ## How to view a user's history Open the **user menu** (your name, bottom-left) → **Settings → Audit Logs** (under **Observability**) and filter to the user you're investigating. Each matching entry records the same details as any audit entry: * **Actor** — the user who made the change. * **Time** — when it happened. * **IP address** — captured at the start of the session. * **Item** — the record or field that changed. * **Before / after** — the previous and new values (From → To). You can review changes a user *made* as the actor, as well as changes made *to* that user's account by others. ## Reading the IP address The IP address is captured **at session start**. It isn't re-checked if the user later switches networks within the same session, so a single entry reflects where the session began — not necessarily where the user was at the exact moment of the change. Treat it as a session-origin signal, not a real-time location. ## Related * [Audit Logs Overview](/product/reporting-and-analytics/audit-trail-and-logs/audit-logs-overview.md) — entry fields and event categories. * [Viewing Audit Logs](/product/using-peakcommerce/authentication-and-security/viewing-audit-logs.md) — the audit-entry field reference. * [Audit Log Retention](/product/settings/observability/audit-log-retention.md) — how long a user's history is kept. > **Gotcha:** a user's entries are subject to the same retention windows as everyone else's — older history may have already been pruned. --- # 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/reporting-and-analytics/audit-trail-and-logs/user-audit-history.md?ask=&goal= ``` `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.