Release May 26, 2026

This release extends multi-participant support to Dynamic Documents and brings OTP authentication and case note improvements to Case Manager — giving teams more control over complex, multi-party processes and customer verification workflows.

Collaboration Room

👥 Multi-participant support for Dynamic Documents

Dynamic Documents now support multiple participants, bringing the same multi-party capabilities already available for PDF Templates to Dynamic Documents as well. Businesses can now collect input, approvals, and signatures from several participants within a single Dynamic Document, while benefiting from its dynamic structure and real-time presentation.

Business Configurators can assign roles such as signers, approvers, and viewers, define who signs where, and ensure all required participants complete their part. Invitations are triggered at the right point in the Workflow.

This makes it easier to run multi-party processes on Dynamic Documents, without relying on static PDFs, while maintaining control, accuracy, and a seamless participant experience.

For more information, see Add multiple participants to a Dynamic Document.

Case Manager

🔢 OTP authentication for customer engagement tasks

Case Manager now supports OTP (One-Time Passcode) authentication for customer engagement tasks. When OTP is enabled, agents need to provide a second contact channel — aside from the original invitation channel — to which the OTP is delivered automatically to the customer when they reach the authentication point.

When a customer engagement task includes OTP verification, a status indicator on the task row shows whether verification is pending, passed, or failed, giving agents visibility without having to open the task.

For more information, see Create a Workflow for a case task.

🔒 Lock and unlock case notes faster

The padlock icon on each case note now shows the lock state at a glance and toggles it in one click, replacing the previous options menu.

For more information about working with notes in Case Manager, see Complete a case.

Fixes

Collaboration Room

Resolved the following issues:

• Tables containing images inside table cells rendered incorrectly during customer sessions.

• An invalid error message was displayed on agent-facing Forms when navigating back to a previously filled page containing text Attributes that allow digits.

• In specific cases, customers were prompted to complete identity verification a second time within the same session despite a successful pass on the first attempt.

• IDV retry attempts were not being enforced correctly, allowing customers to exceed the configured retry limit.

• Identity verification results did not always return to the corresponding session record in Lightico.

• A signature was missing from a completed and locked document despite the audit confirming it had been signed.

• When a Workflow switch or condition step contained six or more conditions, the conditions list overflowed the popup and some conditions became unclickable.

• When an HTML step with "Send step data to email" was also configured for customer download or review, only the CSV file was included in the email and the completed document was omitted.

• If a Document Request was deleted while still referenced in a Workflow step, that Workflow could no longer be edited or removed.

Admin Center

Resolved the following issues:

• When an image upload failed in Shared Items, no error message was shown to the user.

• Using the zoom function in the PDF Template editor caused field placeholders to shift position on publish.

• Table width changes made in the visual editor were not reflected in the editor view, only in the live session.

• Configuration options toggled off in the Lightico for Salesforce settings did not save correctly.

Case Manager

Resolved the following issues:

• When a custom "New Conversation" form exceeded the visible area, no scroll bar was available.

Document Analyzer

Resolved the following issues:

• When creating or updating a rule with a condition JSON that exceeded the maximum allowed size, the API returned a 500 error instead of a 400.

System Usage

Resolved the following issues:

• In specific cases, older sessions were not accessible for reuse despite the reuse setting being enabled.

• Updating an existing dataset by uploading a new file incorrectly returned a "Name must be unique" error.

• Resetting a sandbox password redirected the user to the production login URL upon completion.

Events

Resolved the following issues:

• API events triggered by patching a Workflow to complete were incorrectly labeled as "customer" under the originator field instead of "API."

Release timeline