Tasks and subtasks

Subtasks nest one level deep. A task has one assignee and any number of labels.

Details

A concept in Stackly maps to one thing you can see on a board, so the words here match the labels in the app.
Permissions follow the container: a person who can see a project sees every task in it.
Archived items stay searchable and can be restored by an Admin.
Names are not unique, so two tasks or two projects can share a title without clashing.
Automations can read these concepts, and they appear in the API under the same names.
Changing a concept for one project does not change it for the others in the workspace.
The activity history records who changed what, and keeps entries for as long as the plan allows.
The Free plan keeps the default behaviour; paid plans unlock the settings that change it.
A concept in Stackly maps to one thing you can see on a board, so the words here match the labels in the app. (Tasks and subtasks, note 2.)
Permissions follow the container: a person who can see a project sees every task in it. (Tasks and subtasks, note 2.)
Archived items stay searchable and can be restored by an Admin. (Tasks and subtasks, note 2.)
Names are not unique, so two tasks or two projects can share a title without clashing. (Tasks and subtasks, note 2.)
Automations can read these concepts, and they appear in the API under the same names. (Tasks and subtasks, note 2.)

Every plan includes the Stackly API, so the steps on this page work on Free, Pro and Business.