CLM – Contract Relationships

⭐ Introduction

⚠️ Restricted access — This feature is available exclusively to certain clients under a specific contractual agreement. If you believe you should have access and do not see it, contact your Customer Success Manager.

The Contract Relationships module lets you formalise the links between related documents directly in DiliTrust CLM. Any contractual documents — regardless of their document type — can be grouped into a single contract bundle, navigated as a cascading hierarchy, and kept consistent by sharing key attributes — all without leaving the platform.

It answers a concrete need: contracts rarely exist in isolation, and a single procurement process can generate dozens of pre-contractual and contractual documents that must remain traceable next to the main contract. The module replaces flat, disconnected document lists with a structured contractual tree anchored in the document life cycle itself. It was rolled out progressively across several scopes, described below.

Permissions and access

Contract relationships rely on the existing document permissions, configured by the administrator:

• Administrators and Editors — can link and unlink documents, qualify the nature of each link, and share attribute values.
• Contributors — read-only access: they can browse the bundle hierarchy and the Linked documents panel, but cannot create or modify links.

Key points:

• The bundle hierarchy only displays documents the user is allowed to see. A document the user cannot access appears as a placeholder row that preserves the structure without exposing its content.
• Sharing an attribute value follows the edit rights on the source document.
• An attribute value can be shared with any document the user can access — the documents do not need to belong to the same bundle.

ℹ️ The feature itself remains subject to the restricted contractual access mentioned in the introduction. The activation modalities and the detail of authorised profiles will be specified soon.

⚙️ Module overview

The module is built on two main concepts:

• Contract bundle — a tree of documents linked together, with a main (root) document and documents linked beneath it, each qualified by a nature of link (Main Contract / Subcontract, Amendment, Appendix or Others).
• Attribute sharing — the propagation of a Summary Sheet attribute value from a source document to one or more target documents.

ℹ️ Any document type can be added to a contract bundle. The nature of the link qualifies the contractual relationship between documents — it is independent of the document type (a purchase order, a notification letter or a bidder offer are document types, not natures of link).

It comprises several scopes:

ℹ️ Availability:

Scopes 1 and 2 are available.

Multiselect linking and column management (Scope 3) are under development. Automatic linking of a bundle's documents through its parent, linking from the Advanced Data view, and the public API exposure of contractual relationships are also under development.

In this article:

TABLE DES MATIÈRES

• ⭐ Introduction
• Permissions and access
• ⚙️ Module overview
• 1️⃣ Scope 1: How to create a bundle
  • ⭐ Link types (nature of link)
  • ⭐ Linking documents
  • ⭐ The cascading bundle view
  • ⭐ The Linked documents panel
  • ⭐ How attribute sharing works
  • ⭐ Sharing an attribute
  • ⭐ Changing or removing a shared value
  • ⭐ Viewing attribute traceability
• 2️⃣ Scope 2: Advanced properties
• ⏳ Scope 3: Multiselect linking & column management (under development)
• ⭐ Best practices
• ⚠️ Limitations and points of attention
• ❓ Frequently asked questions

1️⃣ Scope 1: How to create a bundle

Scope 1 is the core of the module. It covers how documents are qualified and linked together, how the resulting contractual hierarchy is visualised, and how Summary Sheet attribute values are shared and traced across documents.

⭐ Link types (nature of link)

Every document linked beneath a main document is qualified with a nature of link that defines its role in the bundle. The main (root) document itself carries no nature of link; the nature qualifies each document linked beneath it.

Figure 1: Contract bundle structure — Main Contract at the root, with Subcontract, Amendment, Appendix and Others as direct children. A Subcontract can itself be the parent of further documents (unlimited levels).

ℹ️ A contract can have any number of linked documents, including appendixes — there is no enforced limit.

ℹ️ A document can be the child of one document and the parent of another. When a main document becomes linked beneath another, its existing nature of link is preserved.

⭐ Linking documents

Documents are imported as usual; linking is a separate, explicit step. To create or extend a bundle, use the Link documents flow from the folder view — or directly from a document's summary sheet via the Linked documents panel.

• In the folder view, open the actions menu of the document you want to use as the main document and select Link documents.
• Step 1 — select the documents to link from the folder selector. Newly imported documents can be selected here too. Documents already linked are shown as disabled, with a tooltip explaining why.

Figure 2 — Step 1: selecting the documents to link. Documents already linked to another bundle are shown as disabled with a tooltip. Selected documents appear as chips at the top of the panel.

• Step 2 — assign a nature of link to each selected document (Main Contract/Subcontract, Amendment, Appendix, Others). Each document's type is shown next to it to help you choose. Lini automatically suggests document types; adjust if needed.

Figure 3 — Step 2: the four available natures of link. The tooltip describes the attribute-sharing behaviour of each option.

• Click Confirm. A success message confirms the documents are linked.

Figure 4 — Click Confirm to finalise the bundle.

ℹ️ If a document's type is still being resolved by the platform, a loader is shown on the document type — you can still create the link; the rest of the flow is unchanged.

Linking a document that already belongs to a bundle:

• Selecting the main document of an existing bundle automatically includes all the documents linked to it.
• A document that is already a bundle root can only be linked as a Subcontract or Others.
• You can choose a different main document during linking; the documents associated with it are re-attached to the new bundle accordingly.

⭐ The cascading bundle view

As contractual structures grow — framework agreement → application contract → amendment → notification — a flat list is no longer enough. The folder and Contract room views display the full bundle as a cascading, indented hierarchy.

• Linked documents appear indented under their main document.
• Each row shows the document type, the nature of link and key dates — including values inherited through attribute sharing.
• Use the arrow to the left of a document to expand or collapse the documents linked beneath it.
• The hierarchy supports any depth (n levels), reflecting the real complexity of your contracts.

Figure 5 — The cascading bundle view

⭐ The Linked documents panel

Every document in a bundle has a Linked documents panel in its summary sheet, giving a structural overview without leaving the document. It keeps a consistent structure:

• Linked to / Main document — the document above the current one in the hierarchy (shown when the current document is at level 2 or lower).
• Current document — the document you are viewing.
• Amendment(s) — if applicable.
• Subcontract(s) — if applicable.
• Other(s) — if applicable.
• Appendices — if applicable.

Click any document in the panel to navigate directly to it, or start the linking flow to extend the bundle from here.

Figure 6 — The Linked documents panel

⭐ How attribute sharing works

Attribute sharing copies the value of a Summary Sheet attribute from a source document to one or more target documents, to keep key information consistent.

• Sharing is done from the Summary Sheet and is independent of the nature of link: a value can be shared with any document the user can access, whether or not the documents belong to the same bundle.
• Only attributes that have an entered value can be shared.
• Appendix or Other documents have no Summary Sheet and therefore cannot share or receive attribute values.

Attributes commonly shared include: expiration date, contract holder, contract value, counterparty name, applicable law and maximum budget amount.

⭐ Sharing an attribute

1. Open the source document and locate, in its Summary Sheet, the attribute whose value you want to share.
2. Hover over the attribute to reveal the Share icon, and click it.
3. In the file selector, choose the target document(s) — any documents you can access.
4. Confirm. The value is copied into the target document(s).

ℹ️ A badge next to the Share icon shows the number of documents the value has been shared with. There is no limit to the number of target documents.

Figure 7 — Hovering over an attribute reveals the Share icon. The badge shows how many documents already receive this value.

Figure 8 — The "Share the attribute value" window: selecting the documents that will receive the value.

Figure 9 — The attribute after sharing: the badge confirms the value has been propagated to the selected documents.

⭐ Changing or removing a shared value

• Remove a target — in the list of shared documents, click the X next to a document and confirm in the pop-up. The value is then cleared in that target document and must be re-entered if needed.
• Edit the value on a target document — this disconnects the share for that document; you are asked to confirm.
• Edit the value on the source document — the share connection is broken; verify the affected documents after the change.

⭐ Viewing attribute traceability

CLM shows where a shared value comes from and which documents have received it, supporting auditability for contract teams.

1. Open a document that has received a shared value.
2. In its Summary Sheet, the inherited value is marked with a shared icon.
3. Hover or click the icon to see the source document the value was shared from. If you do not have access to a related document, the available information is shown in the hover tip.

Figure 10 — Traceability on a target document: the attribute indicates the source document it was "shared from".

2️⃣ Scope 2: Advanced properties

The bundle panel is a dedicated side panel that opens when you click the bundle indicator on a document row. It gives a focused, contextual view of the bundle structure without leaving your current folder view.

Panel features:

• Bundle indicator — a visual marker on a document row signals it belongs to a bundle; clicking it opens the panel.
• Focused path display — the panel shows only the path to the selected document; other branches are collapsed under "Show X more documents".
• Permission-aware display — a document the user cannot access is shown as a placeholder row, preserving the structure without exposing its content.
• Document type display — each document shows its type to help qualify links quickly.

Advanced linking:

• Per-document qualification when linking within a folder or linking a bundle to another bundle.
• Linking a document that is the main document of an existing bundle automatically carries over the documents linked to it.

⏳ Scope 3: Multiselect linking & column management (under development)

The following capabilities are under development and will be available in an upcoming release:

• Multiselect document linking — linking several documents to a bundle in a single action, instead of one by one.
• Documentation toolbar & column management — a dedicated toolbar and expanded column management for bundle lists, for better navigation and customisation of bundle overviews.

⭐ Best practices

• Decide which document is the main document and which are linked beneath it before linking, so the hierarchy stays intuitive for everyone.
• Assign the nature of link precisely at creation, so the bundle reflects the real contractual structure.
• Use attribute sharing for fields that must stay consistent across related documents: contract value, counterparty name, applicable law, expiration date, maximum budget amount.
• Remember that an appendix has no Summary Sheet: capture shared values on the contract or its subcontracts/amendments rather than on appendixes.
• Review traceability before editing a shared value, to understand which documents will be affected — editing the value on a target disconnects the share.
• For public procurement, make sure the bundle contains all required documents: unique contract, terms of reference, bidder offer, notification letter, acknowledgement of receipt — and where applicable, subcontracting declaration and negotiation documents.

⚠️ Limitations and points of attention

• Attribute sharing is available only from a document that has a Summary Sheet: appendixes cannot share or receive attribute values.
• Sharing is independent of the nature of link and of bundle membership - except Appendix and Others: a value can be shared with any document the user can access.
• Editing a shared value — on the source or on a target — breaks or disconnects the share (a confirmation is requested). Removing a target clears its value, which must be re-entered if needed.
• Documents the current user cannot access appear as placeholder rows in the bundle hierarchy and the bundle panel: their position is visible but their content is not exposed.
• The available natures of link depend on your environment configuration — contact your administrator to adjust them.
• Automatic linking of a bundle's documents through its parent, linking from the Advanced Data view, and the public API exposure of contractual relationships are under development.

❓ Frequently asked questions

What is a contract bundle?
A group of documents formally linked in CLM — for example a framework agreement and all its application contracts, amendments, purchase orders and supporting documents. It reflects the real structure of a contractual relationship. Any document type can be added to a bundle.

What are the available natures of link?
Main Contract / Subcontract, Amendment, Appendix and Others. The main (root) document itself carries no nature of link. The nature of the link is independent of the document type.

Does attribute sharing depend on the nature of the link or on the bundle?
No. Sharing is done from the Summary Sheet and works with any document the user can access, whether or not the documents belong to the same bundle, and regardless of the nature of link — but Appendix and Others cannot share or receive values. .

Why can't I share a value with an appendix?
An appendix has no Summary Sheet, so it can neither share nor receive attribute values.

How do I know if a value was shared from another document?
The inherited value is marked with a shared icon in the Summary Sheet. Hover or click it to see the source document it was shared from.

What happens if I edit a shared value?
Editing the value on a target document disconnects the share for that document (you confirm). Editing it on the source breaks the share connection. Removing a target clears its value, which must be re-entered if needed.

Can a bundle have multiple levels?
Yes. A document can be linked beneath another and itself have documents linked beneath it. The cascading view displays the complete structure regardless of depth.

Is there a limit on the number of linked documents or appendixes?
No enforced limit.

What happens to the bundle structure when a user cannot access a document?
A placeholder row preserves the structure: the user sees that a document exists at that position but cannot access its content.

How do I find all the bundles for a given tender across the Contract room?
Use the filters described in the CLM – Advanced Data & Search article.