--- title: "Configure consent settings" slug: "configure-consent-settings" updated: 2024-12-17T08:50:20Z published: 2024-12-17T08:50:20Z canonical: "knowledge.lightico.com/configure-consent-settings" --- > ## 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. # Configure consent settings ## Importance of obtaining customer consent > [!WARNING] > Attention > > The following explanation is provided for educational purposes only. Please consult your legal advisors to fully understand the specific requirements for obtaining customer consent based on your business and jurisdiction. When conducting business in a digital environment—such as signing or approving documents—obtaining clear consent from customers is not only a best practice but also a legal and ethical necessity. Consent ensures that customers fully understand and agree to participate in the transaction under the terms outlined. ### Benefits of obtaining clear customer consent #### Legal compliance Many regions and industries require explicit customer consent for digital transactions to comply with local and international laws, such as the eSign Act in the United States or GDPR in Europe. Without proper consent, the transaction could be deemed invalid or unenforceable. #### Building trust Asking for consent demonstrates transparency and professionalism. It reassures customers that their rights are respected and that the process is secure, fostering trust in your business practices. #### Protecting your business Consent provides a clear record that a customer has voluntarily agreed to the transaction. This protects your organization against potential disputes, misunderstandings, or claims of fraud. #### Enhancing CX By ensuring customers are informed and on board, the process becomes smoother and more collaborative. Customers are more likely to feel confident and engaged when they know their consent is valued. --- ## How to obtain consent Consent ensures that customers understand and willingly agree to the transaction or process they are engaging in. Below are some key guidelines to follow when obtaining consent: ### Be clear - Use simple, straightforward language to explain what the customer is consenting to. - Avoid technical jargon or overly complex terms that may confuse or overwhelm the customer. - State the purpose of the transaction or process in plain language, so the customer fully understands what is being requested. - Example: “By checking this box, you agree to sign the loan application digitally and submit it to XYZ Bank for processing.” ### Be specific - Incorporate a clear acknowledgment step where the customer must actively confirm their consent. This could be: - A checkbox the customer selects. - A digital signature the customer provides. - A confirmation button or acknowledgment prompt that requires interaction. - Ensure that this step is unambiguous and directly tied to their consent. Passive consent (e.g., pre-checked boxes) should be avoided to ensure clarity and compliance. ### Provide an opportunity to review - Before requesting consent, ensure that customers have ample opportunity to review all relevant information: - Terms and conditions of the transaction. - Any applicable disclaimers, policies, or important details. - Present the information in a way that is easy to navigate, such as a scrollable text box, a downloadable PDF, or a clickable link. - Give customers the ability to ask questions or seek clarification if something is unclear. --- ## Consent in a Lightico session Lightico enables you to create consent pages for a collaboration session which require a customer to read and approve conditions for entering the session and completing digital processes and documents. The consent requirements are configured globally in system settings and as part of the documents and Workflows on which you collaborate with customers. This standardizes your process of obtaining consent. You can set a general consent page to appear at the beginning of a session or Workflow and you can also present a consent before individual documents. | ![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/2024-12-04_11-13-59.png) Session consent page | ![](https://cdn.document360.io/473bb8c5-ff1b-4930-8109-2321ac6ab967/Images/Documentation/2024-12-04_11-12-06.png) Document consent page | | --- | --- | ### Types of Lightico consent In Lightico settings, consent requirements are split into 2 types of settings: - [Session consent](/v1/docs/configure-consent-settings#session-consent) - [Signature and approval consent](/v1/docs/configure-consent-settings#signature-and-approval-consent) See below for an explanation of each. ### Session consent Consent before entering a Collaboration Room is a general agreement for all business that will take place in the session which could include signatures and approvals on multiple documents. This consent page is activated from system settings under **Session > Preferences**. For more information, see [Configure customer consent](/v1/docs/customer-consent). ### Signature and approval consent Signature and approval consent pages are displayed per Workflow or individual document once a session has started. In a single session you could include multiple consent pages, each obtaining consent for a different Workflow or document. You can include a consent page for some documents and not include for others. To understand signature and approval consent, it’s important to be familiar with the different setting options in different parts of the Lightico platform, including what is the hierarchy of settings if they contradict one another. Below are the consent setting options listed from lowest precedence to highest: #### System settings - Overridden by any consent settings in PDF Templates or Workflows. - Set two global policies, one for signature and one for approval whether to include consent. - Edit the text for the customer consent page. This is the text that will appear for all consent pages, even when the consent page is included because of the PDF or Workflow settings. - For more information, see [Configure customer consent](https://knowledge.lightico.com/docs/customer-consent#signature-and-approval-consent). #### PDF Template - Overrides system settings. - Choose whether to require customer consent for each document. - For more information, see [Configure PDF Template settings](https://knowledge.lightico.com/docs/new-pdf-builder-configure-pdf-settings#require-consent-message-before-signing-or-approving). #### Workflow - Overrides system and PDF Template consent settings. - Choose one of the following options: - Only a single consent page at the beginning of the Workflow - Consent pages according to the settings of each individual document - No consent page for the Workflow or any of the individual documents - For more information, see [Configure Workflow settings](https://knowledge.lightico.com/docs/configure-workflow-settings#define-customer-consent-policy). --- ## Consent for External Documents and Dynamic Documents (HTML) This section explains your options for requiring customer consent for External Documents and Dynamic Documents that do not have their own consent settings. To require customer consent for stand-alone External Documents, you have the following options: - Make sure system settings are set to require customer consent - Use an overlay template that requires customer consent To require customer consent for External Documents and Dynamic Documents in a Workflow, you have the following options: - Set the Workflow to show **Single consent** - Set the system settings to require customer consent and set the Workflow to **Use document configuration** 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. A module within the Lightico Platform that enables you to complete all parts of a customer journey from a single, chat-style interface. You can obtain signatures, verify ID, collect supporting documentation, collect payments and more. A PDF document that has been enhanced with interactive fields so that it can be completed by a customer in a session. A PDF document that is uploaded to a session from a source other than Lightico, for example, from the agent’s computer. Documents created entirely in the Lightico UI, displayed as dynamic HTML and converted to PDF after signing or approval.