Summary
iinked Sign 4.1 brings several exciting features further enhancing the user experience and functionality of the platform:
- In response to customer feedback, iinked Sign now supports replayable iink Signatures. You can configure a Signing Package to allow signers to reuse the same iink Signature across all documents within that Package. The signature is reusable only within the Signing Package and cannot be saved or applied to other packages ensuring strict compliance and control.
- Packages can now be created without documents. This allows you to set up Identity Verification (IDV)-only workflows when documents are not yet available, or to provide a standalone IDV experience during an onboarding process of a client.
- Package senders can now add Witnesses to Sequential Signing Packages. A Witness is a signer who signs the document immediately after the person they are witnessing for. Senders can also include unnamed Witnesses, enabling each signer to designate their own Witness when that information is not known at the time of package creation.
- Added another cloud storage integration: Xerox DocuShare Go
- Organization Administrators (OAs) can now manage Multi-Factor Authentication (MFA) settings for individual members directly from the Member Management section.
iinked 4.1 New Features
-
Document Signing
- Replayable iinked Signatures allow signers to add their handwritten signature once when signing a document and reuse it across all signature fields within the same Package. This feature streamlines the signing experience by enabling signers to apply their last used iink signature or initials in a document without needing to redraw or resend them each time. This signing method needs to be enabled in the Package defaults/settings and the replayable iink Signature is only available on a per Package basis.
-
Packages and Templating
- The Witness Signer feature allows a designated witness, where permitted, to observe and attest to a signer’s signature, enabling secure and compliant witness signing workflows. The Package Sender can add either a named witness, if the witness is known, or an unnamed witness if the witness is not yet identified. Multiple witnesses can be added for each signer, providing the flexibility to meet various compliance requirements. If unnamed witnesses are added when creating the Package, the signers will have to enter in their witness' details during the signing process. The witness will then be added as a signer to the Package and will sign on their own device. All witness details and actions are securely recorded in the MasterFile, ensuring a complete audit trail. Please note that the Witness Signer feature is available as an add-on and must be enabled as part of your iinked Sign subscription. For step-by-step details, please review this help article.
- Packages can now be created without documents. This permits the use case where Identity Verification (IDV) needs to be performed prior to documents being available. This provides greater flexibility in managing signing workflows by enabling you to verify the signer’s identity at an early stage of the process. Once the signer successfully completes ID verification, the Package Owner can later edit the same Package and add documents for signing without any additional cost. The MasterFile will display the IDV results and all the updates to the Package up to its completion.
-
Cloud Storage Integrations for Document Management
- In addition to our existing cloud storage integrations with Microsoft OneDrive, SharePoint, and Xerox DocuShare Flex, iinked Sign now also integrates with Xerox DocuShare Go. This integration enables users to securely import documents and store completed Packages and MasterFiles directly in their DocuShare Go environment, providing greater flexibility and seamless document management across supported cloud storage platforms.
- Improvements have been made to the cloud storage integrations to provide better visibility and control when exporting Packages to connected storage services. Package Owners can now clearly see when an export fails due to access or permission issues, including access denial errors. This enhanced visibility allows users to quickly identify and resolve problems, such as expired permissions or authorization issues, ensuring successful export of completed Packages and MasterFiles. These improvements help reduce disruptions and make cloud storage integration more reliable and easier to manage.
-
Organization and Member Management
Organization Administrators (OAs) can now disable and enable (previously configured) Multi-Factor Authentication (MFA) for individual members directly from the member management section. This provides greater control over account security by allowing administrators to enforce MFA for members who require additional protection or disable it where appropriate based on organizational policies.
Update rollout begins February 2026.