> **Source:** https://knowledge.leegality.com/deal-collaboration/Obligations/Settings/obligation-library
> **Site:** Leegality Knowledge Base — https://knowledge.leegality.com
> **About:** Leegality is a document execution platform covering eSigning, stamps, NeSL, workflows, and REST API integration.
> **Navigation:** Every article on this site has a plain-text version at `<article-url>.txt` (this format). To get an index of all articles with their `.txt` links, read: https://knowledge.leegality.com/llms.txt
> **AI Guide:** For instructions on how to navigate this knowledge base as an AI agent, read: https://knowledge.leegality.com/ai-readable.txt

---
# Obligation Library

> The Obligation Library is where your obligation templates live. A template tells the AI what to look for in your contracts, and how each obligation it finds sho

The Obligation Library is where your obligation templates live. A template tells the AI what to look for in your contracts, and how each obligation it finds should be set up, including when it falls due and who is responsible for it.

Your organisation starts with a set of default templates covering common commitments, such as renewal notices and auto-renewal opt-outs. You can use these as they are, edit them to suit your contracts, or add your own alongside them. See [Creating an Obligation Template](https://knowledge.leegality.com/deal-collaboration/Obligations/Settings/create-obligation-template) for how to build one.

## Opening the Library

1. Go to **Settings**.
2. In the sidebar, click **Obligations**.
3. Open the **Library** tab. Your obligation templates are listed.

## Library Columns

<!-- ARCADE · P2 · Tour the Library
     Show: the template list, Configure Columns to reveal Reference variable, then filtering by Category.
     Call out: no screenshot of this screen exists anywhere in the docs.
-->

| Column | What it shows |
| :--- | :--- |
| **Obligation name** | This column shows the name of the template. It is always visible and cannot be hidden. |
| **Category** | This column shows the [category](https://knowledge.leegality.com/deal-collaboration/Obligations/Settings/obligation-categories) that the template is grouped under. |
| **Type** | This column shows whether the template is a **Default** one that came with the module, or a **Custom** one that your team created. |
| **Due Date** | This column shows how the due date is worked out, either **Linked variable**, **Directly extracted**, or **Not configured**. |
| **Scope** | This column shows the workflows and document templates that the template applies to. |
| **Status** | This column shows whether the template is **Active** or **Disabled**. |

You can add four more columns through **Configure Columns**: **Priority**, **Responsibility**, **Assignee**, and **Reference variable**.

## Row Actions

Click the **Three Dots (⋮)** on an entry to:

- **View:** Open the template's configuration in read-only mode.
- **Edit:** Modify the template's configuration.
- **Duplicate:** Create a copy of the template to use as a starting point for a new one.
- **Disable:** Stop the module from extracting this obligation going forward, without deleting existing data.
- **Enable:** Put a disabled template back into use.
- **Delete:** Remove the template.

> **Note — Some templates can't be deleted**
>
> Default templates cannot be deleted, so disable them instead. Their names cannot be changed either, although the rest of their configuration can be edited.
> 
> A template cannot be enabled while its category is disabled. Enable the category first.

Template names must be unique within your organization. Names are limited to 100 characters and descriptions to 2,000.

## Finding a Template

Use the search box to find a template by name. To narrow the list further, use **Filters**. You can filter by category, status, priority, responsibility and type, as well as by the reference variable a template uses, the workflows and document templates in its scope, and who it is assigned to.

## Related Pages

- [Creating an Obligation Template](https://knowledge.leegality.com/deal-collaboration/Obligations/Settings/create-obligation-template)
- [Managing Obligation Categories](https://knowledge.leegality.com/deal-collaboration/Obligations/Settings/obligation-categories)
- [Obligation Settings](https://knowledge.leegality.com/deal-collaboration/Obligations/Settings/obligation-settings)

<!-- ==================== POC REVIEW NOTES (not rendered) ====================
Verified against obligation/constants/template.py,
obligation/constants/filters/category_configs.py (which holds the template
filter config despite its filename), and the frontend slice
slices/obligation-templates/ (constants/obligation-template-table-columns.js,
obligation-template-test-ids.js).

CONFIRMED CORRECT: the ten filters and their labels were accurate in the
previous version — Category, Status, Priority, Responsibility, Type, Reference
Variable, Scope (Workflow), Scope (Template), Assignee (by user), Assignee (by
contract role). Only the value lists needed tidying.

CORRECTIONS MADE:
- TYPE COLUMN was wrong and mattered most. The previous version said Type is
  "whether the template creates a One-time or Scheduled obligation". Type is
  Default vs Custom — whether the template shipped with the module or your team
  created it. (The column id is `source` and it renders a source badge.)
  Frequency is not a library column at all.
- DUE DATE column values were described generically as "a fixed date, or linked
  to a reference variable". The actual displayed values are "Linked variable",
  "Directly extracted", and "Not configured".
- Responsibility label is "Counter Party" (two words) in the filter values, and
  "Third Party" rather than "3rd Party".
- The assignee-role filter offers "Initiator" — note this differs from the
  obligation form, which labels the same role "Initiator / Uploader".
- Added the four columns the previous version omitted entirely: Priority,
  Responsibility, Assignee, Reference variable — plus which columns are visible
  by default.
- Added the Enable row action (previously only Disable was listed).
- Added: default templates cannot be deleted or renamed; a template cannot be
  enabled while its category is disabled; names must be unique; field limits.
- "Key Features of Obligation Templates" was renamed and rewritten. It used
  the term "Anchor Variables", which is the internal API field name — the UI
  label is "Reference variable". It also repeated the automatic-sync claim;
  that now links to the overview instead of restating it (see the sync question
  on that page).
- Removed the claim that Delete preserves existing extracted data. Disable
  explicitly does; whether Delete does was not verifiable.

OPEN QUESTIONS:
1. RESPONSIBILITY "ANY". The filter config includes an "Any" value for
   templates, and the template form's helper text says "Used by AI to find
   obligations by the right party. Choose Any to keep it open-ended." So Any
   appears to be a template-level concept. A backend comment claims ANY is
   seed-only and "not accepted from API payloads", which the code contradicts.
   Listed in the filter table here; confirm it is selectable when creating a
   template.
2. DELETE VS EXTRACTED OBLIGATIONS. What happens to obligations already
   extracted from a template when that template is deleted? Not visible in the
   code. This is the question a customer will ask before clicking Delete.
3. SORTING AND SEARCH. The API allows sorting by name, created date and
   modified date, but which of these the UI exposes is unconfirmed, so sorting
   is not documented here.
4. WHO CAN MANAGE TEMPLATES. Undocumented — same open permissions question as
   on the settings page.
========================================================================== -->