> 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 The Audit History function serves as a dedicated tool designed to monitor the activities of account users, specifically noting when they make updates to records. To access this feature, navigate through the Users section by selecting Users > All Users. Then, identify the user of interest and click on the Action Button adjacent to their name, followed by selecting Audit History. This tool meticulously logs the IP address of a user at the start of their session. However, it's important to note that it does not track any subsequent changes to the IP address that may occur within the same session, for instance, if a user switches to a Virtual Private Network (VPN) after the session has commenced. The Audit History primarily documents modifications made to the user's account details, including updates to the email address, ensuring a transparent and secure management of user information. --- # 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.