> For the complete documentation index, see [llms.txt](https://docs.labii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.labii.com/widgets/section-widgets/regulation/audit-trail.md). # Audit Trail ## Overview The Audit Trail category provides record-level compliance and traceability widgets for Labii ELN and LIMS. These widgets help teams review who changed a record, what historical versions exist, and who accessed the document over time, all without leaving the record context. Together, they support internal quality review, deviation investigation, approval workflows, and regulated documentation practices that depend on transparent audit evidence. Whether you need event-by-event changes, immutable version checkpoints, or a simple visitor log, this category keeps critical record history visible inside the working document. ## Widgets * [Activities](/widgets/section-widgets/regulation/audit-trail/activities.md) - Review chronological record changes with users and timestamps * [Versions](/widgets/section-widgets/regulation/audit-trail/versions.md) - Inspect saved record versions, hashes, and restore actions * [Visitors](/widgets/section-widgets/regulation/audit-trail/visitors.md) - Track who viewed a record and when --- # 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.labii.com/widgets/section-widgets/regulation/audit-trail.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.