> **Source:** https://knowledge.leegality.com/document-execution/esign-type/aadhaar/prioritise-aadhaar-for-invitee
> **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

---
# Prioritise Aadhaar for Invitee

This section provides instructions for prioritizing the Aadhaar eSign option over other eSign methods for an invitee during the document signing process. By prioritizing Aadhaar eSign, you ensure that it is presented as the first signing option to the user, even if you have enabled multiple other eSign methods for the document.

This configuration provides flexibility by offering the user various choices while directing them to your organization's preferred method first.

#### New Document Journey

## New Document

Use the following steps to configure Aadhaar eSign priority when initiating a new document.

1. While initiating a document, go to the **Invitee level options**.
2. Toggle on **Prioritise Aadhaar for Invitee**.
   - If enabled, the invitee will see the Aadhaar eSign options first. Other selected eSign options are displayed only after the configured Aadhaar eSign attempts are exhausted.
3. Toggle on **Order Level Retry Count** (Optional)
   - Enable this setting to define a specific display order for the different Aadhaar verification subtypes (such as OTP, Biometric, Face Auth or Iris scan).
   - When enabled, retries are counted collectively for all subtypes with the same Order number. The system proceeds to the next Order priority only after maximum attempts for the current Order group are exhausted.
4. Set the number of **retry attempts** for each subtype. This is the maximum number of attempts an invitee has for a specific subtype after the initial unsuccessful attempt.
5. Set the **Order** for each subtype to specify the priority in which it should appear to the invitee.
6. Click **Save**.

#### Workflow Creation

## Workflow Creation

Use the following steps to configure Aadhaar eSign priority within a workflow configuration.

**Prerequisite:** Before you begin, enable Aadhaar under Signature type.

1. While initiating a document, go to the **More Options**.
2. Toggle on **Prioritise Aadhaar for Invitee**.
   - If enabled, the invitee will see the Aadhaar eSign options first. Other selected eSign options are displayed only after the configured Aadhaar eSign attempts are exhausted.
3. Toggle on **Order Level Retry Count** (Optional)
   - Enable this setting to define a specific display order for the different Aadhaar verification subtypes (such as OTP, Biometric, Face Auth or Iris scan).
   - When multiple subtypes are arranged in a specific order, The system will only proceed to the next Order priority group after the invitee has exhausted the maximum retry attempts set for the preceding subtype.
   - If a specific order is not configured, the OTP method is displayed first by default.

> **Info — NOTE**
>
> The Order level retry count is fixed and cannot be changed while running the workflow. To make changes you need to edit the workflow.

4. Set the number of **retry attempts** for each subtype. This is the maximum number of attempts an invitee has for a specific subtype after the initial unsuccessful attempt.

> **Info — Retry limit**
>
> The retry limit must be between 0 and 5.
>    - A limit of 0 grants the User only the original attempt.
>    - A limit between 1 and 5 allows the User the original attempt plus the configured number of additional retries.

5. Set the **Order** for each subtype to specify the priority in which it should appear to the invitee.
6. Click **Save**.

## How Prioritization Affects the Signing Journey

When Aadhaar eSign prioritization is enabled, the invitee's signing experience is structured to present Aadhaar verification methods first, before any other eSign options become available. This section explains how the signing flow changes with prioritization enabled.

### Standard Signing Flow vs. Prioritized Flow

**Without Prioritization:**
When multiple eSign methods are enabled (such as Aadhaar OTP, DSC, Quick Sign), the invitee can freely choose any available option to sign the document immediately upon reaching the signing page.

**With Prioritization Enabled:**
The invitee must first attempt signing using the Aadhaar eSign methods in the configured order and exhaust the allowed retry attempts before other eSign options become visible.

### Invitee Signing Experience

When an invitee receives a document with Aadhaar prioritization enabled, the signing journey follows this flow:

1. The invitee receives the invitation via email, SMS, or WhatsApp and clicks the signing link.
2. After previewing the document and clicking **Proceed**, they are presented with the available Aadhaar eSign methods.
3. The Aadhaar verification subtypes (OTP, Biometric, Face Auth, or Iris) appear in the order configured by the sender.
4. The invitee selects an available Aadhaar method and proceeds with the verification.

### How Retry Attempts Work

The retry attempt configuration determines how many times an invitee can attempt each Aadhaar verification subtype:

- **Initial Attempt:** The invitee makes their first signing attempt with the chosen Aadhaar method.
- **Retry Attempts:** If the verification fails (e.g., incorrect OTP, biometric mismatch, face authentication failure), the invitee can retry based on the configured retry limit (0-5 additional attempts).
- **Exhausted Attempts:** Once all retry attempts for a subtype are exhausted, the system proceeds according to your configuration:
  - If other Aadhaar subtypes are available in the next order group, those options appear next.
  - If all Aadhaar retry attempts are exhausted, other eSign methods (if enabled) become available.

### Order Level Retry Count Behavior

When **Order Level Retry Count** is enabled, the retry attempts are counted collectively for all Aadhaar subtypes that share the same order number:

- **Collective Retry Count:** The system counts retry attempts collectively across all subtypes in that order number.
- **Progression:** The system only moves to the next order priority after the maximum retry attempts for any subtype within the current order group are exhausted.

### When Other eSign Methods Become Available

If you have enabled multiple eSign types (e.g., Aadhaar, DSC, Quick Sign) and have prioritized Aadhaar:

1. The invitee initially sees only Aadhaar eSign options in the configured order.
2. They must exhaust all configured Aadhaar retry attempts across all order groups.
3. Only after all Aadhaar attempts are exhausted do the other eSign methods (DSC, Quick Sign, etc.) become visible and selectable.

This ensures your preferred verification method (Aadhaar) is attempted first while still providing alternative signing options if needed.

> **Info — NOTE**
>
> The invitee can still complete the signing process even if Aadhaar verification fails, as long as you have configured alternative eSign methods.