--- title: "Add Document Requests to a Workflow" slug: "add-document-requests-to-a-workflow" updated: 2026-04-26T07:53:33Z published: 2026-04-26T07:53:33Z canonical: "knowledge.lightico.com/add-document-requests-to-a-workflow" --- > ## 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. # Add Document Requests to a Workflow A Document Request step enables you to obtain essential supporting documentation from customers. Whether it’s financial statements, legal forms, or personal ID documents, this step ensures that the required materials are promptly submitted. ![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/Snag_6c0bdc7f.png) --- ## Preparing to add a Document Request to a Workflow Before adding a Document Request step to a Workflow, make sure the required Document Requests are already configured in the Document Request configuration page. - **Create the relevant Document Request types** you plan to use in the Workflow (for example, a US driver’s license, passport, utility bill, bank statement, or other document type). For instructions, see [Create Document Requests](/v1/docs/document-request). - **Configure advanced processing** for any Document Requests that require classification validation, data extraction, or **photo ID authentication**. For more information, see [Advanced processing](/v1/docs/document-request#advanced-processing). --- ## How to add a Document Request step 1. Drag the **Document Request**item from the left pane. The Document request dialog box opens. 2. In the left pane, select the category of Document Requests to filter the list of document types or select **All**. 3. In the middle pane, select documents that you want to request from the customer. ![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/doc-requ-wf.png) > [!TIP] > Tip > > If the document includes data extraction, an icon is displayed next to the document. You can click on the icon to see which Attributes are bound to the extraction results. ![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/data%20extraction%20icon(1).png) The selected items appear in the right panel. 4. Click the **x**next to any of the selected items to remove them from this step. 5. Click **Done**. ![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/doc-requ-wf-2.png) The Document Request item is added to the canvas and displays the number of documents you included in that step. ![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/image-1717509953223.png) --- ## Edit the Document Request step After adding the Document Request item to the Workflow canvas, you can select it, and, in the *right panel*, edit it as follows: - **Step name** - Click the edit icon and change the name that appears for this step in the collaboration session. - **Included documents** - Shows which documents are being requested: - Click **Edit list** to add or remove documents - Click one of the documents to do any of the following: - **Description** - Add a description that clarifies what is required. For example, if the required document is a bank statement, include the following description: *Please upload 3 months of statements.* > [!TIP] > A description can also be added or edited by the agent in the session, see [Send a Workflow that requires agent input](/v1/docs/send-a-workflow-that-requires-agent-input#editing-a-document-request-step). - **Extract data** - Enable data extraction from this document and bind the data to Attributes for use in the session. See [below](/v1/docs/add-document-requests-to-a-workflow#advanced-processing-options). - **Validate classification** - Enable validating the document before the customer continues (see [below](/v1/docs/add-document-requests-to-a-workflow#advanced-processing-options)). Optionally, select a Boolean Attribute to which to bind the result. - **Additional checks** - Enable checking optional factors (see [below](/v1/docs/add-document-requests-to-a-workflow#additional-checks)). Optionally, select a Boolean Attribute to which to bind the result. - **Allow****minimum required** - Allow the customer to select from the list of documents as long as they provide the minimum number. Turn on the toggle and, under **Documents required,** set the minimum number of documents required. See [below](/v1/docs/add-document-requests-to-a-workflow#minimum-required-documents)for more information about this setting. - **Allow agent selection** - Allow agents to select which documents from the defined list are required (see next settings and [below](/v1/docs/design-workflows#empowering-agents-to-select-and-create-documents)) - **Agent instructions** - (optional) Provide an explanation of this step for the agent to help them understand what documents are required - **Allow custom documents** - Allow agents to add custom documents to the required list - **Capture-only mode** - Limits customer to scanning a document and does not allow them to upload a file of the document. This ensures that customers submit real-time, authentic document captures. See [below](/v1/docs/add-document-requests-to-a-workflow#captureonly-mode). - **Send step data to email** - Turn on the toggle and select an email connector hub to have session sent to a predefined email at the completion of this step. For more information, see [Configure general Workflow settings](/v1/docs/configure-workflow-settings#send-workflow-data-to-an-email-address). ![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/2026-01-07_17-39-14.png) Use the context menu above the selected item to do the following: - Duplicate this step - Delete this step ![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/image(52).png) --- ## Empowering agents to select and create documents The types of documents that are included in a Document Request step are defined by the Administrator/BC that creates the Workflow. However, you may have a Workflow that requires flexibility for which documents are included in the final required list that is sent to the customer. In this case, the Administrator can allow agents to edit the list of documents and even to create custom ones as they are adding the Workflow to the session (see [Send a Workflow that requires agent input](/v1/docs/send-a-workflow-that-requires-agent-input#editing-a-document-request-step). **To empower agents to select and create documents:** After adding the Document Request step to the Workflow, turn on the relevant settings in the *right panel* (see **Allow agent selection** and **Allow custom documents**[above](/v1/docs/add-document-requests-to-a-workflow#edit-the-document-request-step)). --- ## Minimum required documents The **Minimum required documents** setting allows you to define how many documents must be uploaded in a Document Request step, without requiring specific document types. Instead of forcing customers to provide fixed documents, you can allow any combination from a predefined list—as long as the required number is met. This is useful in scenarios where multiple document types can serve the same purpose, such as proof of income or identity verification. ### How it works When configuring a Document Request step in the Workflow builder: - Select one or more document types that the customer can upload - Set the **minimum number of documents** required (0–N) - By default, all selected documents are required unless a minimum is defined - Optional: Enable **Allow agent selection** to let agents choose which documents to request before sending the step, see [below](/v1/docs/add-document-requests-to-a-workflow#agent-behavior-optional-configuration) ### Customer experience During the session: - The customer sees the full list of available document options - If a minimum is defined, guidance indicates how many documents must be uploaded - The **Next** button is enabled only after the requirement is met - A validation message confirms when enough documents have been uploaded - Customers can upload more documents than the minimum if needed ### Making the step optional If you set the minimum to **0**: - The step becomes optional - A **Skip** option is available to the customer - If skipped, the step is marked as completed without any uploads ### Agent behavior (optional configuration) If **Allow agent selection** is enabled: - The agent must select documents before sending the step - The system enforces the minimum requirement - A message indicates the requirement (for example, “At least X documents are required”) - Sending is blocked until the minimum is met > [!NOTE] > Note > > Even when the minimum is set to 0, the agent must select at least one document before sending the step. ### Example use case A banking Workflow includes an income verification step. Instead of requiring specific documents, the business configurator defines a list that includes payslips, bank statements, and tax documents, with a minimum of two. Customers can upload any two of these documents based on what they have available. This reduces back-and-forth and allows the process to move forward without delays. --- ## Advanced processing options Advanced processing options are configured when you **create a Document Request** (see [Advanced processing for Document Requests](/v1/docs/document-request#advanced-processing)) and are then **enabled in the Workflow builder**. Each Document Request Workflow step can include multiple documents, and advanced processing settings are configured per document. So, you can choose which documents in the step are enabled for advanced processing options. The following advanced processing options are supported in a Document Request Workflow step. > [!TIP] > To perform Photo ID authentication in a Workflow, see [Customer verification as a Workflow step](/v1/docs/customer-authentication-as-a-workflow-step). ### Data extraction When data extraction is enabled, the system analyzes the uploaded document and extracts structured data. Extracted data is: - Bound to Attributes for use within the session (for example, conditions and content personalization) - Included in the **Workflow step element completed** event, making it available to downstream systems in real time ### Classification validation Classification validation verifies that the document uploaded by the customer matches the **expected document type** for the Document Request (for example, confirming that a driver’s license was uploaded when a driver’s license was requested). When classification validation is enabled, you must connect the Workflow step to **separate paths for pass and fail results**, allowing you to control how the Workflow continues in each case. If the uploaded document does not match the expected type, the Workflow follows the configured fail path. > [!TIP] > Tip > > When one of the included Document Requests includes classification validation we recommend not including any other documents in the step. A validation failure of one document will cause the customer to go down the *fail* path even if the other documents passed. ### Additional checks Additional checks include optional validation mechanisms that evaluate the uploaded document beyond classification. Currently, the available additional check is: #### Risk indicators When **Risk indicators** is selected, the system evaluates the uploaded document for predefined signals that may indicate potential issues requiring closer review. If such indicators are detected, the document is flagged as failing the check. You can use this result to route the Workflow differently—for example, by directing the session to a manual review step or applying additional verification steps. As with classification validation, you must configure separate paths in the Workflow builder to determine how the process continues when a risk indicator is triggered. --- ## Capture-only mode Capture only mode is a setting that requires the customer to capture documents using their device camera only. This ensures that documents are captured in real time, rather than uploaded from their device. When **capture-only mode** is enabled (see [above](/v1/docs/add-document-requests-to-a-workflow#edit-the-document-request-step)), customers who enter the Document Request step using a desktop or laptop will see a message explaining that a mobile device is required to continue. Since desktops or laptops may not support real-time image capture for document scanning, the message gives them the option to request a new session invite—allowing them to switch to a mobile device and complete the step successfully. ![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/image(400).png) An interaction in a Lightico session that enables customers to provide supporting documentation by uploading a file or scanning the document using a mobile device. A user that communicates with end-customers to complete tasks in a Collaboration Room session or a Case Manager case. 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. A Lightico user with a business configurator or BC role configures elements of the Lightico journey in the Admin Center pages.