> For the complete documentation index, see [llms.txt](https://docufi3d.gitbook.io/docufi3d/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docufi3d.gitbook.io/docufi3d/how-to/sign.md).

# Sign

The **Sign Page** in Docufi3d allows recipients to securely review and digitally sign documents. This step is crucial for completing legally binding agreements.

#### 🔗 Accessing the Sign Page

To sign a document, the signer receives a unique link (e.g.):

```
https://docufi3d.com/sign/{token}
```

Each link is one-time-use and tied to the signer's identity or email.

#### 🖋️ Signing Interface

Upon opening the page:

**🔹 Sign the Document Dropdown**

Select the desired action from the dropdown. The default is usually:

> **Sign the document**

**🔹 Signature Block**

A visual signature block appears, displaying:

* **Date** (e.g., `2025-06-09`)
* **Location** (e.g., `jaipur`)
* A **QR code** to verify signer identity or link to a verification record

**🔹 Location Input**

Below the signature box, users can optionally:

* Type or confirm their location (e.g., "jaipur")

#### ✅ Actions

Two primary buttons are available:

* **Sign** – Confirms your signature, finalizing your acceptance of the document.
* **Decline** – Refuses to sign. The sender will be notified, and the document remains unsigned


---

# 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://docufi3d.gitbook.io/docufi3d/how-to/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.