This article will provide you with an overview of Ironclad Signature.
Ironclad Signature makes it easy for you to get documents signed electronically. Whether you want traditional eSignature, documents beautifully rendered on your website, or anything in between, Ironclad Signature helps you design the optimal signing experiences for your customers, executives, and internal stakeholders.
There are a number of ways you can send a document for signature:
- From a CLM Workflow: select Ironclad Signature at the Sign Step to route signature requests through Ironclad Signature. Signers can sign throughout the document, or with a single click (click-to-accept).
- From the CLM Dashboard: upload, stamp, and send documents for signature without configuring a workflow.
- Via the API: programmatically generate and render documents outside of Ironclad.
Each method is optimized for different business processes and offers different options for document generation, delivery, and assent capturing. Regardless of the path you choose, the rendered document and associated metadata is available in Ironclad Repository post-signature.
Capture Assent with Ironclad Signature
How you ask signers to provide assent can vary depending on your business, business process, contract type, region, and more. Ironclad Signature uses our robust Activity API to capture the metadata data necessary to generate a legally binding record of acceptance, and offers flexible ways to capture assent.
- With a signature: type your name or initials in various places throughout the document. This is the most common form of capturing assent and feels the most like signing a physical document.
- With a click: sign the document with a single click rather than interacting with various sections of the document. This is the fastest way to sign a document and can be used in CLM Workflows (Click-to-Accept) or experiences you create (Embedded Clickwrap).
FAQs
Which browsers are supported?
We recommend Google Chrome for desktop, and Google Chrome or Safari on mobile devices.
Which document elements are supported in mobile-friendly views?
Most elements are supported. Page numbers, headers, footers, tables of contents, superscripts, subscripts, and text boxes are only available in the PDF view. If there is a signature tag in one of these elements, Ironclad Signature will automatically display the PDF view before allowing signature.
Can the signature experience be translated?
Yes. If CLM Translation is enabled in your company, the signing experience and signature request emails will be translated. For internal signers, the language displayed is based on the user’s setting. Otherwise, the language displayed is based on the user’s browser setting. For the list of supported languages and how to configure translations, refer to the Ironclad CLM Translation Overview.
Can I add someone as a CC recipient?
Yes. You can add a CC recipient in Workflow Designer, or add them to an active workflow during the Sign step. CC recipients can access updates on the workflow and are able to view, but not sign, the document.
Can I monitor or report on contracts sent directly for signature versus from a workflow?
You can keep track of these contracts in a variety of ways. The easiest is to create a Dashboard view and filter it by the Straight to eSignature workflow configuration. This option only displays after a contract has been sent for signature using this method. You can also filter by specific record types that your company used for this method in the Repository.
What metadata is included in when sending directly for signature via Ironclad Signature?
The counterparty name and record type are required to send. Additional record metadata can be added post-signature as needed in the Repository.
I use a cloud storage integration. Will contracts sent directly for signature via Ironclad Signature be saved to my cloud storage provider?
Yes, they will automatically be backed up to your cloud storage. The file path cannot be configured and is the Workflow Designer default, which is:
<Folder that is pre-set in Integrations> / <Record Type> / <Counterparty Name> / <Signed or Drafts folder> / File Name
Can I define an expiration date?
No. All Ironclad Signature packet links expire after 30 days. If the signer attempts to view the signature packet, it generates an updated link that is sent to the signer's email.