This article provides context for the upgrade to the new Ironclad Signature from the classic solution, powered by DropboxSign.
Context Surrounding the New Ironclad Signature
Ironclad partners with external eSignature providers to support end-to-end contracting. Historically, we offered a white-labeled integration with DropboxSign (formerly HelloSign) as an option for customers not using one of our supported integrations.
In 2021, Ironclad acquired PactSafe, the leader in clickwrap technology. PactSafe’s primary mission was to push the limits of contract acceptance velocity and volume, and did so by defining the Clickwrap Transaction Platform (CTP). Now, we’re excited to use that same technology to rebuild Ironclad Signature from the ground up, rethinking everything from how it looks to how it integrates with the workflows already powering your contracts.
Customers using classic Ironclad Signature will be automatically upgraded to the new solution. Use this article and the additional resources below to better understand the differences and next steps:
Common Questions
Is the upgrade optional?
No, this is not optional. We’re sure you’ll love the new solution, but you can also use one of our 3rd party signature providers with – or instead of – the new solution.
Do I need to take action?
Ironclad will manage the upgrade automatically, but we encourage you to review the enablement material prior to the upgrade.
What will happen to in-flight workflows or signatures?
Any in-flight signature packets will still be managed by DropboxSign. Any signature packets sent after your upgrade will be sent using the new Ironclad Signature service.
Will I still have access to previously executed contracts?
Yes, you will continue to have access to all previously executed agreements within your Ironclad Repository.
Will there be any interruption to my service?
We’re not anticipating any interruption to your service, and will be actively monitoring the system during and following the upgrade.
Is this new solution legally compliant?
This solution is compliant for most contracts within the United States (ESIGN & UETA), and many contracts in Europe (eIDAS SES), but we recommend reviewing Ironclad Signature Compliance in detail to understand supported jurisdictions.
Ironclad Signature Comparison Chart
While the process for both internal and external signers remains largely the same, there are some differences between the two solutions. For the majority of workflows, these differences will be minor, but we recommend reviewing this chart in detail:
| Functionality | Use Case | Classic | New | Notes |
|---|---|---|---|---|
| Electronic record of signature | Provide proof of signature with a timestamp | Yes | Yes | |
| Signature input (“scribble” signature) | Allow a signer to demonstrate their intent to sign | Yes | Yes | The classic Ironclad Signature supports typed, drawn, uploaded, and smartphone options. The new solution currently only supports typed. |
| In-app signing | Internal signers can easily access signature request | No | Yes | |
| View workflow and contract context | No | Yes | Internal signers can see approver and signer context, as well as key terms of the contract prior to signing. | |
| Configure a URL for redirecting signers post-signature | Integrate signing into downstream processes | No | Yes | |
| Customizable signature request email | Provide additional written context to signers | Yes | Yes | |
| Custom “From” name in email header | Provide signers a more recognizable “from” name | No | Yes | The email domain is ironcladapp.com, but the name in the email will be your company name. |
| Custom “Reply-to” email address | Capture replies to the signature request email | No | Yes | |
| Signer verification | Require signers to verify their identity before accessing the document | No | Yes | Signers can be emailed a one-time-password. This is the recommended best practice. |
| Notifications and reminders | Notify signers of action needed | Yes | Yes | Signers and CC recipients receive email notifications throughout the signing process. Automated reminders are configurable in the native Ironclad Signature. 3 and 7-day reminders were available in classic. |
| Signer activity (Activity Feed) | Observe when a party viewed and signed the packet | Yes | Yes | |
| Access partially signed documents | Pull partially signed documents out of Ironclad | No | Yes | |
| Signature packet expiration | Increase security on signature requests | No | Yes | Signing links automatically expire after 30 days, then a new signing link will be created for that signature packet. |
| Localized signing experience | View a non-English signing experience | Yes | No | Portuguese (Brazil), French, Japanese, Spanish (Spain), German languages are supported in Ironclad Signature upon request. |
| EU data residency | Send out contracts to parties guided by EU regulations | Yes | No | |
| LE Builder workflow compatibility | Support for our legacy workflow system | Yes | No | You must be transitioned off LE Builder workflows to begin using the new Ironclad Signature. |