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

---
# Add fields to a workflow

Once created, every custom field appears in the **left panel** of the workflow editor, ready to be added. The one decision that matters is the **level** you add it at — it determines how many copies of the value exist, who fills them, and what a rule reading the field will see.

## The four levels

| Level | How to add | The value exists… | Right for |
| --- | --- | --- | --- |
| **Pack** | Click **Add to Pack** | Once, shared across the entire pack — available on every document | Values true for the whole send: **Loan Amount**, Customer Type, Branch Code |
| **Document** | Right-click the field → **Add to Document** | Once **per document**, configured separately on each | Values that differ by document: a per-document reference, a document-specific rate |
| **Invitee** | Select an invitee, add the field from the left panel | Once **per invitee** | Values that differ by person: **Employee ID** for each signer |
| **Group** | Add to a group invitee at the group level | Once for the **group as a whole** | Values shared by everyone in a group card |

**Pack and Document level fields are added in the Create stage:**

**Invitee and Group level fields are added in the Invite stage:**

## Choosing the level: think in copies

The practical test: **how many values of this thing exist in one run?**

- One value for the whole send → **Pack**. A loan has one Loan Amount, no matter how many documents describe it.
- One per document → **Document**. Adding at document level adds the field to *each* document **separately** — three documents means three independent values.
- One per person → **Invitee** (or **Group** for the group's shared value). Getting this wrong shows up later in confusing ways: a "Loan Amount" added at document level means the runner types the amount three times — and a rule reads only the copy on the document it points at.

> **Note — Level determines what a rule reads**
>
> When a rule watches a custom field, it reads the field *at a specific level* — the pack's value, one document's value, or one invitee's value. If the field will drive a [rule](https://knowledge.leegality.com/document-execution/workflows/v4/rule-engine/what-is-a-rule), decide the level with the rule in mind; the rule's logic must point at the same placement. Ready-made rule logic in the [how-to guides](https://knowledge.leegality.com/document-execution/workflows/v4/rule-engine/build-your-first-rule) states which level it expects.

## Where you can't add fields

> **Warning**
>
> Custom fields cannot be added in the **Template** or **Finalise** stages. Add them in the stages where their data belongs — pack and document fields alongside the documents, invitee fields on the invitee cards.

## Reorder fields

Every field has a **six-dot** handle. Click and drag it up or down to rearrange — this works throughout the workflow, for every field and element.

## Remove a field

Hover over the field and click the **delete** icon.

## Next steps

With the field in place, configure how it behaves per document — visible, editable, mandatory — via [Field Properties](https://knowledge.leegality.com/document-execution/workflows/v4/setup-configuration/field-properties), and control its input format with [Validations](https://knowledge.leegality.com/document-execution/workflows/v4/setup-configuration/field-configuration). If the field exists to drive logic, continue to [Build your first rule](https://knowledge.leegality.com/document-execution/workflows/v4/rule-engine/build-your-first-rule).