# Configuring as a Webform

### Web Form Settings

FlexiForm templates support **Web Forms**, allowing documents to be signed directly through a shared link without requiring prior user creation.

Web Form configuration is available from the Settings panel on the right-hand side.

***

#### Enabling a Web Form

To enable a web form:

1. Open **Web Form Settings**.
2. Enable **Create a web form**.
3. Choose one of the following options:

   * **Public**
   * **Private**

   <figure><img src="https://1693119202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKpOPGIHdEkmaF2RQso%2Fuploads%2Fzn6GqgcSRP94sFBXWl3H%2Fimage.png?alt=media&#x26;token=92837f2f-ba37-4d2f-b36e-11e07c3f17e5" alt=""><figcaption></figcaption></figure>

***

#### Public Web Form

When **Public** is selected:

* A **public signing URL** is generated after template activation.
* The link can be shared with **any external user**.
* No prior user mapping is required for the **first signatory**.

**Important behavior:**

* The **first signatory must be left unassigned** during template setup.
* The external user accessing the link will act as **Signatory 1**.
* Once Signatory 1 completes signing, the workflow continues to the remaining signatories based on the configured signing order.

***

### Private Web Form

A **Private Web Form** allows controlled access to the signing experience with additional authentication and permission settings. This option is typically used when access must be restricted to known or authorized users.

***

#### Enabling a Private Web Form

To configure a private web form:

1. Expand **Web Form Settings**.
2. Enable **Create a web form**.
3. Select **Private**.

Once selected, additional security and access controls become available.

***

#### Authentication Settings

Private web forms support authentication to validate the signer’s identity before allowing access.

Available options include:

* **Username & Password**
  * Signers must authenticate using credentials before accessing the web form.
* **Office 365**
  * Enables authentication through Office 365 accounts (SSO-based access).

One or more authentication methods can be enabled based on organizational requirements.

***

#### Signatory Control

**Allow to Choose/Add Signatories**

* When enabled, the user accessing the private web form can:
  * Select an available signatory
  * Or add signatory details during the signing process (based on template rules)

This provides flexibility in scenarios where signer details are not fixed at template creation time.

***

#### Signing Flow Behavior

* Access to the web form is restricted based on the configured authentication method.
* Once authenticated, the signer proceeds according to the **workflow order** defined in the template.
* After a signatory completes their action, the workflow continues to the next signatory as configured.

***

#### Key Notes

* Private web forms are suitable for **secure or internal signing scenarios**.
* Authentication settings help ensure only authorized users can access the document.
* Signatory addition permissions must align with the template’s workflow design.
* Field configuration rules (such as mandatory placeholders for textboxes, checkboxes, and radio buttons) still apply.

***

> **Web Form Field Requirement**\
> Before activating a web form, ensure that all interactive fields (Textbox, Checkbox, and Radio Button) have their **Placeholder** values configured. Missing placeholders will prevent successful activation of a public web form.

***

#### Web Form Link Generation

After successful activation:

* A confirmation message is displayed.
* A **Web Form URL** is generated.
* The link can be:
  * Copied directly
  * Shared via email or other channels

<figure><img src="https://1693119202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKpOPGIHdEkmaF2RQso%2Fuploads%2FztcuYauH7ZpZumZfKja3%2Fimage.png?alt=media&#x26;token=18c06cb0-9c93-4de3-af0f-e6d74fa3b650" alt=""><figcaption></figcaption></figure>

***

#### Key Notes

* Web Forms are available **only for FlexiForm templates**.
* The signing flow follows the **same workflow order** defined in the template.
* Once activated, the web form link reflects the latest template configuration.