# Documint Sign

{% embed url="<https://youtu.be/uPyhMlDbzog>" %}

{% hint style="warning" %}
This feature is available only on the current **Silver plan and up** and can only be accessed from the new Template Designer.
{% endhint %}

{% stepper %}
{% step %}

### Configure Data Source

Signer information will need to be included with the data sent to Documint when creating a document. As such, we'll need to add a Collection Field (list of objects) that has at least 2 child properties, one that will contain the signer's email address and one that will contain the signer's name. &#x20;

{% tabs %}
{% tab title="Custom Data Source" %}
When creating the custom data source, the Signers field needs to be a "Collection" type with each object containing:

| Field         | Type   |             Required            |
| ------------- | ------ | :-----------------------------: |
| Name          | String | <i class="fa-check">:check:</i> |
| Email         | String | <i class="fa-check">:check:</i> |
| Signing Order | Number |                                 |

{% hint style="info" %}
If you already have a collection field that contains the signer information, you can skip.&#x20;
{% endhint %}

{% hint style="warning" %}
Signer's field cannot have the same email address more than once, and it cannot have the same email as the requester.
{% endhint %}

Open the Field Editor by clicking **"Custom Data Source"**&#x20;

<figure><img src="/files/7P7q1BP8LscKau64og9K" alt=""><figcaption></figcaption></figure>

Add the following fields. The names of the fields can be whatever you'd like, but the types must match the example below

<figure><img src="/files/QQzMUyClix8m0pazh2NM" alt=""><figcaption></figcaption></figure>

After adding the fields, click **"Save"**

{% hint style="danger" %}
**ALL SIGNERS MUST BE IN THE SAME FIELD**
{% endhint %}
{% endtab %}

{% tab title="Airtable" %}
In Airtable, we'll need at least 2 tables:&#x20;

1. The primary table that you're generating the document from.&#x20;
2. The secondary table that will contain the signers data. This table will be linked with the primary table via a Linked Record field.

#### Primary Table Configuration

{% hint style="info" %}
Table and Field names can be whatever you want them to be.
{% endhint %}

<table><thead><tr><th>Field</th><th>Field Type</th><th data-type="checkbox">Required</th><th>Notes</th></tr></thead><tbody><tr><td>Signers</td><td>Linked Record</td><td>true</td><td>Link this field to the Signer's Table</td></tr></tbody></table>

{% hint style="danger" %}
**ALL SIGNERS MUST BE IN THE SAME FIELD**
{% endhint %}

<figure><img src="/files/u3ooWsGmzxCA4EMq3wql" alt=""><figcaption></figcaption></figure>

#### Signer's Table Configuration

<table><thead><tr><th>Field Purpose</th><th>Field Type</th><th data-type="checkbox">Required</th></tr></thead><tbody><tr><td>Signer's Name</td><td>Single Line Text</td><td>true</td></tr><tr><td>Signer's Email</td><td>Email</td><td>true</td></tr><tr><td>Signing Order</td><td>Number</td><td>false</td></tr></tbody></table>

{% hint style="warning" %}
Signer's field cannot have the same email address more than once, and it cannot have the same email as the requester.
{% endhint %}

<figure><img src="/files/jSr4EZcYFO7CmZ5LHOjv" alt=""><figcaption></figcaption></figure>

Here is a sample base you can model your tables on:

<a href="https://airtable.com/appia050KmTldJ8dk/shrHRjcquDZn7UcJ9" class="button primary" data-icon="database">Example Airtable Base</a>

#### Connect to Documint

Follow these instructions to [connect the Base](https://docs.documint.me/~/changes/155/integrations/airtable) to your template.

{% hint style="warning" %}
Make sure the Signers field that you create will be expanded when you integrate with Airtable.
{% endhint %}

<figure><img src="/files/zG6vC4HoItxu5H7uJNRJ" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Configure Documint Sign Settings

Once our data source is set up, we can go ahead and dive into the settings themselves.<br>

Navigate to the **"Integrations"** tab

<figure><img src="/files/92jZuGGk2WRCRr7aatw2" alt=""><figcaption></figcaption></figure>

In the Integrations tab click the **Documint Sign** Destination

<figure><img src="/files/awrFtgmCZKmyKoAhCpK9" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/LYjSLXnP0hLeOVTjR7sW" alt=""><figcaption></figcaption></figure>

### Settings Fields

<table><thead><tr><th width="213">Setting</th><th>Description</th></tr></thead><tbody><tr><td>Expires after</td><td>Amount of time signers have to sign the document before it expires and they can no longer sign it.</td></tr><tr><td>Requires all signers</td><td>Check this option to require all signers to sign in order to complete this document. If false, then the document will can be finalized after being signed by one.</td></tr><tr><td>Enable auto reminders</td><td>Reminders will be sent a week after the document was created if it hasn't been signed yet.</td></tr></tbody></table>

Documint auto-detects the eligible fields for the signer field and the matching sub-fields that you can choose to populate.&#x20;

{% hint style="danger" %}
If the email address field doesn't contain a valid email, the document won't be sent for signing. ⚠️
{% endhint %}

<figure><img src="/files/itYpHIesEb0Tbf3GXuin" alt=""><figcaption></figcaption></figure>

Finally, you can add a custom message and title (the title is connected to the document name), in which you can use the variables from your template to populate dynamically if needed.

{% hint style="warning" %}
Make sure to **save** the settings! 💾
{% endhint %}

{% endstep %}

{% step %}

### Add E-sign Elements

Lastly, you need to position the signing fields in your document.

<figure><img src="/files/EngqrpSg2Ae79Pu1ymyz" alt=""><figcaption></figcaption></figure>

We have 4 types of fields:

* Sign Field - Inserts a Basic Sign component&#x20;
* Date Field - Inserts current date when signing
* Initials Field - Inserts initials based on name
* Text Field - The client can choose what to insert (we offer validations for guaranteed free input)![](/files/kB4ccMWIZbP2iPKbqylX)

For each signing field, we can also make sure some specific fields are required. If we've enabled signing order, we need to set up the signing order accordingly.

<figure><img src="/files/ztbH9kvoHi8JhkrC1LSS" alt=""><figcaption></figcaption></figure>

These settings will pop up whenever we drop a field in, or we can access them again by clicking the component and selecting the cogwheel icon. ⚙️

<figure><img src="/files/g2JWJkQNqbWj1GKsFMRq" alt=""><figcaption></figcaption></figure>

All that's left now is to merge the document while with the data depending on your integration, and the data will be compiled and sent!&#x20;
{% endstep %}
{% endstepper %}


---

# Agent Instructions: 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:

```
GET https://docs.documint.me/e-signatures/documint-sign.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.