Skip to main content
Ask for a native shared task list when you want checkboxes people can actually update. A plain Markdown checklist or a custom HTML checkbox may only be document content or local state.
Create a shared to-do Page for the launch: review onboarding, rehearse the demo, and choose the launch date. Leave owners unassigned. Keep it to one simple task list.

​
Work with a to-do list

Native task lists show a completion count and support checking tasks off, adding tasks inline, and opening a task’s title and notes editor. Assignment controls can be included where supported. Select a task to edit its details, then save. Changes use the record revision you began editing. If another person has changed it, a conflict should preserve your draft rather than silently overwrite the newer record.

​
Boards and timelines

The same task records can appear in list, board, and timeline views. A change to a record is shared across views using that record’s identity.
Add a board view of these same tasks. Do not create a second set of tasks.
Milestones can use a timeline. A timeline depends on the dates and fields supplied; creating the view does not invent a schedule or start background agent work.

​
More than tasks

Pages can combine supported records for decisions, risks, assumptions, milestones, updates, polls, and annotations.
Create a project tracker with tasks and milestones. Add a separate risk list with owners and mitigation notes, and keep unresolved decisions distinct from completed tasks.
Use only the sections the team needs. A simple to-do request does not require a decision log, risk register, or dashboard.

​
Saved state and document history

Shared records have their own revisions. Refreshing the Page does not turn them back into the original sample list. Restoring an older document revision does not undo task completion, votes, or other shared records. Historical inspection disables live actions. This also means removing a component from the layout is not the same operation as rolling back all its records.

​
Collaboration and access

The Page’s audience controls who can open it; available record actions still follow their permissions. Being able to change a shared task does not transfer authorship of the Page document. Use comments for discussion and Ask for changes when the Page’s author should change the document or layout.