Checklists in docs

Checklists inside docs are real task items — checkbox, assignee, and due date — not just bullet points. They're built for SOPs, onboarding plans, launch checklists, and runbooks where "who does what by when" matters.

Inserting a task list

• Slash menu → Task list inserts a checklist item ready to customize.

• Or select lines of text and convert them to a task list from the floating toolbar.

What each item supports

• Checkbox — check it off right in the doc; completion state saves with the document.

• Owner — assign any workspace member or team from the item's metadata toolbar.

• Due date — set a date on the item.

• Rich text — an item can contain formatted text, links, and inline code.

Task metadata toolbar

Selecting a task item reveals a small toolbar for assigning owner and due date — the same controls exist for checklist items created in PM tasks, so behavior is consistent across the product.

How this differs from linking a PM task

	Checklist item in a doc	Linked/embedded PM task
Lives in	The document itself	The PM module
Best for	Procedural steps inside a doc	Trackable work with its own workflow
Assignee	Document-level, simple	Full task ownership, states, estimates
Syncs to PM boards	No	Yes

Rule of thumb: if finishing the step should appear on someone's board, create or embed a PM task; if the step is part of following the document, use a checklist item.

Indenting and nesting

Task items nest under parent items for phases and sub-steps, and render with the same check styling in markdown export and on the public help center.