> For the complete documentation index, see [llms.txt](https://support.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emsigner.com/initiate-and-sign-envelopes/using-templates/originating-a-template/flexi-form-template.md).

# Flexi Form Template

Flexi Form Templates allow users to initiate documents using pre-configured, dynamic templates created and managed by administrators. These templates provide flexibility in defining participants, form fields, and workflow behavior at the time of initiation.

> **Note:** Visibility of Flexi Form Templates depends on access granted by the administrator. If a required template is not visible, contact your administrator to request access.

***

### Accessing a Flexi Form Template

1. From the **Dashboard**, navigate to the **Templates** panel on the left.
2. Select the required **Flexi Form Template** from the available categories.
3. Clicking the template opens the **template initiation screen**, where document configuration and participant setup can be completed.

***

### Adding Participants

Participants define who will receive, review, and sign the document.

#### Add Participants from Existing Contacts

* Select participants from the existing contact list by seraching with first four letter of  their name.

#### Add New Participants

* Enter participant details manually (Name, Email, Mobile, etc.).
* Newly added participants become available for future initiations.

***

### Email Delivery Options

For each participant, you can choose how notifications are sent:

* **Primary Email**
* **Secondary Email**
* **Both Primary and Secondary Emails**

This allows flexibility in aligning with organizational communication preferences.

***

### Optional Configuration Settings

Before sending the document, additional configuration options are available:

#### Document & Workflow Settings

* **Envelope Name** – Assign a custom name to identify the document.
* **Reference Number** – Add a business or system reference (optional).
* **Workflow Settings** – Configure workflow-related options as permitted by the template.
* **Language Selection** – Choose the language for participant notifications and UI during signing.

#### Visual & Compliance Enhancements

* **Watermark** – Apply a watermark to the document if enabled.
* **Stamp Configuration** – Configure eStamp or physical stamp options where applicable.
* **Merge Additional Documents** – Attach supporting documents to be sent along with the main document.

***

### Bulk Initiation (Optional)

If the template supports bulk initiation:

* Upload participant details using an **Excel file**.
* Each row in the file represents a separate document instance.
* This is useful for initiating the same Flexi Form Template for multiple recipients in one action.

### Sending the Document

Once all participants and optional settings are configured:

1. Review the document and participant details.
2. Click **Send** to initiate the signing workflow.
3. The document is sent to participants based on the defined signing order and notification preferences.

After initiation, the document will appear in the appropriate Dashboard sections and docstore depending on workflow progress.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.emsigner.com/initiate-and-sign-envelopes/using-templates/originating-a-template/flexi-form-template.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.