The Clause Library stores clause language which is then used to generate contracts or other negotiable documents. This provides a single repository for all legal language, streamlines the document creation process, and allows sales teams to send out contracts without the need to involve the legal team in every deal.

The Clause Library works seamlessly with Conga Composer or X-Author for Contracts, giving you powerful document generation capabilities in addition to all the benefits of the Library itself.

The Clause Library is made up of several custom objects in the Contracts for Salesforce managed package. These are defined in more detail below.


The object that stores clause language used in generating contracts.

Clause Types

A way to build your Library and group clauses by the section of a contract that clauses should be inserted into. Clause Types can also be used to group by document types being created and negotiated.

Clause Categories

Used to group your clauses in categories like “Primary”, “Fallback”, “Amendment”, etc.

Clause Bundles

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 agreement. These clauses can be changed to track changes as the document is negotiated without impacting the master version in the Clause Library.

Alternate Clauses

Clauses tagged as alternates (or fallbacks) for existing clauses. Configuring alternate clauses allow end-users to swap rejected clauses for pre-approved alternates without involving legal.

Sub Clauses

An object that allows legal teams to define a clause hierarchy in the Clause Library. Ultimately, this allows you to format sub clauses in your agreements. Example:

  1. Parent Clause 1
    1. Sub Clause 1
    2. Sub Clause 2
    3. Sub Clause 3
  2. Parent Clause 2
    1. Sub Clause 4
    2. Sub Clause 5


Define the Library

  1. A Salesforce admin configures the object(s) to use with the Clause Library. In most cases this will be the Contract Agreement
  2. Admins create Clause Types and Clauses
  3. Admins define Alternate Clauses and Sub Clauses as necessary
  4. Admin creates Clause Bundles to define groups of clauses that are commonly added to the same type of document. In most cases, Clause Bundles correspond with the document type – MSA, NDA, SOW, etc.

Use the Clause Library

  1. End-users select the Clause Bundles that will be added to a specific agreement, or
  2. Admins can configure Conga Orchestrate to automatically add clauses to agreements based on data in Salesforce 3) Using Composer or X-Author, end-users will create the agreement and merge Managed Clauses into it

Negotiate using the Clause Library

  1. End-users send their agreement for negotiation
  2. As the clauses are negotiated, Contracts for Salesforce tracks and stores revisions of each clause in the Managed Clause records. This allows users and contract managers to easily identify when and where risk is introduced into agreements, as well as which clauses are frequently negotiated and how the language evolves over time

For more information, reference the documentation on the complete end-user process using Contracts for Salesforce.