> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/sign/en/advanced-features/interactions-and-fields/add-fillable-fields.md).

# Add fillable fields

You can add checkboxes, dynamic text boxes or statements to be filled in by the signer before signing the document, either mandatory or optional.

This information will be added to the document after it is signed, and no data is sent to Salesforce fields.

## Add a statement

* From the assistant, go to the signer you want to add fillable fields to
* Go to the "Mention" block
* Customize the text as you like or keep the statement `Lu et approuvée le %date%` (Read and approved on %date%), which will display the date of signature
* Copy the tag and paste it into your document where you want it

{% hint style="danger" %}
**Warning**

Make sure the tag is not split across two lines
{% endhint %}

## Add a checkbox

* Go to the "Checkbox" block
* Give the checkbox a title
* Copy and paste the tag into the document where you want it

{% hint style="danger" %}
**Warning**

Make sure the tag is not split across two lines
{% endhint %}

{% hint style="warning" %}
**Tip**

Note that you can add a written statement in your document to help the signer understand
{% endhint %}

## Add a text field

* Go to the "Text Field" block
* Give the text field a title
* Then copy and paste the tag you created into your document template

{% hint style="danger" %}
**Warning**

Make sure the tag is not split across two lines
{% endhint %}

{% hint style="warning" %}
**Tip**

Note that the data entered in these fields will only be visible in the signed document. No data is updated in Salesforce records

If you need to collect data to update a Salesforce record, go to [the section on Interactions](/sign/en/advanced-features/interactions-and-fields.md)
{% 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://university.gonexa.fr/sign/en/advanced-features/interactions-and-fields/add-fillable-fields.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.