> 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/getting-started/configure-sign/configure-signer-experience.md).
# Set up the signer experience
Access the standard Salesforce email templates via the App Launcher
{% tabs %}
{% tab title="Option 1: Gonexa Sign with the YouTrust interface" %}
## Create the email template
* Access the standard Salesforce email templates via the App Launcher
* Create a new email template and give it a name
* Select a public folder to store it in
* Define a subject and save
* The essential element to place in the template is the link to the signer interface. You must place this tag in your template: `{{{Recipient.gnx__Last_delivery_link__c}}}`
* If you want to start from a pre-designed template, copy the Gonexa HTML email template by clicking the button below ("Copy HTML" button on the original page)
* Then simply click "Source" at the top left of the editor and paste the HTML code you just copied.
* Click the "Source" button again to view the result
* Customize the template as you see fit with your logo and the necessary information
## Retrieve the user ID in L'App Gonexa
* Log in to your account on L'App Gonexa:
* Go to the "Profile & Users" section
* On your user's row, click the 3 dots, then "Copy Sign ID" to copy the user ID so you can paste it into the custom setting in the next step
## Create the "Gonexa Sign" custom settings
Please take the following **settings hierarchy** into account when making your configuration choices:
* In the Setup Quick Find, search for "Custom Settings"
* In the list, click Manage on the "Gonexa Sign" row
* Click "New" (first button) or "Edit", depending on your case
**Branding:**
Go to your L'App Gonexa account to set up your Branding. See [the article on creating a Branding](/sign/en/advanced-features/branding.md) \[Optional]
**Default email template:**
Salesforce ID of the email template used for signature requests
**App Sign ID:**
Paste the user's Sign ID previously retrieved from L'App Gonexa
**Phone field:**
API name of the phone field on the Contact \[MobilePhone if left empty]
**Two-factor authentication:**
4 possible choices: "SMS by default", "SMS", "Email" or "No MFA"
**Validity period:**
Number of days before the signature link expires
**OrgWideEmailAddress:**
Enter the sender email address \[Optional]
{% hint style="warning" %}
Make sure you have set up an organization-wide email address and confirmed it by email beforehand
{% endhint %}
**Follower email template:**
Salesforce ID of the email template used for followers \[Optional]
**Allow signer to refuse the signature:**
Check the box if you want to allow signers to refuse to sign \[Optional]
{% endtab %}
{% tab title="Option 2: Gonexa Sign with the Gonexa interface" %}
## Create the email template via the App
* Log in to your App account
* Go to the "Sign" tab, then to "Email template"
* Click "New email template"
* Select the desired template type from: Signature request, Follower, Reminder
* Give your email template a name; this name will allow you to identify it easily
* Select a branding if you want to customize the logo displayed in the email. If you have not configured any branding, refer to the article [**Create a Branding**](/sign/en/advanced-features/branding.md)
* Customize the predefined email subject and body
{% hint style="warning" %}
Do not delete the `{!button|Vérifier et signer}` tag. This button leads to the signature and must remain in the email template.
{% endhint %}
## Create the Sign configuration in the App
* Still in your App account, go to the "Sign" tab, then to "Configuration"
* Click "New Configuration" to be redirected to the configuration creation page
* Enter the following requested information:
**Configuration Name**
Used to identify the Sign configuration
**SALESFORCE SYNCHRONIZATION**
**Interface user**
The user designated to manage the connection and perform updates in Salesforce. They must be logged in to the Salesforce environments and have the Gonexa Sign Admin permission set in Salesforce.
**Branding \[Optional]**
Select an existing branding. It must have been created in the App beforehand. See the article on [creating a branding](/sign/en/advanced-features/branding.md).
**EMAIL TEMPLATES**
Select the associated template(s)
* **Signature request templates**: Initial email sent to the signer to access the document to sign
* **Reminder template**: Email used for automatic reminders
* **Follower template**: Email sent to followers to access the document and track its progress
* **Signed document templates**: Confirmation email sent to the user who initiated the process, once the document has been signed
**SENDING CONFIGURATION**
Some fields include default values. You can change them if they do not meet your business requirements, including:
* **Default language**: French
* **Validity period**: \[Number] in days
* **Two-factor authentication method**: SMS, SMS by default (SMS will be chosen if the contact has both a mobile number and an email address), Email, No MFA
* **Phone country code**: +33 by default
* **Salesforce organization-wide address**: You can enter an email address to be used as the sender address for signature requests. It must be configured and verified in Salesforce beforehand
* **Allow signature refusal:** Check this box to allow the signer to decline signing a document
* **Signer sequencing**: Check this box to enable signer sequencing, which lets you define whether a signing order must be followed
* **Enable initials**: Check this box to add initials when signing a document
* **Enable reminders:** Check this box to enable and configure automatic reminders and access their settings
**REMINDER SETTINGS**
Access the automatic reminder settings, if the Enable reminders box is checked:
* **Reminder frequency**: Once a day, once every two days, once a week
* **Number of reminders**: \[Number] between 1 and 10
* **Salesforce organization-wide address**: You can enter an email address to be used as the sender address for signature reminders. It must be configured and verified in Salesforce beforehand
* Check the "Default Sign Configuration" option\
This configuration will become the primary Sign Configuration and will be used for all Salesforce environments connected to the App.
* Click "Create configuration" to finish
{% endtab %}
{% endtabs %}
---
# 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/getting-started/configure-sign/configure-signer-experience.md?ask=&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.