> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dualentry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Task Fields, Types, and Permissions

> Reference for DualEntry Tasks: custom task fields, the five system-generated task types, and who can create, edit, and complete each.

Field definitions, task types, and the permission rules that govern each, for the [Tasks](./index) board.

## Fields on a custom task

The New Task drawer creates a Custom task with these fields:

| Field       | Type | Required | Default | Description                                 |
| ----------- | ---- | -------- | ------- | ------------------------------------------- |
| Title       | Text | Yes      | None    | Short name shown on the card.               |
| Description | Text | Yes      | None    | Longer detail shown when you open the task. |
| Status      | Enum | No       | To Do   | The lane the task starts in.                |
| Due date    | Date | No       | None    | When the task is due.                       |
| Preparer    | User | No       | None    | The person doing the work.                  |
| Reviewer    | User | No       | None    | The person who signs off.                   |

A custom task created through the New Task drawer always applies across your whole organization; the drawer doesn't offer a way to scope it to one company.

## System-generated task types

DualEntry creates a task automatically for each of five conditions, independent of anything a user creates:

| Type                 | Created when                                                                                                                                 | Cleared by                                                                                                                        |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| **Bank Match**       | A connected account has unmatched bank transactions.                                                                                         | Matching the account's remaining transactions in [Bank Match](../../core-financials/close-management/bank-match/index).           |
| **Bank Connection**  | A connection needs reconnecting, hasn't synced recently, has new accounts to review, or setup is incomplete.                                 | Resolving the connection in bank connection settings.                                                                             |
| **Anomaly Detector** | Your organization has one or more open, high-confidence anomaly alerts. One card per alert type: high value, field difference, or duplicate. | Reviewing or dismissing the underlying alerts in [Anomaly Detection](../anomaly-detection/index), or turning that alert type off. |
| **Close Checklist**  | A close checklist is created. One card per checklist, kept in sync with it.                                                                  | Completing the checklist's own tasks. Status derivation is below.                                                                 |
| **Agent Run**        | A scheduled agent finishes a run. Visible only to the agent's owner.                                                                         | Marking it reviewed, from the card or from the agent's chat.                                                                      |

### Close Checklist card status derivation

A Close Checklist card's status is calculated from the checklist every time the checklist changes; it is not set directly.

| Checklist state                        | Card status |
| -------------------------------------- | ----------- |
| No tasks complete yet                  | To Do       |
| Some tasks complete, not all           | In Progress |
| Every active task complete or archived | Done        |
| Checklist itself archived              | Expired     |

## Who can create, edit, and complete a task

Opening Tasks and creating a custom task doesn't require a dedicated permission: any signed-in member of your organization can do both. If your access is restricted to specific companies, you only see tasks that are either unscoped or assigned to one of your companies.

Completing a task follows the people assigned to it, not a permission check:

* A custom task with no preparer or reviewer set can be moved to any status by anyone.
* Once a preparer and reviewer are both set, the preparer can move the task to any status except Done. Only the reviewer can mark it Done.
* Turning on **Enforce separation of duties** on a task requires the preparer and reviewer to be two different people.

The same "only the reviewer can mark it Done" rule applies to a system task if it happens to have a reviewer set on it, though the task types above don't expose assignment fields in their own UI. In practice, the way to close out a system task is to resolve what it's pointing at (match the transaction, review the alert, finish the checklist item) and let DualEntry move the card, or drag it to Dismissed if you don't need to act on it.

## Related reading

* [Tasks: To-Dos, Agent Runs, and Close Work in One Board](./index)
* [How to Schedule an Agent from Tasks](./schedule-an-agent-from-tasks)
* [How to Manage Close Workflows with Tasks](./manage-close-workflows-with-tasks)
* [Scheduled Agents Reference](../accounting-intelligence/scheduled-agents)