Skip to main content
Field definitions, task types, and the permission rules that govern each, for the Tasks board.

Fields on a custom task

The New Task drawer creates a Custom task with these fields: 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:

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.

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.
Last modified on September 22, 2026