> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/signature.md).

# Signature

Store a handwritten signature on a record.

Use a **Signature** field when the record should store a handwritten signature.

For the general settings all data fields have in common, see [Shared field settings](/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/shared-field-settings.md).

Field-specific settings for **Signature** are:

#### On the form

**Display**

* **Display as**: controls how the signature field appears on the form
  * **Thumbnail**: shows the signature as a thumbnail
  * **Preview**: shows a larger preview in the form

On the form, click **Click here to open the signature editor** to draw a signature. You can click **Clear signature** to remove the current input, **Cancel** to close the editor without saving, or **Save signature** to store it in the record.

After you save a signature, use **`⋮`** to **View**, **Download**, **Replace**, or **Remove** the file.\
Click the saved signature or drawing to open the print editor, where you can print it or download it.

Ninox also stores the signature in **Files**, where users can access it later.\
Unlike a file in a **File** field, a removed signature does not remain in the **Files** tab of the record. Ninox moves it directly to **Trash** in the **Documents** area of the workspace. For more information about file storage, see [Documents](/user-hub/ninox-basics/documents.md).

{% hint style="info" %}
Use a **Signature** field when the record should store a signed confirmation or approval.

If you only need to attach a scanned signature image or document, use **File** instead.
{% endhint %}


---

# 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.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/signature.md?ask=<question>&goal=<user_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.