Contracts are often part of a larger relationship, not standalone documents. You may have multiple contracts tied to the same counterparty, such as a Master Service Agreement, related SOWs, and amendments. These contracts can reference or modify one another, and understanding how they relate to one another helps paint a broader picture of your agreements with a specific entity.
A contract hierarchy is a structured view of these connected contracts, showing how they relate so you can evaluate the full scope of your contracts with an entity.
Use Case
Classics Inc. has a long-term partnership with WonderWeb that includes multiple agreements: a Master Service Agreement (MSA), several Statements of Work (SOWs), and amendments. When a legal team member needs to review obligations or negotiate a new contract, it can be difficult to understand how all these documents connect.
Using contract hierarchies, the team can see the structured view of the MSA, its related SOWs, and any amendments.
Permissions
| Features | Entities |
| Permissions | Admin role OR Repository and Entities = View, edit, and create access to all Record types and Entity types (current and future) |
Step 1: Export Entities
- Click on the Entities tab.
-
Click the three stacked dots located in the top right corner, and then click Export view.
- Click Export.
Step 2: Update Entity Information in the Spreadsheet
- Open the spreadsheet.
-
Make any necessary changes.
Note: You can delete any columns that you don’t want to update.
- If you want to update an entity’s status, in the Status column, enter ACTIVE or INACTIVE. This must be in all caps.
- If you want to update the entity’s relationship type, in the Relationship Type column, enter the relationship type’s key. The relationship type key can be found in Data Manager.
- Save the spreadsheet.
Step 3: Re-Import the Entities
- Click on the Entities tab.
-
Click the three stacked dots located in the top right corner, and then click Import entities.
- Click New Import and upload your new spreadsheet.
- Map your spreadsheet column headers to entity properties. If the column name matches a property, it is automatically mapped. Otherwise, you must manually map your columns during the import process.
- Select the appropriate entity property for each column.
- If a property is missing, add it via Entities Properties in Data Manager. Important
- Map the entity name to the system “Name” property; otherwise, imported entities will be labeled “Imported.”
- Map the "record ID" (ie. d307076a-6825-44d3-b25b-1494e4c4b144) to the system "ID" property. Mapping other IDs, such as the Ironclad ID (ie. Entity -1) or an external ID may lead to an error.
- Configure the Merge duplicates using drop-down. Choose a property to control which should be used as a reference between Ironclad and the spreadsheet when updating existing entities. This allows you to make sure the right entities in Ironclad get updated with the right data. The options include:
- ID: This will use the entity identification number (ie. d307076a-6825-44d3-b25b-1494e4c4b144) to match the data in your spreadsheet to the entities in Ironclad. If any entities in your spreadsheet don’t have an ID listed, a new entity will be created.
- Name (recommended): This will use the “Entity name” to match the data in your spreadsheet to the entities in Ironclad. This is the best option if you want to ensure that you don’t have any duplicate entities with the same name.
- Create all new entities: This will create all new entities. This does not check for duplicates.
Resources
Explore articles, courses, and support options to get the most out of Ironclad.