Clickwrap Workflows Overview

This article will provide you with an overview of Clickwrap workflows.

What Is a Clickwrap Workflow?

A Clickwrap workflow lets companies capture a user's acceptance of terms through an embedded experience—typically with a checkbox, acceptance language, and access to view the terms. Clickwrap Workflows are built for standard agreements where contract acknowledgment is required and contracts remain static or can be updated dynamically. Bringing Clickwrap Workflows into CLM allows Ironclad customers to leverage the power of Workflow Designer to build workflows.

As a user fills out information on your website, they will be presented with customizable acceptance language and a link to download the contracts being accepted.

When a user accepts the terms by checking a box, their acceptance is recorded and tracked in Ironclad. While acceptance is often captured upon form submission, you can configure exactly when acceptance is recorded in your implementation. You can find and review the executed agreement and any additional metadata in the Ironclad CLM Dashboard by opening the corresponding record.

You can click the updated record in the Activity Feed to view the fully generated document and the electronic acceptance record.

Create a Clickwrap Workflow Configuration in Workflow Designer

To create an embedded Clickwrap workflow, first build a workflow configuration in Workflow Designer.

After you create the workflow configuration, a technical user on your team can implement it by adding the embed link—found in the Sign tab of the Workflow Designer—to your website’s code. For detailed technical instructions on how to implement an embedded Clickwrap workflow, refer to our Developer Documentation (Coming Soon).

Create a Clickwrap Workflow in Workflow Designer

To create a Clickwrap workflow, select New clickwrap workflow in Workflow Designer. You will:

1. Configure basic workflow information like the name and workflow owner (Workflow Settings)
2. Upload one or multiple documents (Document tab)
3. Define the data you will capture as part of the agreement (Create tab)
4. Define the domains the clickwrap can render on (Create tab)
5. Define the acceptance experience your counterparty will see (Sign tab)
6. Configure what will happen once the document is signed (Archive tab)
7. Publish the workflow

After the workflow is published, work with your implementation partner to add the embed link to your website’s code. Once added, the counterparty will be presented the ability to view the document(s) and accept them with a simple checkbox. We call this a “clickwrap agreement” or “clickwrap.” Accepted agreements are available in Ironclad along with any metadata captured and the certificate of completion needed for electronic signing.

For detailed technical instructions on how to implement an embedded Clickwrap workflow, refer to our Developer Documentation (Coming Soon).

Configure a Clickwrap Workflow

Within Workflow Designer, you will have different configuration options available that you can learn more about here. Many of these are shared across internal and public workflows, but here are some key differences to be aware of when configuring a clickwrap workflow.

1. You will not have a paper source option; only company paper is supported. (Document tab)
2. Launch Forms are not shown to your counterparty. Instead, use the Launch Form to define the data you want to capture, and work with your implementation team to ensure that data is captured on your website and passed to Ironclad using the API. (Create tab)
3. You must define the domains the clickwrap is allowed to appear on. (Create tab)
4. Clickwrap workflows do not support approvals (Review tab)
5. Clickwrap agreements have one counterparty signer; internal signers and multiple signers are not available (Sign tab)
6. You can configure the acceptance language presented to the counterparty. Documents are displayed the the counterparty, accepted with a single checkbox, and can be downloaded to the counterparty’s device prior to signing for review. To embed the full document in your experience or support difference acceptance methods, refer to embedded signing. (Sign tab)
7. Clickwrap workflows always auto-archive by default. (Archive tab)