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

---
# Managing Obligations

> Manage is the working list of every obligation across your contracts. Use it to find an obligation, open it, and act on it, either one at a time or in bulk.

Manage is the working list of every obligation across your contracts. Use it to find an obligation, open it, and act on it, either one at a time or in bulk.

## Opening the Obligations List

1. In the sidebar, click **Obligations**.
2. Click **Manage** to see the complete list of obligations.

## Columns

<!-- ARCADE · P3 · Configure Columns
     Show: opening Configure Columns and turning on Category and Source.
-->

The list always shows the **Obligation name**. You choose the rest through **Configure Columns**, and Status, Document Name, Next Due Date, Priority, Responsibility and Assignee are shown to begin with.

| Column | What it shows |
| :--- | :--- |
| **Obligation name** | The obligation. Always shown, and cannot be hidden. Click it to open the obligation. |
| **Status** | Active, Completed, or Expired. |
| **Document Name** | The contract the obligation belongs to. |
| **Deal Name** | The deal the contract sits in. |
| **Counterparty** | The other party to the contract. |
| **Category** | The obligation's [category](https://knowledge.leegality.com/deal-collaboration/Obligations/Settings/obligation-categories). |
| **Next Due Date** | The next occurrence's due date. Click the column heading to sort on it. |
| **Frequency** | One-time or Repeating. |
| **Priority** | Critical, High, Medium, or Low. |
| **Responsibility** | Us, Counter Party, or Third Party. |
| **Assignee** | Who the obligation is assigned to. |
| **Source** | AI-Assisted, Verified, or Manual. |
| **Date Created** | When the obligation was created. Click the column heading to sort on it. |

> **Info**
>
> An obligation carrying a conflict also shows a **Conflict** badge against its name.

## Searching and Filtering

Use the search box to find an obligation by name. It also matches the document, deal and counterparty.

Use **Filters** to narrow the list. You can filter by:

- **Status**, **Priority**, **Category**, **Responsibility** and **Source**.
- **Frequency**, to separate one-time obligations from repeating ones.
- **Due Date**, to separate obligations that have a due date from those that do not.
- **Due Date Range** and **Date Created**, using a relative range such as the next few weeks, or your own dates.
- **Tasks**, to find obligations with a task configured, with a task conflict, or with no tasks at all.
- **Survives Termination**.
- **Document Name**, **Deal Name** or **Counterparty**, to narrow to one contract, deal or party.

> **Tip — Finding what needs attention**
>
> Filter **Tasks** by **Task Conflict** to see obligations whose due date or task setup needs review. Filter **Due Date** by **No Due Date** to find obligations that were never given one.

Before any obligations exist, the list reads *No obligations added yet. Create your first obligation to get started.*

## Finding and Fixing Conflicts {#finding-and-fixing-conflicts}

A conflict means an obligation's due date or task setup can no longer be trusted, so the module flags it instead of acting on stale information. See [Conflicts](https://knowledge.leegality.com/deal-collaboration/Obligations/obligations-overview#conflicts) for what each type means.

To work through them:

1. Filter **Tasks** by **Task Conflict**. The list then shows only obligations that need attention.
2. Click an obligation with a **Conflict** badge. The drawer opens and lists every conflict on it, under a heading that counts them, such as **2 conflicts detected**. Each one has a title and an explanation of what changed.
3. Click **Fix Conflict**. The obligation opens in edit mode.
4. Correct whatever the conflict describes. A changed reference date usually needs the due date confirming. A missed task creation window usually needs the task settings adjusting.
5. Click **Save**.

The conflicts that your edit resolves are cleared. Any that remain stay on the obligation, so one with several conflicts may need more than one pass.

> **Info — Note**
>
> If an obligation has a conflict, its tasks may not have been created at all. The obligation itself will say so: *Tasks have not been created due to conflict. To resolve, edit the obligation and configure task settings.*

## Actions

<!-- ARCADE · P3 · Edit a due date that has a task
     Show: changing the due date on an obligation with an active task, and the Keep existing task / Cancel and reschedule choice.
-->

<!-- ARCADE · P2 · Complete then reopen
     Show: Mark as Complete with its warning, then Reopen on the same obligation.
     Call out: the point is that tasks are NOT restored on reopen.
-->

Click an obligation to open it in a side drawer. The drawer shows its full detail, including the source clause, its schedule, its tasks, and any conflicts. Each obligation has its own address, so you can share a link to one.

Act on an obligation from the drawer, or from the actions on its row.

| Action | What it does | Good to know |
| :--- | :--- | :--- |
| **Edit** | This option changes the obligation's details, schedule, or task setup. | If you change the due date on a one-time obligation that already has an active task, you are asked to either **Keep existing task** or **Cancel and reschedule**. |
| **Verify** | This option confirms an AI-extracted obligation. | This action appears only on AI-extracted obligations. The source changes from AI-Assisted to Verified. |
| **Fix Conflict** | This option opens the obligation so that you can clear a conflict. | The obligation opens in edit mode. There is no separate conflict screen. |
| **View Task** | This option opens the task that the obligation generated. | This action appears only when a task exists. |
| **Create Task** | This option adds a task to an obligation that does not have one. | The obligation needs a due date before a task can be created. |
| **Add Assignee** | This option assigns another user to the obligation. | The assignee receives task assignments and reminders. |
| **Send Reminder** | This option sends a reminder to recipients that you choose. | You can add a note to the reminder. |
| **Mark as Complete** | This option closes the obligation as met. | This closes all open and future tasks. You can add remarks and attachments. |
| **Mark as Expired** | This option closes the obligation as no longer applicable. | You can add remarks and attachments. |
| **Reopen** | This option returns a closed obligation to Active. | Tasks are not recreated. Reopening is tracked for audit purposes. |
| **Delete** | This option removes the obligation. | Deleting is permanent. |

Which actions you see depends on the state of the obligation and on your permissions. A completed obligation offers **Reopen** rather than **Mark as Complete**, and **Verify** appears only on an AI-extracted obligation.

> **Caution — Important**
>
> Marking an obligation complete closes all its open and future tasks. You can reopen the obligation afterwards, but its tasks are not recreated. To start tracking it again, edit the obligation and turn task creation back on.

### Acting on Several Obligations at Once

<!-- ARCADE · P2 · Bulk actions
     Show: selecting three AI-extracted obligations, using Verify, then opening the overflow menu.
     Call out: show a greyed-out action and why — e.g. Reopen disabled while an Active row is selected.
-->

Select obligations with the checkboxes to open the bulk action bar.

- **Verify** and **Add Assignee** sit on the bar itself.
- **Send Reminder**, **Mark as Complete**, **Mark as Expired**, **Reopen** and **Delete** are in the overflow menu.

You can act on up to 100 obligations at a time. Changing a filter keeps your selection. Navigating away clears it.

**When an action is unavailable.** A bulk action only applies where it makes sense for every obligation you have selected, so some become unavailable depending on the mix.

| Action | Needs |
| :--- | :--- |
| **Verify** | Every selected obligation to be AI-extracted. |
| **Mark as Complete** | No selected obligation to be completed already. |
| **Mark as Expired** | No selected obligation to be completed or expired already. |
| **Reopen** | Every selected obligation to be closed. It is unavailable while any is still active. |

> **Info — Note**
>
> If your access is limited to the documents assigned to you, this list shows obligations on those documents rather than the whole organisation.

## Related Pages

- [What is an Obligation?](https://knowledge.leegality.com/deal-collaboration/Obligations/obligations-overview)
- [Adding an Obligation](https://knowledge.leegality.com/deal-collaboration/Obligations/add-obligation)
- [Obligations Dashboard](https://knowledge.leegality.com/deal-collaboration/Obligations/obligations-dashboard)
- [Obligations in the Processing Hub](https://knowledge.leegality.com/deal-collaboration/Obligations/obligations-in-processing-hub)

<!-- ==================== POC REVIEW NOTES (not rendered) ====================
NEW PAGE. The obligations listing had no documentation at all, despite being
the module's primary working screen and the destination that add-obligation
and obligations-dashboard both point users to ("Go to Obligations > Manage").

Written against the shipped frontend slice
slices/obligations-listing/ (its README.md, constants/obligations-listing-
columns.js, -actions-list.js, -bulk-actions.js) plus the backend listing filter
config (obligation/constants/filters/listing_configs.py) and the bulk-action
constants in obligation/constants/obligation.py.

SIDEBAR: added at position 3, which shifted add-obligation from 3 to 4 and
obligations-in-processing-hub from 4 to 5. Reading order is now:
What is an Obligation -> Dashboard -> Manage -> Adding -> Processing Hub.

ANSWERS A PREVIOUSLY OPEN QUESTION: the edit-with-active-task prompt (POC item
22) is documented here — the options are "Keep existing task" and "Cancel and
reschedule". Note a naming discrepancy for engineering: the backend constants
are EXISTING_TASK_ACTION_CANCEL / _RETAIN, while the listing README describes
the payload values as RETAIN / REPLACE. The user-facing labels are what this
page uses, so the docs are unaffected, but one of those two is stale.

OPEN QUESTIONS:
1. ROW ACTION AVAILABILITY. Every row action is gated by a backend-supplied
   row_actions map (can_edit, can_verify, can_delete, can_reopen, and so on),
   and the frontend defaults a missing flag to "allowed". This page therefore
   says only that availability "depends on the obligation's state and on your
   permissions". A precise matrix needs the rules behind those flags — part of
   the module-wide permissions gap (POC item 14).
2. PAGINATION. The slice loads more rows as you scroll rather than paging, with
   a store default of 5 rows per fetch. That page size looks like an internal
   fetch size rather than anything a user sees, so this page describes neither.
   Confirm what the user actually experiences — infinite scroll, or pages.
3. ASSIGNEE FILTER. The backend deliberately EXCLUDES the "Assignee (by user)"
   filter from the global listing config while keeping it for the
   document-scoped listing. So Manage cannot be filtered by assignee even
   though Assignee is a column. Intended, or an oversight? It is a fairly
   obvious thing for a user to want, and the Dashboard's "My Active
   Obligations" tile does filter by assignee internally.
4. DELETE. What deleting an obligation does to its tasks and to any audit
   history is not described in the code. Not documented here.
5. CREATE TASK ON AN EXISTING OBLIGATION. Offered as a row action. Whether it
   opens the same Tasks & Notifications step as the add flow, or a smaller
   dialog, is unconfirmed.
6. DRAWER DEEP LINKS. Each obligation has its own URL
   (/obligations/manage/:id). This page says such a link can be shared; confirm
   that a recipient without access degrades gracefully.
7. ARCADE. No walkthrough or screenshot yet. This is the module's main screen,
   so it likely deserves both — a filtered-list walkthrough and a bulk-action
   one.
========================================================================== -->