Go back to the Release Notes Hub
Welcome to Ironclad's Release Notes! This article highlights Ironclad’s new feature releases and existing feature updates. We update release notes the Monday of each release. Generally, each week's features are available to test in your demo environment by end-of-day Monday. The features are then added to your production environment by end-of-day Wednesday.
If you are interested in Ironclad CLM API updates, refer to the Ironclad API Changelog. Want to be updated about the latest and greatest changes to Ironclad's APIs? In your favorite RSS reader, add this link to subscribe for updates.
If you have questions about any of these features, submit a request with our Support Team.
June 19, 2024
At a Glance
This week's release includes the following features:
Feature Name |
Connect Multiple Salesforce Organizations to a Single Ironclad Instance |
Product Area |
CLM
Integrations
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
It has become increasingly common for Ironclad Salesforce integration users to have multiple Salesforce organizations that they actively use for various reasons, including acquisitions, differing product lines, and/or regions. You can now integrate all of your Salesforce organizations within a single Ironclad instance. This provides you with the benefits of using a single Ironclad instance to manage for setup, workflow management, unified dashboard, and unified repository based on existing permissions. |
Use Case |
Company A has two Salesforce orgs after acquiring Company B. Company A already has their original Salesforce org integrated with Ironclad and are loving the benefits of the seamless integration! Now, they want to glean the same benefits on Company B's Salesforce org. To do so, the Ironclad Admin and Salesforce Admin will work together to set this up. During the setup, they will connect the new Salesforce org with Ironclad, select the workflows they want to use with the new Salesforce org, and set up the data mapping configurations. After completing setup and launching their first workflow, Larry in Legal was able to see the workflows launched from both Salesforce orgs on the dashboard! |
Notes |
|
How to Enable |
An admin must enable this feature. To enable this functionality, navigate to Company Settings > Settings and toggle on Enable Multiple Salesforce Orgs. You can then connect your additional orgs to Ironclad. |
Relevant Resources |
Feature Name |
PactSafe Sign UpdateSigner API Security Fix |
Product Area |
Clickwrap
API
|
Impact of Change |
Signers who are attached to a draft or have sent signature requests can no longer have their emails or phone numbers edited (App/API). |
Roles Impacted | Admins and End Users |
Description |
Due to a security vulnerability discovered in the UpdateSigner API endpoint where unauthorized individuals could update the email, authorization controls were added to this endpoint that limits the change of the user’s email to only the necessary parties, such as the user themselves and an administrator. NOTE |
Use Case |
In the event that the Signer email and/or phone number needs to be updated, this can no longer happen while assigned to Signature Requests that have not been completed. Users will need to update the Signer email and/or phone number on the Signer Details page in the Classic UI. |
How to Enable |
This is on by default for all customers who send PactSafe Signature Requests via the Classic App or the API. |
Relevant Resources |
No related resources at this time. |
Feature Name |
eSignature Webhook Enhancements |
Product Area |
CLM
eSignature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
We've added two new webhooks for when signers view signature packets, and added additional data points to existing webhooks The following webhooks were added to help you listen for/take action of signature packet views. Both webhooks are only available for actions taken by signers; they are not available for viewers (i.e. CC recipients):
The following webhooks were updated to include additional payload data points. Any existing data points were not changed. Review the developer docs to understand the new data available for each webhook:
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
June 5, 2024
At a Glance
This week's release includes the following features:
Feature Name |
Out of Office |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
“Out of office” includes two features:
Out of office status is available to all users. Company Admins must enable the reassignment capability. For a list of frequently asked questions surrounding out of office, refer to Out of Office FAQs. |
How to Enable |
An admin must enable this feature. To enable this feature, navigate to Company Settings > Settings and toggle on Enable Out of Office Reassignment. |
Relevant Resources |
|
Feature Name |
Updated Ironclad Signature Permissions Nomenclature |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
UI Change |
Roles Impacted | Admins |
Description |
Previously
Updated |
How to Enable |
No action required. Automatically enabled for all Ironclad Signature users. |
Relevant Resources |
|
Feature Name |
Update Ironclad Signature Context Icons |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
UI Change |
Roles Impacted | Admins and End Users |
Description |
The icons in the Ironclad Signature Context modal have been updated to look less interactive. |
How to Enable |
No action required. Automatically enabled for all Ironclad Signature users. |
Relevant Resources |
No relevant resources at this time. |
Feature Name |
Default Apply Signature Everywhere to On |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
Minor Change |
Roles Impacted | Admins and End Users |
Description |
In the new Ironclad Signature UI, Apply Signatures Everywhere defaults to on. This means that unless the signer unchecks it, it will auto-populate all the signature or initial tags. Previously in the new Ironclad Signature UI, Apply Signatures Everywhere defaulted to off. |
How to Enable |
No action required. Automatically enabled for all Ironclad Signature users. |
Relevant Resources |
No relevant resources at this time |
Feature Name | |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
UI Change |
Roles Impacted | Admins and End Users |
Description |
The scale of Signature and Initials tags in Auto-format have been increased so they are more prominent (on all device types). |
How to Enable |
No action required. Automatically enabled for all Ironclad Signature users. |
Relevant Resources |
No relevant resources at this time. |
Feature Name |
AdobeSign Initials Update |
Product Area |
CLM
Integrations
|
Impact of Change |
Minor Change |
Roles Impacted | Admins and End Users |
Description |
Previously, when AdobeSign was set up as signature provider, we saw initials were not considered one of the tags that have to be required for AdobeSign. This was an issue when there was dual providers with AdobeSign or AdobeSign solo. Tooltip were also not explaining why a user could not send for signature. These have been updated. |
How to Enable |
No action required. Automatically enabled for all Ironclad Signature users. |
Relevant Resources |
No relevant resources at this time. |
May 22, 2024
At a Glance
This week's release includes the following features:
Feature Name | |
Product Area |
CLM
eSignature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
You can now make initial and signature tags optional. Previously, only checkboxes and text fields could be made optional. This provides greater customization so you can tailor your signature packet to your exact use case. |
Notes |
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
Feature Name |
Translated Ironclad Signature Experience for Unauthenticated Signers |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Previously, only authenticated signers had a translated Ironclad Signature experience. Now counterparty and unauthenticated signers will default to the browser language (if supported) and fall back on the company translation experience if the browser does not support browser languages. |
How to Enable |
An admin must enable this feature. To enable this feature, navigate to Company Settings > Settings and toggle on Enable Translations. |
Relevant Resources |
|
Feature Name |
Ironclad Signature Refresh |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
UI Change and Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
We have updated Ironclad Signature’s look and feel for easier signing. Signer tags, navigation, and styling have been simplified as part of this effort. In addition, these updates include exciting new functionality:
Save Signature for Future Use You can now save your signature to use the next time you need to sign a document. This functionality will lend to a faster signing experience. Use Case An Ironclad Signature user needs to sign a contract. They sign the document and save the signature for future use. Next time they need to sign a contract, they use their saved signature and formatting and apply it to all signature tags.
Apply Signature Everywhere
Multiple Fonts |
How to Enable |
No action required. Automatically enabled for all Ironclad Signature users. |
Relevant Resources |
|
Feature Name |
Improved AI Assist Redlines |
Product Area |
CLM
AI Assist
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
Previously, AI Assist would take the first preferable position in all AI Playbooks and redline the document. However, AI Assist would delete the whole paragraph in the document. Now, AI Assist will compare the paragraph in the document against the first preferable position in playbooks and redline based on the differences. This provides a more elegant redline option where only necessary redlines are applied, and to limit the frequency of crossing out whole paragraphs. Before this update, AI Assist only redlined differences on clauses with payments terms duration and governing law state. This update applies to all clauses. |
Notes |
|
How to Enable |
No action required. Automatically enabled for all AI Assist users. |
Relevant Resources |
No relevant resources at this time. |
May 15, 2024
At a Glance
This week's release includes the following features:
Feature Name | |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
Expanded Functionality |
Roles Impacted |
Admins and End Users |
Description |
We have added links to learn more about Ironclad Signature in two places:
Counterparty Landing Page
Company Settings Utilization Page |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
Feature Name |
Dropbox Sign Email Tag Truncated |
Product Area |
CLM
eSignature
|
Impact of Change |
UI Change |
Roles Impacted | Admins and End Users |
Description |
Previously, when a document was sent for signature from Ironclad using Dropbox Sign, email signer tags were getting truncated. This has been updated. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
Feature Name |
Updated Ironclad Signature Icons |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
UI Change |
Roles Impacted | Admins and End Users |
Description |
We have updated Ironclad's Signature's icons for both desktop and mobile. These updates will lend to a more cohesive design experience.
Desktop
Mobile |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
May 8, 2024
At a Glance
This week's release includes the following features:
Feature Name |
Dependency Visualizer |
Product Area |
CLM
Workflow Designer
|
Impact of Change |
Expanded Functionality |
Roles Impacted |
Admins |
Description | The Dependency Visualizer in Workflow Designer enables you to search for a property and visualize the fields, conditions, roles, and form questions it depends on. This helps you to understand complex workflow configurations, address errors, and make/test changes. |
Use Case |
An Ironclad admin wants to understand why a property in Workflow Designer is functioning the way that it is. They open the Dependency Visualizer to view how the property relates to other fields, conditions, roles, and form questions in Workflow Designer. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
Feature Name |
URLs Updated to Include Company ID |
Product Area |
CLM
|
Impact of Change |
Process Change |
Roles Impacted | Admins and End Users |
Description |
We have updated a majority of post-authentication (logged in) URLs to include your company's unique ID. This update will improve performance and stability of the application. URL paths are still unique to each customer. All existing URLs will continue to work as they will redirect to the new URLs. There will be no impact to bookmarks or saved links. If you use any app on top of Ironclad that relies on a specific URL path, like in-app guidance tools (e.g. Walkme, Spekit, Bento), you will likely have to update the URLs to the new format. |
Example |
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
Feature Name |
Custom Clauses Training Impact |
Product Area |
CLM
AI
|
Impact of Change |
Expanded Functionality |
Roles Impacted |
Admins |
Description |
When training your AI clauses, you can now view real time how much of a training impact an example will have. Unique training samples will help AI accurately detect clauses that are similar to the samples. Based on this indicator, you can decide whether or not to provide the sample. |
Use Case |
An Ironclad admin wants to train their AI model to detect a clause in specific contexts. They locate the AI clause on the AI Clauses page, click on it to edit it, and then enter an example. They refer to the Training impact beneath the example, tailoring their example until the impact is Strong. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
Feature Name |
Custom Clauses Similarity Threshold |
Product Area |
CLM
AI
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins |
Description |
You can now define the threshold AI should follow for AI to detect a specific clause in your documents. When you select exact match, this means AI will look for clauses in documents (when using AI Playbooks or Smart Import) that look exactly the same as the samples provided to train this specific clause. This provides you greater control over how sensitive your AI detection should be for the clause in AI Playbooks and Smart Import documents. |
Use Case |
An Ironclad Admin wants to adjust a specific clause to only be detected when it is an exact match. They locate the AI clause on the AI Clauses page, click on it to edit it, and adjust the Detection Settings to Exact match. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
May 1, 2024
At a Glance
This week's release includes the following features:
Feature Name |
SCIM Scoped Tokens |
Product Area |
CLM
API
|
Impact of Change |
Process Change |
Roles Impacted |
Admins |
Description |
The Ironclad platform supports SCIM for user provisioning. Customers mainly integrate tools like Okta and Azure Active Directory for this purpose. These integrations need an Ironclad API token to work properly with our SCIM API. You can now create a token that can only access the specific resources needed to power that integration. |
Use Case |
An Ironclad user wants to use SCIM for user provisioning. They generate a SCIM scoped API token and use it to integrate Okta with their Ironclad instance. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
Feature Name |
Admin Permission Usability |
Product Area |
CLM
Admin
|
Impact of Change |
UI Change |
Roles Impacted | Admins and End Users |
Description |
Group permissions will be grouped into "General Permissions" and "Admin Permissions”. The admin permissions section will also include a link to a Help Center article that will help you determine if the update you are making will change the group’s seat type. This update will make it easier to distinguish if the impact of updating permissions could result in the group being changed to an Admin seat type. |
Use Case |
An administrator wants to adjust a group's permissions. When editing the group's permissions, they can easily discern which permissions may result in upgrading the group's seat types to admin. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
Feature Name | |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
UI Change |
Roles Impacted | Admins and End Users |
Description |
Previously, completed signature/initials tags were occasionally rendering smaller and would then jump to a larger size upon click. This has been updated so that completed signature/initial tags display as their true size. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
Feature Name |
Checkbox Signature Tag Too Long |
Product Area |
CLM
Ironclad Signature
|
Impact of Change |
UI Change |
Roles Impacted | Admins and End Users |
Description |
Previously, in Ironclad Signature, the checkbox signer tag was too long, causing it to overflow to the next line. This was particularly noticeable in mobile format. This has been updated to so that checkbox signer tags display correctly. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
April 17, 2024
At a Glance
This week's release includes the following features:
Feature Name |
AI Playbooks Term Duration Detected |
Product Area |
CLM
AI
|
Impact of Change |
Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
In AI Playbooks, if we detect term duration as "30 calendar days", then we will display "30 days" as the term duration. This will help you standardize the jurisdiction data across your contracts, creating tidier and more detailed records with less effort. |
Use Case |
An Ironclad user uploads a document using Smart Import. Ironclad detects the words "30 calendar days" as the term duration. "30 days" is recorded as the term duration. |
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
Feature Name |
AI Playbooks and Smart Import Jurisdiction Detected |
Product Area |
CLM
AI
|
Impact of Change | Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
In AI Playbooks and Smart Import, if we detect a jurisdiction as "State of ___", then we will display the state's name as the jurisdiction to the end user. This will help you standardize the jurisdiction data across your contracts and records, creating tidier and more detailed records with less effort. |
Use Case | An Ironclad user uploads a document using Smart Import. Ironclad detects the words "State of California" as the jurisdiction. "California" is recorded as the jurisdiction. |
How to Enable | No action required. Automatically enabled for all users. |
Relevant Resources |
No relevant resources at this time. |
April 10, 2024
At a Glance
This week's release includes the following features:
Feature Name |
Workflow Launch Improvements |
Product Area |
CLM
Workflows
|
Impact of Change |
UI Change |
Roles Impacted | Admins and End Users |
Description |
We have made a variety of small improvements to the workflow launch experience. These changes include:
These improvements will:
|
How to Enable |
No action required. Automatically enabled for all users. |
Relevant Resources |
|
Feature Name |
Send Directly for Signature from Dashboard |
Product Area |
CLM
Ironclad Signature
|
Impact of Change | Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
You can now upload a document in CLM and place tags to send it out for signature without having to configure a workflow. This functionality provides even more application possibilities for Ironclad Signature, saving you time when a workflow is not the best path for your contract.
If you have this functionality enabled, on your Dashboard, you will see a New button with a dropdown to start a workflow. |
Use Case | An Ironclad Signature user has a document that has already been negotiated outside of the CLM platform and needs to send out for signature. They upload the document and send it out for signature, skipping the workflow process entirely. |
How to Enable | This is automatically turned on for users in the “Administrators” group, but for other users, it must be enabled by an administrator. If you are an administrator and want to enable this functionality for your users, refer to Configure Ironclad Signature. |
Relevant Resources |
|
Feature Name |
AI Playbooks Reviewer Notes and Automated Comments |
Product Area |
CLM
Playbooks
|
Impact of Change | Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
AI Playbooks users can now configure positions to include internal reviewer notes and quickly add or automate external document comments. This reduces review time and back-and-forth communication while providing context as to why certain changes have been made. |
Use Case | An administrator configures their company's playbooks. When they configure a clause, they can add a note for internal reviewers to give them context on when and how to use the clause. The administrator can also add a note to share with counterparties to help them understand why the change is being proposed. |
How to Enable | No action required. Automatically enabled for all users. |
Relevant Resources |
|
April 3, 2024
At a Glance
This week's release includes the following features:
No feature releases this week.
Feature Name |
Run AI (Beta Release) |
Product Area |
CLM
AI
|
Impact of Change | Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
The Run AI button enables you to use bulk actions to gather Ironclad's Smart Import suggestions on any existing records in your Repository. This functionality provides the following benefits:
|
Use Case | An Ironclad Smart Import user wants to use the latest AI suggestions to update their Smart Import records. They select a batch of records and use Run AI to get the latest AI suggestions. |
How to Enable | This feature is currently in beta and Ironclad must manually enable it. If you are interested in enrolling in this beta, please reach out to your Ironclad representative. |
Relevant Resources | No relevant resources at this time. |
Feature Name |
Ironclad Signature In-App Guides |
Product Area |
CLM
Ironclad Signature
|
Impact of Change | Expanded Functionality |
Roles Impacted | Admins and End Users |
Description |
You will see in-app guides when you are nearing and have reached your Ironclad Signature free trial threshold. These in-app guides will provide you with next steps to continue using Ironclad Signature. |
Use Case | An Ironclad user is testing Ironclad Signature using a free trial. When they reach 20 sends remaining, they receive an in-app notification alerting them of the end of their trial nearing its end. They click Learn More to review next steps to continue using Ironclad Signature. |
Notes |
|
How to Enable | No action required. Automatically enabled for all Ironclad Signature users. |
Relevant Resources | No relevant resources at this time. |
Feature Name |
"Generate Report" Button Removed |
Product Area |
CLM
UI/UX
|
Impact of Change | Quality-of-Life Improvement |
Roles Impacted | Admins and End Users |
Description |
The Generate Report button has been removed. The metrics found in this report can be found elsewhere in Ironclad CLM using Dashboard Export. Dashboard Export provides more granular filtering on workflows, as well as faster downloads of the data. |
How to Enable | No action required. Automatically implemented for all users. |
Relevant Resources |
|