Overview
Checklist task dependencies let you decide the order in which checklist tasks are completed. A task that depends on other tasks stays locked until all of those tasks are completed, and then unlocks automatically.
This is useful when one step can only happen after another, for example verifying a new joiner's account access only once their email account and payroll access have been set up.
Permissions
- To set dependencies in a checklist template, you need the Manage Checklist Template permission on global.
- To set dependencies on a checklist that has already been created, you need the Manage Checklists permission.
No one can complete a locked task or override the lock, including admins and the checklist owner. More information on Checklist permissions can be found here.
How Checklist Task Dependencies Work
- Locked until ready: A task that depends on other tasks cannot be completed until every task it depends on is completed.
- Unlocks automatically: Once the final prerequisite task is completed, the dependent task automatically unlocks and becomes actionable.
- Due date on the unlock date: A dependent task’s expected duration begins counting from the day it unlocks, rather than the day the checklist starts (e.g., a 3-day task unlocking on Monday will be due on Thursday). If no expected duration is set, no due date is displayed.
- Notifications upon unlock: Assignees receive an email notification only once their task unlocks. No assignment or reminder emails are sent while a task is locked.
- Same-checklist scope: A task can depend on multiple prerequisite tasks, provided they all belong to the same checklist. Cross-checklist dependencies are not supported.
Task dependencies configured in a Checklist Template are automatically applied to every new checklist created from that template.