> **Source:** https://knowledge.leegality.com/document-execution/workflows/v4/custom-fields/overview
> **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

---
# Custom Fields

Custom fields let you capture additional information in a v4 workflow — an employee ID, a loan amount, a reference number — beyond the standard document and invitee details.

They do two jobs. The obvious one: **collect data** the standard fields don't cover. The powerful one: **drive logic** — custom fields are the values that [Rule Engine rules](https://knowledge.leegality.com/document-execution/workflows/v4/rule-engine/overview) watch. When a rule says *"IF Loan Amount > ₹10,00,000"*, Loan Amount is a custom field someone created.

## Anatomy of a custom field

Every custom field is defined once, centrally, with four things:

| Part | What it is |
| --- | --- |
| **API Name** | The field's unique technical identifier. Mandatory, must not repeat. Rules and integrations refer to the field by this name — choose it carefully, it's the stable handle. |
| **Display Name** | The label people see in the workflow. |
| **Field Description** | What the field is for — context for whoever fills it. |
| **Field Type** | **Text** (free input, with optional character limits and regex), **Dropdown** (pick from a list, single or multiple select), or **Toggle** (on/off). |

> **Info — Admin only**
>
> Only admin users can create custom fields. Anyone building workflows can then *use* the fields the admin has created.

## Where custom fields live in a workflow

Once created, every custom field appears in the **left panel** of the workflow editor, ready to be added. You choose the **level** at which it applies:

- **Pack level** — one value shared across the entire pack. Right for values like **Loan Amount**.
- **Document level** — added to each document separately, configured per document.
- **Invitee level** — a value per invitee, like **Employee ID** for each signer.
- **Group level** — attached to a group invitee as a whole. Picking the right level matters more than it looks: it decides who fills the value, where it shows, and what a rule reading it will see. [Add fields to a workflow](https://knowledge.leegality.com/document-execution/workflows/v4/custom-fields/add-fields-to-workflow) covers the four levels with examples.

## Fields are configurable per document

Any field in a document — custom or built-in — can be right-clicked to control three properties: **Visible**, **Editable**, and **Mandatory**, plus validations like character limits and regex. So the same field can be visible and editable on one document, locked on another. Details in [Field Properties](https://knowledge.leegality.com/document-execution/workflows/v4/setup-configuration/field-properties) and [Field Configuration](https://knowledge.leegality.com/document-execution/workflows/v4/setup-configuration/field-configuration).

These right-click settings are **static** — fixed when the workflow is designed. When you need them to change *dynamically* based on data ("mandatory only for big loans"), that's a [rule](https://knowledge.leegality.com/document-execution/workflows/v4/rule-engine/what-is-a-rule).

## Custom fields as rule inputs

This is the pairing that makes v4 workflows adaptive:

1. A custom field **captures** a value — Loan Amount, Customer Type, Source.
2. A rule **watches** that field as its Subject Field.
3. When the condition is met, the rule **changes** another field's visibility, editability, mandatory state, or value. Designing a workflow with rules in mind usually starts here: *what data do rules need to see?* — then create those custom fields first. The [Build your first rule](https://knowledge.leegality.com/document-execution/workflows/v4/rule-engine/build-your-first-rule) tutorial walks the full loop: create the field, add it, build the rule that watches it.

## Explore the section