Document library and contracts

Last updated: 2026–08-19

Documents and contracts cover two related jobs: keeping applicant-facing document types consistent across products, and building the legal agreements — loan agreements, disclosures — that applicants sign to close a loan. The Document Library handles the first job. Contract Builder handles the second.

Document library

The document library typically lists document types or templates that can be requested from applicants or attached to applications.

Open Document Library from Workflows.
View the list of document types or templates.
Depending on your role, you may be able to add, edit, or deactivate entries.

Documents attached to a specific application are viewed on the application detail page.

Contract Builder

Contract Builder is where you create and maintain the agreement templates presented to applicants — loan agreements, disclosures, and similar documents — and control how they get signed.

The contract list

Open Contract Builder from the sidebar to see every contract in your tenant. The list shows name, version, creation date, who created it, whether it is published, and whether it is active. You can search the list, filter by active/published/blocked status, and sort by any of those columns.

From the list you can:

Create a contract. Give it a name and choose a body format (rich text or HTML). The system creates a draft and opens it in the editor.
Clone a contract. You must give the clone a name different from the original — the system rejects a clone that reuses the source contract’s name. Contract names are limited to 60 characters.
Turn a contract active or inactive without deleting it.

Building the contract

Inside the editor you configure:

Contract type. One type is DocuSign-based e-signature. If you choose it, you must select a DocuSign template before you can save — the system blocks saving otherwise.
Products. Assign the contract to one or more lending products.
Decision outcomes. Assign the contract to specific decision outcomes, so it is only presented when that outcome fires.
Signers. Configure a primary signer and up to five co-signers, each with a name and email address.
Email template. If you turn on the primary signer and add at least one co-signer, you must also select an email template. The system blocks saving until you do.
Variables. Insert variables into the contract body (for example, applicant name, loan amount) that get filled in when the contract is generated for an application.
DocuSign field mapping. For DocuSign contracts, map each field (“tab”) on the uploaded DocuSign template to a contract variable. Variables can be numbers, text, yes/no values, lists, or dates. You can preview the DocuSign template from inside the editor before mapping.

As you work, the editor surfaces warnings for common problems before you publish — for example, a missing email variable, missing signing blocks, unmapped variables, or missing signer configuration.

Versions and publishing

Saving a contract keeps it in draft. Publishing creates a numbered version with a required description of what changed, and you choose whether to mark that version as the default. If you don’t mark it default, the previous default version stays in effect until you promote the new one.

On the versions screen for a contract you can:

View every version with its description, creation date, last-updated date, and whether it’s the current default.
Set any earlier version as the default.
Copy a published version back into a draft so you can edit it further.
Preview a version.

Worked example

A tenant admin needs a loan agreement for a new product, Signature Personal Loan ($5,000–$35,000, unsecured), with DocuSign e-signature and a co-signer option.

From Contract Builder, the admin creates a contract named “Signature Personal Loan Agreement” and picks rich text as the body format. The system creates the draft and opens the editor.
The admin sets the contract type to DocuSign e-signature and selects the DocuSign template “Personal Loan Agreement v3.” The system requires this before the draft can be saved.
The admin assigns the contract to the “Signature Personal Loan” product and to the “Approved” decision outcome.
The admin turns on the primary signer and adds a co-signer with email jane.doe@example.com. Because a co-signer is now configured, the system requires an email template — the admin selects “Loan Agreement Ready for Signature.”
The admin maps the DocuSign template’s tabs — ApplicantName, LoanAmount, APR — to the matching contract variables.
The admin saves the draft. The editor shows no outstanding warnings, since every tab is mapped.
The admin clicks Publish, enters the description “Add co-signer support,” checks “set as default,” and publishes. The contract becomes version 2 and the default version applications now use.

Use case

A credit union requires a co-signer on its shared secured loan product whenever the applicant’s FICO score falls in the 620–659 band. Loan operations builds a dedicated contract with two co-signer slots and a DocuSign template mapped to applicant name, loan amount, and APR. They assign the contract to the “Shared Secured Loan” product and to the “Approved – Co-signer Required” decision outcome, so it only appears for applications that land on that outcome, while applicants above 660 continue to receive the standard single-signer agreement.

Best practices

Give each contract a distinct, descriptive name — clones must use a different name than the original, and names are capped at 60 characters.
Only set the contract type to DocuSign e-signature once you have the DocuSign template ready; the system won’t let you save without one selected.
Map every DocuSign tab to a variable before publishing. Unmapped tabs generate a warning you should resolve rather than ignore.
If you enable co-signers, set up the required email template at the same time — saving is blocked until you do.
Use the publish description field to record what actually changed in each version, so the version history stays useful.
Deactivate contracts you no longer use instead of leaving them live in the list.
Preview a contract version before making it the default, especially after changing DocuSign field mappings.

Use the document library and Contract Builder together to keep required documents and legal copy consistent across applications.

Document library and contracts ​