> 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/column-widgets/regulation/signature.md). # Signature ## Overview Labii’s signature widget streamlines the process of adding signatures to records, enhancing the efficiency of electronic approvals and documentation. This versatile widget allows users to input their signatures directly into Labii records, ensuring secure, authenticated, and legally binding endorsements. With customizable options such as typed, drawn, or uploaded signatures, the widget accommodates various user preferences while maintaining compliance with industry standards. Its integration into Labii’s platform simplifies workflows by embedding the signature process seamlessly into the record management system, eliminating the need for external tools and ensuring a cohesive, tamper-proof digital audit trail. ## Widgets * [Signature](/widgets/column-widgets/regulation/signature/signature.md) * [Open Signature](/widgets/column-widgets/regulation/signature/open-signature.md) * [Signature Status](/widgets/column-widgets/regulation/signature/signature-status.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.labii.com/widgets/column-widgets/regulation/signature.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.