> **Source:** https://knowledge.leegality.com/deal-collaboration/Obligations/Settings/obligation-settings
> **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 Settings

> Obligation Settings is where you decide when the AI should read your contracts and pull obligations out of them, without anyone having to ask it to. These setti

Obligation Settings is where you decide when the AI should read your contracts and pull obligations out of them, without anyone having to ask it to. These settings apply to your whole organisation, so what you choose here affects every contract your team executes or uploads.

Extraction only ever runs on contracts that have reached **Executed**. What these settings control is whether it runs on its own at that point, and which contracts it covers. You can still trigger extraction by hand at any time, and you can always add an obligation yourself. See [Adding an Obligation](https://knowledge.leegality.com/deal-collaboration/Obligations/add-obligation).

If all four toggles are off, nothing is extracted automatically and every obligation in your organisation is created by hand.

## Opening Obligation Settings

1. Go to **Settings** and click **Obligations** in the sidebar.
2. Open the **Settings** tab.

## Extraction Triggers

<!-- ARCADE · P2 · The extraction toggles
     Show: switching each of the four toggles, with the hint text under each label readable.
     Call out: there is no Save button — each toggle saves on click.
-->

Four toggles control automatic extraction. All of them start off, so nothing is extracted automatically until someone turns them on.

| Toggle | What it does | Good to know |
| :--- | :--- | :--- |
| **Auto-extract from contracts executed from a Workflow** | This toggle extracts obligations from contracts that complete execution through a Deal Collaboration workflow. | This covers the usual path, where a contract is signed inside the product. Extraction starts as soon as the contract reaches **Executed**. |
| **Auto-extract from uploaded contracts outside a Workflow** | This toggle extracts obligations from contracts that you upload rather than execute in the product. | This is how you get obligations out of older contracts that were signed before you started using Deal Collaboration. |
| **Let users decide on extraction for non-workflow uploads** | This toggle lets people choose whether to extract obligations each time they upload a contract, individually or in bulk. | The choice appears as its own toggle on the upload screen. See [Choosing Extraction When You Upload](#choosing-extraction-when-you-upload). |
| **Skip auto-extraction for expired contracts** | This toggle leaves out contracts whose expiry date has already passed, so the AI only reads contracts that are still live. | Contracts with no expiry date, and those with perpetual or open-ended terms, are always processed. |

> **Info — Note**
>
> There is no Save button. Each toggle takes effect as soon as you click it, and the toggle itself is your confirmation. If a change cannot be saved, the toggle returns to its previous position and you are told why.

### Choosing Extraction When You Upload

When you upload contracts, the upload screen carries its own toggle, **Automatically extract obligations from the uploaded contracts**. It is on by default, so you can turn it off for a batch of contracts you do not want read.

Turning it on here also overrides the organisation setting for that upload, so you can extract from a particular batch even when automatic extraction is switched off for uploads generally.

### What Happens After a Trigger

Extraction runs in the background and never holds up the work that started it. Signing completes and uploads finish whether or not extraction succeeds, and a failure is recorded rather than shown to the person who uploaded.

Contracts are sent for extraction in batches of up to 100. When **Skip auto-extraction for expired contracts** is on and the expiry date cannot be worked out from the contract, the contract is still sent, and the expiry is checked before it is read.

Follow what happens next in [Obligations in the Processing Hub](https://knowledge.leegality.com/deal-collaboration/Obligations/obligations-in-processing-hub), which lists one row per contract and shows whether extraction is queued, running, finished or failed.

> **Caution — Important**
>
> Re-extracting a contract replaces the obligations already extracted from it. Anything a person edited or verified on those obligations is replaced along with them.

## Related Pages

- [What is an Obligation?](https://knowledge.leegality.com/deal-collaboration/Obligations/obligations-overview)
- [Obligation Library](https://knowledge.leegality.com/deal-collaboration/Obligations/Settings/obligation-library)
- [Managing Obligation Categories](https://knowledge.leegality.com/deal-collaboration/Obligations/Settings/obligation-categories)

<!-- ==================== POC REVIEW NOTES (not rendered) ====================
Verified against obligation/constants/settings.py,
obligation/controllers/settings.py, and the frontend slice
slices/obligation-settings/ (constants/obligation-settings-form-fields.js and
its README.md).

CONFIRMED CORRECT: the four Extraction Triggers toggle labels and their
descriptions were verbatim accurate in the previous version — they match the
frontend label/hint strings exactly. No wording changed. The old
"Draft — Needs Verification" caution has been removed on that basis.

ADDED: all four default to off; each toggle autosaves with no Save button and
rolls back on failure.

SECTIONS REMOVED — these did not exist:
1. "Default Reminders and Notifications" (Notify on Task Creation, Notify
   Before Deadline, Notify on TAT Breach, Default Repeat Reminders). The
   settings config has exactly four boolean fields — extract_executed_dc,
   extract_legacy_uploaded, allow_bulk_batch, only_active_contracts — and no
   notification defaults of any kind. There is no mechanism to pre-fill the
   Tasks & Notifications step from settings, so the claim that these defaults
   flow into new obligations and templates was also wrong. Reminder
   configuration is per-obligation and per-template only.
   -> If module-level notification defaults are planned, this section can come
      back once they ship.
2. "Permissions" table. Could not be verified. Obligation actions are gated by
   per-row permission flags (retry_allowed / discard_allowed /
   review_obligations_allowed on extraction jobs) and by a document-assignment
   entitlement check that scopes what a user can see, but the mapping from
   roles to those flags is not visible in either repo. The previous table's
   categories ("Obligation module Admins", "users with obligation edit access")
   do not correspond to anything found in the code.
   -> Needs the platform/entitlements owner. Worth its own section once
      confirmed, since permissions are currently undocumented everywhere.
3. "Limits". Unverifiable as written. The real documented limits found are:
   category name 50 chars / description 1,000; template name 100 chars /
   description 2,000; obligation name 100 / description 2,000; bulk actions
   capped at 100 obligations or jobs per request; repeat reminders limited to
   1/2/3/5/10 occurrences. Those are documented on the pages they belong to
   rather than collected here. The previous claims of "no fixed limit" on
   categories, templates and reference variables were not verifiable.

OPEN QUESTIONS:
1. TOGGLE 3 SEMANTICS. The UI label says "Let users decide on extraction for
   non-workflow uploads", but the underlying field is allow_bulk_batch and the
   extraction trigger treats it as a second gate that must ALSO be on before
   bulk uploads auto-extract (bulk requires extract_legacy_uploaded AND
   allow_bulk_batch). "Let users decide" and "additionally allow bulk" are not
   the same behaviour. This page follows the UI wording. Worth confirming
   which is intended — if the label is wrong it is a product copy bug.
2. EXPIRED-CONTRACT HANDLING. The hint says contracts with no expiry date are
   "always processed". In the code, a contract whose expiry cannot be
   determined locally is passed to the extraction service with a check_expiry
   flag so the service verifies expiry itself — meaning such a contract can
   still be skipped upstream. Confirm whether "always processed" is accurate
   from the user's point of view.
3. SETTINGS PERMISSIONS. Who can change these toggles is not documented.
========================================================================== -->