> 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.md). # Regulation Compliance-focused widgets for audit trails, electronic signatures, and regulated record controls inside Labii ELN and LIMS ## Overview The Regulation category provides section widgets that help laboratories maintain traceability, approval control, and audit-ready record management directly inside Labii ELN and LIMS. These widgets are designed for workflows where it matters not only what was documented, but also who changed it, who viewed it, and who formally approved it. Together, they support regulated and quality-sensitive environments such as GLP-style documentation, FDA 21 CFR Part 11-oriented electronic records, and internal compliance review processes. Whether you need audit trails, immutable version history, visitor logs, or controlled electronic signoff, this category keeps those controls attached to the same record as the scientific or operational work. ## Widgets * [Audit Trail](/widgets/section-widgets/regulation/audit-trail.md) - Review activities, versions, and visitor access history * [Signature](/widgets/section-widgets/regulation/signature.md) - Manage electronic signoff, witnessing, and approval workflows --- # 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.labii.com/widgets/section-widgets/regulation.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.