> 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/configure-interactions.md).

# Configure interactions

Once all the interaction tags have been added to your document, upload it to Salesforce.

The document will then be scanned to detect all the interaction tags. You will find the detected interactions in the "Interactions" component in the Sign tab of the document template.

There you will find the Salesforce field label, the interaction tag, the recipient and the field type.

You can customize each interaction using the arrow at the end of the row:

* **Name**: named after the field label in Salesforce by default, but can be customized. This is the information the signer will see when filling in the data
* **Help text**: add an instruction here to guide the signer in completing the data
* **Required**: check this box if the signer must fill in the expected information to sign the document
* **Is Autofilled**: check this box if you want to pre-fill the field of the generated document with the data found in Salesforce

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

This option is only available for non-certified signatures
{% endhint %}

* **Auto update**: check this box if you want the information entered by the signer at the time of signing to be automatically updated in the associated Salesforce record, without prior verification by the user
* **Width**: adjust the width of the field displayed in the document
* **Row amount**: adjust the number of lines displayed when the signer enters information
* **Max length**: adjust the maximum number of characters expected

![Customizing an interaction](https://content.gitbook.com/content/fJiC57rqLAtDo49GS6QB/blobs/xo6MWbpRyrt2M1KVf6hy/47-02-modif-interaction.gif)


---

# 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/configure-interactions.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.