Archiving a project hides it from the sidebar and search without deleting anything, which makes it the right move for finished work you might need to reference later. This article covers archiving, restoring, and the difference between archiving and deleting.

Archived projects disappear from the team's project list and from ⌘K search results by default, but every task, file, and status update stays exactly as it was.

Restoring puts the project back in its original team with its members, tasks, and history untouched.

Archiving a project has no effect on time already logged against it — timesheets and time reports still include those hours, and billable rates stay attached to the project's tasks. This matters for client-services teams that archive a project the day it wraps but still need to run a final invoice from it weeks later.

Deleting a project, by contrast, removes its time entries along with everything else once the 30-day recovery window closes. Export any time reports or invoices you need before deleting, not after.

Archiving is a project-level action that affects everyone with access to it. If you personally no longer need to see a project but it's still active for the rest of the team, remove yourself as a member instead — open Project settings → Members and click Leave project. The project stays exactly as it was for everyone else.

An archived project can still be found through direct links and mentions — archiving only removes it from the default project list and search, not from the workspace entirely.

Tip: When in doubt, archive instead of delete. You can always delete an archived project later, but you can't undo a deletion.