> **Source:** https://knowledge.leegality.com/document-execution/leegality-features/invitee-level/esignature-appearance/company-seal
> **Site:** Leegality Knowledge Base — https://knowledge.leegality.com
> **About:** Leegality is a document execution platform covering eSigning, stamps, NeSL, workflows, and REST API integration.
> **Navigation:** Every article on this site has a plain-text version at `<article-url>.txt` (this format). To get an index of all articles with their `.txt` links, read: https://knowledge.leegality.com/llms.txt
> **AI Guide:** For instructions on how to navigate this knowledge base as an AI agent, read: https://knowledge.leegality.com/ai-readable.txt

---
# Company Seal from Invitee

An eSignature seal is a digital version of the traditional rubber stamp. It is used to authenticate signatures.

Enable the option **Require company seal from invitee** while sending the document to get an organizational signature. Leegality will create a digital impression of a rubber seal and apply it on the signature of the signer.

Configure your eSignature seal here. When a sender requests your signature with a seal, the one you have set up will be automatically pre-selected.

To set up the eSignature seal for your account:

1. Click on the **Settings ⚙️** icon in the top right corner.
2. From the left panel, go to **Settings > eSignature & Seal.**
3. In the Default eSignature Seal section, you can choose between three types of eSignature seals:
      - **Authorised Signatory:** Requires organization's name.
      - **Director:** Requires organization's name.
      - **Upload Physical Seal:** Upload an image of the physical seal. (Supported image formats are .jpg, .jpeg, and .png)

> **Info**
>
> The company seal feature is available in every signing method, including **Aadhaar eSign**. When using Aadhaar eSign with a company seal, the signature will display your company seal instead of the Aadhaar logo.

4. You can see the preview of the eSignature seal on the right.
5. Click **Update** to save your settings. 

## Requiring a Company Seal from Invitees

#### V3 Workflow

1. On the **Invitee Card**, click **Invitee Level Options** (labelled **More Options** in a workflow).
2. Enable **Require company seal from invitee** (labelled **Require Organisational Signature** in a workflow).
3. **Set organisation name:** The sender can either enter the organisation's name on behalf of the invitee or leave it blank for the invitee to provide during the signing journey.
  Within a reusable workflow, this becomes a three-way choice: leave it disabled so the invitee provides it, enable it without a name so the workflow runner must provide it while running the workflow, or enable it with a fixed name that neither the runner nor the invitee can modify.
4. **Choose a Seal Type:** Select one of the following options:
  - **Authorised Signatory Seal**
  - **Director Seal**
  - **Allow Upload of Custom Seal:** The invitee will be required to upload an image of their company seal during the signing journey.
5. Click **Save**.

**Note:** Within a reusable workflow, the workflow runner cannot disable this if enabled by the creator, and vice versa.

#### V4 Workflow

1. On the **Invite** stage, select the invitee card.
2. In the right panel, open the **Settings** tab and go to **Signature Appearance**.
3. Enable **Require Organisational Seal**.
4. **Set Org Name:** Enter the organisation's name, or leave it blank for the invitee to provide it during the signing journey.
5. **Choose a Seal Type:** Select one of the following options:
  - **Authorised Signatory Seal**
  - **Director Seal**
  - **Allow Upload of Custom Seal:** The invitee will be required to upload an image of their company seal during the signing journey.

**Note:** Whether the workflow runner can modify these settings depends on the [field properties](https://knowledge.leegality.com/document-execution/workflows/v4/setup-configuration/field-properties) set by the workflow creator.

## Example of Company Seal with Signature