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

---
# Workflow Overview

Workflows allow you to create, save, and reuse the document sending journey configurations, eliminating repetitive setup. They store all invitee-level and document-level options, ensuring a consistent sending journey each time.

**Invitee Level Options**

- eSign type
- Security settings
  - 1 or 2 Factor Authentication
  - GPS Capture (Geo-fencing)
  - Photo Capture (Face verification and Liveliness detection)
- Custom consent
- Signing retry attempts

**Document Level Options**

- Number of signers
- Signing order
- Signature positioning
- Stamp paper requirements

Workflow setup only needs to be done once and can be used over and over again. This removes the need for repetitive tasks of preparing documents from scratch each time.

Workflows are ideal for frequently executed and complex document journeys, accelerating the process significantly.

> **Info — Example - Loan Agreement**
>
> Your bank provides loans to multiple customers, requiring a loan agreement signed by both parties with all terms and conditions. 
> 
>     To streamline this process, you can create a workflow and upload your loan agreement PDF or select the loan agreement template with variable fields like Beneficiary Name, Loan Amount, Tenure, and Guarantor.
>     
>     One-Time Workflow Configuration as per requirement
> 
>     - Add stamp papers as needed
>     - Add invitee roles such as "Beneficiary" and "Lender" as signers.
>     - Set a signing order, for example, the beneficiary signs first, followed by the lender.
>     - Specify the eSign type for each signer.
>     - Add other invitees as reviewers if needed.
>     - Configure any invitee-level and signing journey options during workflow creation.
>     - Set eSign coordinates where the signature would be placed.
> 
>     Whenever you need to send a loan agreement document, you don’t need to repeat all the above steps. Instead, run the workflow with a pre-configured sending journey. Provide the contact information of invitees and send the signing invitation.