---
title: "Create Document Requests"
slug: "document-request"
updated: 2026-02-18T14:56:42Z
published: 2026-02-18T14:56:42Z
canonical: "knowledge.lightico.com/document-request"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.lightico.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create Document Requests

During a Lightico session, you can request supporting documents from a customer—such as ID cards, bank statements, or utility bills. When the customer opens a Document Request interaction, they can either upload a file or, if on a mobile device, take a photo of the document directly.

Document Requests can be added as steps in a Workflow or used as stand-alone interactions via the agent console or API. When used in a Workflow, Lightico can also authenticate documents and extract key data automatically.

![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/2024-07-29_17-42-44.PNG)

Document Request shown in the customer UI

---

## Document Request categories

Every Document Request in Lightico must belong to a category. Categories help organize and visually distinguish the types of Document Requests that you create in the following areas:

- **Document Requests page** - Click a category in the **Categories**pane to filter the Document Request list by category.
- **Workflow builder** - When you add documents to a Document Request step, you can filter the documents by category.

### Create new categories

Categories can be created in the Admin Center and may include examples like “Personal ID” and “Financial”.

**To create a Document Request category:**

1. In Admin Center, go to **Document Requests**.
2. In the Categories pane on the left, click **New category**. ![New category button in top of Categories panel on the Document Request page](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/2025-12-04_11-42-18(1).png) The **Create category** dialog opens.
3. In the **Category name**field, enter a name for the category.
4. In the **Category code**field, enter a string of lower-case letters and underscores (optional), without white spaces.
5. Select an Icon to associate with this category.
6. Click **Save**. ![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/2025-12-04_11-50-08.png)

### Edit a category

**To edit a category:**

Hover over the category and click the edit icon.

> [!NOTE]
> Note
> 
> You cannot edit the category code.

### Delete a category

**To delete a category:**

Hover over the category and click the delete icon.

> [!NOTE]
> Note
> 
> A category that contains documents cannot be deleted.

### Copy a category code

You may need to copy the category code for inclusion in an API endpoint.

**To copy a category code:**

Hover over the category and click the copy icon.

---

## Document Request types

A document type defines the specific document a customer is required to provide—such as a driver’s license, passport, or bank statement. Each type is grouped under a category ([see above](/v1/docs/document-request#document-request-categories)) to keep your document requests organized and easy to manage.

### Add document types

**To add a document type:**

1. In the **Document Requests**page, click **New document**in the top right corner. ![New document button shown in upper left of Document Request page](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/2025-12-04_11-42-18.png) The **Create document** dialog opens.
2. In the **Document name**field, enter a name that describes the document. This is the name that will appear for the customer in the session.

> [!TIP]
> Tip
> 
> When you add a Document Request step to a Workflow, you can add a description to each document. See [Add Document Requests to a Workflow](/v1/docs/add-document-requests-to-a-workflow#edit-the-document-request-step).
3. In the **Document code**field, enter a string of lower-case letters and underscores (optional), without white spaces.
4. From the **Category**dropdown, select a category to associate with the document.
5. Set the **Page limits**for pages or images that the customer can upload for this document. See [below](/v1/docs/document-request#set-page-limits).
6. To use Advanced processing for uploaded document, select a document type and configure the settings. See [below](/v1/docs/document-request#advanced-processing).
7. Click **Save**. ![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/image(415).png)

### Set page limits

You can define the **minimum and maximum** number of pages that a customer must upload for a Document Request. A “page” can refer to a traditional document page (for example, a page of text in a PDF) or a single image. Multi-page files are counted per page—for example, a 3-page PDF is treated as three pages, not one file.

When page limits are set, customers cannot complete the task until the number of uploaded pages falls within the required range. This helps ensure documents are submitted in the correct format and reduces incomplete or incorrect uploads.

![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/2025-12-03_16-32-49(1).png)

Document Request interaction on customer mobile device

> [!NOTE]
> Note
> 
> Page limits can be defined for Photo ID documents **only when extraction is off**; when extraction is on, customers are always required to upload exactly one image.

**To set page limits for a Document Request type:**

On the right side of the **Create**or **Edit document** dialog, under **Page limits**, select the minimum and maximum number of pages.

### Edit the document name

Double-click the document in the list, in the **Edit document** dialog - edit the name, and click **Save**.

### Delete the document

Hover over the document in the list, click the options menu and select **Delete**.

---

## Advanced processing

When creating a Document Request, you can enable advanced processing to apply additional validation, authentication, and automation to documents.

Advanced processing is supported for any document type that has a processing model, including custom-trained models and third-party integrations such as [Mitek](/v1/docs/mitek-document-and-id-authentication).

> [!TIP]
> Contact your Customer Success representative to enable and configure a **custom-trained processing model**.

### Capabilities

Advanced processing includes the following capabilities. Availability depends on the selected processing model and how the document is used in a Workflow.

#### Classification validation

Verifies that the uploaded document matches the **expected document type** (for example, confirming that the file is a driver’s license and not a different form of ID or document).

Classification validation focuses on **what the document is**, based on its visual structure and characteristics and the pass/fail result can then be used to decide the path of your customer in a Workflow.

#### Additional checks

After the classification is validated, checks for document integrity indicators.

#### Data extraction

Extracts structured data from the document —such as name, date of birth, and address—and allows you to bind that data to specific Attributes for use in the collaboration session or Workflow logic.

#### Photo ID authentication

Validates the authenticity of a supported photo ID by analyzing **whether the document appears to be genuine and unaltered**, rather than on identifying the document type. This includes checks for indicators of tampering, manipulation, or inconsistencies that suggest the document may not be legitimate.

Authentication **can also support identity verification** by enabling comparison between the photo ID image and a live selfie when configured in the [Photo IDV step in a Workflow](/v1/docs/customer-authentication-as-a-workflow-step#photo-id-verification).

#### AAMVA check

For supported US driver’s licenses, checks the document against AAMVA-registered information to add an additional layer of validation.

---

### How this works in practice

Advanced processing settings enable capabilities at the Document Request level, while the specific features applied depend on how the document is used in the Workflow.

- **Document Request Workflow step** - supports classification validation and data extraction, verifying that the uploaded document matches the expected license type and extracting key data fields for use later in the flow. See [Add Document Requests to a Workflow](/v1/docs/add-document-requests-to-a-workflow).
- **Photo ID Verification (Photo IDV) step** - supports authentication and you can **optionally enable a selfie capture** to perform customer identity verification by comparing the selfie to the photo on the ID. See [Customer verification as a Workflow step](/v1/docs/customer-authentication-as-a-workflow-step#photo-id-verification).

### Configure advanced processing

1. Follow the [directions for adding a document type above](/v1/docs/document-request#add-document-types).
2. Turn on the **Advanced processing toggle.** The **Select document type** dialog appears.
3. On the left side, select the processing model and then, on the right side, the document type.
4. Click **Save**. ![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/image(413).png)
5. Enable and configure any of the following optional settings:
  1. Enable **Classification validation**.
  2. When classification validation is enabled, select any **Additional checks** to perform.
  3. Enable **Photo ID authentication** and select what sides of the ID are required.

> [!NOTE]
> Note
> 
> If you select **back with barcode**, the capture will fail if a barcode is not detected on the back of the ID.
  4. Enable **AAMVA check**.
  5. Enable **Data extraction** and map extracted data categories to Attributes. These Attributes can be used in the context of a Workflow to populate data that was extracted from the document in a subsequent step, such as a [conditional element](/v1/docs/add-conditional-workflow-elements) or Form.
6. At the bottom of the dialog, click **Save**. ![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/2026-02-05_12-45-19.png)

### AADMV verification

You can add an additional layer of authentication for US driver's licenses by having the license checked against AAMVA registered information.

> [!TIP]
> To activate this feature, please speak to your Customer Success representative.

**To create a Document Request for a US driver's licenses with AAMVA verification:**

In the **Create document** dialog, turn on the **AAMVA Check** toggle.

---

## Q and A

### What if my customers will be scanning photo IDs or driver’s licenses with no barcode on the back side?

When you create the Photo ID Document Request, select **Front and back without barcode**. If you choose Front and back with barcode, the system will only verify the back of the ID when a barcode is detected. Using the correct option ensures the customer can submit both sides even when the document has no barcode.

### Can customers upload multi-page PDFs instead of individual images? How does Lightico count them?

Yes. Customers can upload multi-page PDF files, and Lightico will treat each page of the file as a separate page/image. For example, a 3-page PDF counts as three pages, not one file. If you set page limits, make sure they reflect the total number of pages expected—not just the number of files.

### What happens if a customer tries to upload more or fewer pages than allowed?

The customer cannot complete the Document Request until the number of uploaded pages is within the required range. The UI prompts them to add or remove pages/images as needed. This ensures you receive complete, correctly formatted submissions—reducing follow-up requests and manual correction.

A series of customer interactions that must be completed in a certain order. Workflows are configured by a business configurator (BC) and added to the session by an agent or API.

Interface in the Collaboration Room module for inviting participants to a collaboration session and for running the session by adding Workflows and other interactions

Area of the Lightico platform where you will find all settings, user management, and asset configuration pages. Access to this area is defined by a user's role and permissions.

An identifying label that you bind to data in a session that enables you to organize and make use of the data during the session.

Digital form that captures information provided by the customer or agent during a session.