!
Release: The following functionality will be live on August 13th. To learn more about the features included in our August release, refer to What's New in Ironclad: August 2026.
Summary
This article walks you through how to convert a local condition to a global condition in both Conditions Manager. To learn more about local and global conditions and how they differ, refer to Local and Global Conditions.
Use Case
Classics Inc. initially creates a local condition in its Vendor Agreement workflow to identify when a counterparty is based in the United States so the correct governing law clause appears in the contract. After noticing the same logic is also needed in Procurement, Sales, and NDA workflows, the legal operations team decides to convert that local condition into a global condition. By promoting it to global, Classics Inc. can reuse the same rule across multiple workflow configurations instead of rebuilding it each time. This reduces duplicate setup, makes future updates easier to manage, and helps ensure the same business logic is applied consistently across the company’s contracting processes.
Permissions
Features | Conditions, Conditions Manager, Workflow Designer |
Permissions | To view, use, and edit local conditions in Workflow Designer, you must have Workflow Designer access. |
Convert a Local Condition to a Global Condition in Conditions Manager
Click on your profile icon in the top right corner, and then select Company Settings > Conditions Manager.
Locate the local condition you want to convert to global, and then click Make Global.
A modal displays showing where the condition is currently used. Click Make global.
The condition is now global and available in both Conditions Manager and all of your workflow configurations.
Resources
Explore articles, courses, and support options to get the most out of Ironclad.
Help Center
Academy
No relevant resources at this time.