> 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/user-guide/detail-view/actions/sign.md).

# Sign

## Overview

Labii's Sign and Signature feature is designed to streamline the process of digital record-keeping and ensure compliance with regulatory requirements. Here’s a quick overview of how it works:

1. **Digital Signing:** Users can digitally sign records to meet regulatory standards. This feature ensures that once a record is signed, it is locked from further editing, providing a secure and tamper-proof audit trail.
2. **Sequential Signing:** The signing process is managed in a specific order. After the first signer completes their signature, the second signer will receive a notification. This notification prompts them to review and sign the record.
3. **Rejection Option:** If the second signer finds any issues with the record or the first signature, they have the option to reject the signature. This ensures that all stakeholders have a chance to review and approve the record before it is finalized.

Overall, Labii's Sign and Signature feature enhances the integrity and accountability of record management by facilitating a secure and organized signing process.

You can also sign documents in the [Signers](/user-guide/detail-view/signers.md) view and [Signers](/widgets/section-widgets/regulation/signature/signers.md) widget.


---

# 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/user-guide/detail-view/actions/sign.md?ask=<question>&goal=<endgoal>
```

`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.