The Clause Library stores pre-approved clauses which are used to generate contracts or other negotiable documents, eliminating the need to involve the legal team in every deal.

The Clause Library is primarily meant for customers using Conga Composer as their document generation solution for Contracts for Salesforce, as opposed to customers using Salesforce CPQ for document generation.
The Clause Library consists of the following custom objects in the Contracts for Salesforce managed package:

Clause Types

A way to define clauses based on the different document types being negotiated.


The object that stores the pre-approved clauses used for generating contracts.

Clause Bundles

Defined groups of clauses that are commonly added to the same type of document.

Managed Clauses

A copy of clauses from the Clause Library tied to a specific contract or record. These clauses can be changed as the document is negotiated without impacting the master version in the Clause Library.

Alternate Clauses

Clauses tagged as alternates for existing clauses. Attaching alternates to a clause allows end-users to swap rejected clauses for pre-approved alternates.

Sub Clauses

Sub Clauses are a separate, related object to Clauses that allow users to include additional child clauses related to a Master Clause.

After creating Clause Types and Clauses, the admin creates Clause Bundles to define groups of clauses that are commonly added to the same type of document. End-users can then select the Clause Bundles to add Managed Clauses to a specific record. These Managed Clauses are merged into the document using Conga Composer.

As the clauses are negotiated, revisions of each clause are stored with the Managed Clauses. This allows Contracts for Salesforce customers to easily identify when and where risk is introduced into their agreements, as well as which clauses are frequently negotiated and how the language evolves over time.

To configure the Clause Library:

  1. See Setup Contracts for Salesforce to select the standard or custom objects you want to use with the Clause Library.
  2. (Optional) Create Clause Types for grouping your clauses.
  3. Create Clauses.
  4. Create Clause Bundles to define specific groups of clauses commonly added to the same document type.
  5. (Optional). Create Alternate Clauses.
  6. (Optional). Create Sub Clauses.

When the above is completed by the admin, end-users can then create Managed Clauses by selecting Clause Bundles as part of the end-user process, create documents, and send for negotiation.

Later, if the admin wants to update clauses in the Clause Library based on revisions made to Managed Clauses during negotiation, they will have to create new clause revisions.