Archive and trash
Two different ways to clear finished work out of sight. Archiving hides a task without deleting it, so you can bring it back at any time. The trash holds tasks and projects you deleted, keeps them for 30 days so you can restore them, and lets you delete them for good. Both keep working offline and stay in sync across your devices.
Use the archive for tasks you have finished but want to keep as a record. Use delete (which sends items to the trash) for tasks and projects you no longer need. See "Projects and lists" for how projects and boards are organized.
Archive
Archiving takes a task out of the active lists without deleting it. The task keeps everything — status, dates, checklist, subtasks — and can be restored to its list whenever you want. Archiving a task also archives its subtasks.
- 1Open the task menu on the card and choose "Archive".
- 2To clear finished work in one go, use "Archive completed": it archives the completed (done) cards in the current view.
- 3A list (column) menu also offers "Archive all cards" to clear the whole column at once.
- 4To review archived tasks, use "Show archived"; use "Hide archived" to hide them again.
- 5With archived tasks visible, open a task menu and choose "Unarchive" to bring it back to its list.
Trash
When you delete a task or a project, it does not vanish: it goes to the trash. From there you can restore it or delete it permanently. Deleting a project sends its tasks to the trash along with it.
Deleting a task never asks for a blocking confirmation: the card leaves the view right away and a toast offers "Undo" for a few seconds. If you miss the toast, the trash is the safety net.
- 1Open the trash from the Tasks module to see the deleted projects and tasks, in their own sections.
- 2Click "Restore" on an item to bring it back.
- 3Click "Delete forever" on an item to remove it permanently.
- 4To clear everything at once, click "Empty trash" and confirm.
Offline and across devices
Archiving, deleting, restoring and unarchiving all work without a connection. Every change is queued durably on the device — it survives reloading the page and even closing the browser — and syncs to your account automatically as soon as you are back online.
The other direction is covered too: changes made on another device (or by a collaborator on a shared project) show up on their own, without refreshing. On networks that block real-time connections, the module quietly falls back to periodic checks, so everything still catches up.