Sub-tasks give you the ability to break large tasks into smaller, more manageable, pieces. They can be nested under each task from the Workflows page.
An example of a Task with sub-tasks could be how a new hire can follow the internal process for ordering additional hardware - i) confirming within guidelines, ii) submitting a request to manager, iii) sending the receipt to the accounts team and iv) tagging hardware with serial numbers.
How to create Sub-tasks?
Navigate to the Workflows page in your Sapling Admin, and create a new (or modify an existing) task.
Once sub-tasks are added to a task, they will be visible on the task when assigned as part of a Workflow (for example new hire onboarding).
The due date of sub-tasks is at the Task level and sub-task completion is tracked in the task history. It’s important to note that sub-tasks are not shown in the email notifications at this time, so your team must be logged into Sapling to see the sub-tasks.
Who can complete Sub-tasks?
When a team members opens a task with sub-tasks, they will see them listed and be able to complete in any order (Sapling doesn’t require a sequence to be followed).
Employees can see and complete their own tasks and Managers can see and complete their own tasks and tasks of their reports (if using Sapling’s default permission structure).
Typically Admins and Super Admins can see and complete the tasks of everyone.