> **Source:** https://knowledge.leegality.com/document-execution/workflows/v4/setup-configuration/custom-page
> **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 Page

> Design a single page that collects the key details for a pack, link those details to fields across the workflow, and let the workflow runner send documents from one screen.

<!-- TODO: POC notes say the feature is on by default for Scale Plus and Enterprise plans. Confirm how this maps to the [Premium, Enterprise] tags used across the docs. -->

# Custom Page

Most packs depend on a handful of details, such as the loan amount, the borrower's name, the state, or the branch code. Without a Custom Page, the workflow runner finds and fills these details across the **Create**, **Invite**, and **Finalise** stages.

A **Custom Page** brings them onto one screen. You design the page yourself, and it appears as the **first stage** of the workflow. Link its fields to the rest of the workflow with rules, and a value the runner enters once fills in everywhere it is needed. You can also hide the other stages, so the runner fills in the Custom Page and clicks **Send**.

> **Tip — Prerequisites**
>
> - **Custom page** must be enabled in [Workflow Builder Config](https://knowledge.leegality.com/document-execution/settings/Department/workflow-builder-config).
> - The fields you want on the page must already exist as custom fields. See [Create a custom field](https://knowledge.leegality.com/document-execution/workflows/v4/custom-fields/create-a-custom-field).

> **Info — Note**
>
> Only admins have permission to create and edit workflows.

## Step 1: Add a Custom Page

To add a Custom Page to a workflow:

1. Go to the **Workflows** section using the left panel, and open the **V4 Workflows** tab.
2. Open the workflow you want to add the page to, or click **+ New Workflow** to create one. The workflow editor opens at the **Create** stage.
3. In the **left panel** of the workflow editor, click the **Visualisation** icon. If you don't see the left panel, switch to the **Advanced** tab in the top-right corner.

    The Visualisation panel lists the stages of the workflow: **Create**, **Invite**, **Template** (if the workflow has one), and **Finalise**.
4. Click **+ Custom Page**.

    A **Custom Page** stage is added before **Create** in the stepper at the top of the screen, and a blank page opens with the message *Start building your page*.

> **Info — Note**
>
> The **+ Custom Page** button appears only when **Custom page** is enabled in Workflow Builder Config. A workflow can have only **one** Custom Page, so the button disappears once you add it.

## Step 2: Add Static Elements

Static elements don't collect any information. They give the page structure and tell the runner what to do. The toolbar at the top of the page offers six:

| Element | Use it for |
| --- | --- |
| **Heading** | Page and section titles, in four sizes (H1 to H4). For example, *Loan Form* or *Borrower Details*. |
| **Paragraph** | Longer instructions or background for the runner. |
| **Helper Text** | A short hint next to a field, such as *Enter borrower name and email*. |
| **Divider** | A horizontal line that separates one section from the next. |
| **Link** | A clickable link, for example to a policy or reference document. |
| **Accordion** | A collapsible section. |

<!-- TODO: confirm what an Accordion can hold (text only, or fields too) and what a Link needs (display text + URL?). -->

To add a static element, click it in the toolbar. For a heading, choose the size you want. The element is added to the page with placeholder text, which you can replace with your own (see [Step 4: Arrange the Page](#step-4-arrange-the-page)).

## Step 3: Add Custom Fields

Custom fields are the parts of the page the runner fills in. Only **pack-level** custom fields can be placed on a Custom Page: each holds one value for the whole pack.

To add a custom field to the page:

1. Open the **Custom Field** tab in the left panel. It lists the fields you have already created. If the page is still empty, you can also click **Open Custom Fields** in the centre of the page.
2. Find the field you want. To narrow the list, type its name in the **Search** box.
3. Click the **+** icon next to the field. A pop-up titled **Choose Placement** appears.
4. Click **Custom Page**.

    The field is added to the page.

Repeat these steps for each field you want on the page.

> **Info — Set field properties and validations**
>
> Right-click a field on the page to control it individually, the same way as in the other stages:
> 
>     - **[Field Properties](https://knowledge.leegality.com/document-execution/workflows/v4/setup-configuration/field-properties):** Set the field's **Visibility**, **Editability**, and **Mandatory** state.
>     - **[Validations](https://knowledge.leegality.com/document-execution/workflows/v4/setup-configuration/field-configuration):** Add character limits and a regex pattern to control what can be entered.

## Step 4: Arrange the Page

Fields and static elements appear in the order you add them. To change the layout:

- **Reorder:** Click the **six-dot** handle to the left of any field or element, then drag it up or down.
- **Edit text:** Double-click the text of a heading, paragraph, helper text, or link, and type the new text.
- **Delete a static element:** Hover over the element and click the **delete** icon in its top-right corner.
- **Remove a custom field:** Right-click the field and click the **delete** icon in the pop-up.

## Step 5: Link Fields with Rules

A Custom Page is most useful when its fields feed the rest of the workflow. Using the [Rule Engine](https://knowledge.leegality.com/document-execution/workflows/v4/rule-engine/overview), you can link a field on the Custom Page to fields on the **Create**, **Invite**, or **Template** stages. When the runner enters a value on the Custom Page, the rules carry it to every linked field.

For example, a runner enters a **Consideration Price** once on the Custom Page, and rules use it to fill:

- the consideration amount in the template,
- the stamp value, worked out from the price and the state's stamp duty percentage,
- the payment amount.

This works for template fields, payment amounts, stamp values, and document-level or invitee-level custom fields. To see how a rule like this is built, see [Calculate a field value](https://knowledge.leegality.com/document-execution/workflows/v4/rule-engine/how-to/calculate-a-field-value).

<!-- TODO: confirm whether linking requires the Rule Engine toggle in Workflow Builder Config, and whether customers build these rules themselves or Leegality sets them up. -->

## Step 6: Preview the Page

1. Click **Preview** in the top-right corner of the page. The page appears exactly as the runner will see it.
2. Close the preview and make any changes you need.
3. Click **Proceed**.

> **Warning — An empty Custom Page blocks publishing**
>
> A workflow can't be published while its Custom Page is empty. Add at least one field or element, or delete the Custom Page (see [Rename or delete a Custom Page](#rename-or-delete-a-custom-page)).

## Send Documents in One Step

If the Custom Page collects everything the pack needs, you can hide the other stages. The runner then sees only the Custom Page: they fill it in and click **Send**.

To set up one-step sending:

1. In the **left panel** of the workflow editor, click the **Visualisation** icon.
2. On each of the **Create**, **Invite**, **Template**, and **Finalise** cards, click the **View/Hide** (eye) icon. The icon changes to show the stage is hidden.
3. Click **Save**.

> **Caution — Check hidden stages before you publish**
>
> The runner can't fill in anything on a hidden stage. Every **mandatory** field on a hidden stage must get its value another way: from a default value set in the workflow, or from a rule linked to the Custom Page.
> 
>     **Leegality does not check this for you.** Run the workflow end to end before you share it with runners.

<!-- TODO: confirm what the runner sees if a mandatory field on a hidden stage is left empty (error on Send? blocked?). -->

For more on hiding and renaming stages, see [Visualisation](https://knowledge.leegality.com/document-execution/workflows/v4/setup-configuration/visualisation).

## Rename or Delete a Custom Page

Once added, the Custom Page appears as a card at the top of the **Visualisation** panel, with its own controls:

- **Rename:** Click the **Edit** (pencil) icon, enter the new name, and click **Save**. This is the name the runner sees in the stepper, so choose something that describes the page, such as *Loan Details*.
- **Delete:** Click the **Delete** (bin) icon. This removes the Custom Page and everything on it from the workflow.

<!-- TODO: confirm what happens to rules that reference fields on a deleted Custom Page. -->

## Frequently Asked Questions

**Does a Custom Page change what signers see?**

> No. The Custom Page is only part of the **sending** journey, which the workflow runner goes through. Invitees go through the signing journey as usual.

**Can the details entered on a Custom Page be changed after the pack is sent?**

> Yes. Values entered on the Custom Page are saved as pack-level custom fields on the pack. You can change them later through **Pack Edit**, and any rules linked to those fields run again with the new value.
> 
> <!-- TODO: confirm where Pack Edit is in the UI and whether it should link to a page. No Pack Edit doc exists yet. -->

**Why can't I add a document-level or invitee-level custom field to the Custom Page?**

> A Custom Page holds one value per field for the whole pack, so only **pack-level** custom fields can be placed on it. To fill a document-level or invitee-level field from the Custom Page, add a pack-level field to the page and [link it with a rule](#step-5-link-fields-with-rules).

**Can a workflow have more than one Custom Page?**

> No. Each workflow can have only one Custom Page.

## Next Steps

- [Visualisation](https://knowledge.leegality.com/document-execution/workflows/v4/setup-configuration/visualisation): hide or rename the other stages of the workflow.
- [Rule Engine](https://knowledge.leegality.com/document-execution/workflows/v4/rule-engine/overview): build the rules that carry Custom Page values across the workflow.
- [Run a pack](https://knowledge.leegality.com/document-execution/workflows/v4/run-a-pack): see the sending journey from the runner's side.