> 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/users-and-user-roles/user-history.md). # User History When access goes wrong — a permission that shouldn't have been granted, a user who was deactivated unexpectedly — you need to know who changed what, and when. PeakCommerce records every change to users (and to the rest of your tenant) so you can answer those questions with evidence. ## Where to look * **Per-user activity** — open a user from the **user menu** (your name, bottom-left) → **Settings → Users**. The detail page's **Activity**, **Logins**, and **Impersonations** tabs show that user's recent events: profile and password changes, sign-ins, and any times they were impersonated or impersonated others. * **Tenant-wide audit log** — for the full record, open the **user menu** (your name, bottom-left) → **Settings → Audit Logs** (under Observability). Each entry shows the time, the actor, the item changed, the type of change, and the before/after values. Open an entry for its full detail. ## How long it's kept Retention is governed by **Settings → Audit Log Retention**. Older entries age out according to that policy, so export or review anything you need to keep beyond the retention window. ## Gotchas * Impersonation ("Log in as") sessions are attributed to the operator who started them, not silently logged as the customer — check the Impersonations tab to see who acted as whom. * For sign-in and SSO events specifically, see also [Authentication & Security](/product/using-peakcommerce/authentication-and-security.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/users-and-user-roles/user-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.