Help center
Open dashboard

Deleting Projects: How to Manage Dormant or Completed Projects

When to delete, when to archive instead, and exactly what happens when you do.

Atarim team Updated 29 Jul 2026 · 9 min read
Managing Projects
Atarim project actions menu with the delete project option
Before you start

Relevant for

  • Anyone tidying up a Projects screen
  • Administrators clearing out work that has genuinely finished

Required knowledge

  • An understanding of the difference between archiving and deleting.
  • Permission to delete projects.

Tools & resources needed

  • An Atarim workspace.
  • Certainty about what you are removing.

Deleting a project removes it and all its tasks and activity from your dashboard permanently. Atarim states it plainly in the dialog, and the wording is worth taking at face value: this action cannot be undone.

That makes the interesting question not “how do I delete a project” but “should I”. Most of the time the answer is no.

Archive First, Delete Rarely

Both actions free a project slot on your plan. Only one of them is reversible, which makes archiving the right default for anything you are not certain about.

ArchivingDeleting
Tasks and commentsKept in fullRemoved permanently
ReversibleYes, in two clicksNo
Frees a project slotYesYes
Client historyRetained for future referenceGone
ConfirmationA single confirmationTyping a generated number
Recommendation
If the only reason you are deleting is to free a slot, archive instead. It frees the same slot, keeps every client conversation, and takes two clicks to reverse.

Why Archiving Is Usually the Better Answer

Archiving is not a weaker version of deleting. It solves the same practical problems — a cluttered screen, a full plan — while keeping everything that makes a returning client easy to pick back up.

Benefit of archivingIn practice
It frees the same project slotIf your only reason for deleting is a full plan, archiving solves it identically — and costs nothing to reverse.
Nothing is lostTasks, comments, attachments, and the whole client conversation stay exactly as they were.
Restoring takes two clicksA project comes back from Archived Projects with its history intact, so a wrong call is not a permanent one.
Returning clients are easyWhen a client comes back eighteen months later, the record of what was agreed and why is still there.
The decision stops being riskyArchiving turns “should I remove this?” into a low-stakes question, so tidying actually gets done.
  1. Open the project’s kebab menu, the three vertical dots.
  2. Select Archive Project rather than Delete. Alternatively, bulk-select projects and choose Archive in the top bar.
  3. To reach archived projects later, open the Archive section from the top-right kebab menu on the Projects screen.
Archiving a single project
Archiving several projects at once
Recommendation
Make archiving the default and deletion the exception. Nearly every reason people reach for delete — the project is finished, the client has gone quiet, the list is too long, the plan is full — is better served by archiving, and none of them are worth a permanent loss.

When Deleting Is the Right Call

There are genuine reasons to delete. They are narrower than most people assume.

SituationDelete?
A project created by mistake, or a duplicateYes — there is no history worth keeping.
A test or demo projectYes, once it has served its purpose.
A client has asked you to remove their dataYes — this is what deletion is for.
A completed client projectNo. Archive it — clients come back, and the history is the record.
You have hit your project limitNo. Archiving frees the same slot without losing anything.
A dormant project you might reviveNo. That is precisely what archiving is for.
The mistake people regret
Deleting a completed client project. The feedback thread on a site you built two years ago is often the only record of why a decision was made. Archiving keeps it and costs nothing.

What Deletion Removes

Worth being clear on the scope before you confirm, because it goes further than the project card.

WhatOutcome
The projectRemoved from your dashboard permanently.
Its tasksRemoved, including anything still open.
Comments and feedbackRemoved, including your client’s own words.
Its activityRemoved from your dashboard.
Your project slotReleased back to your plan.
The website itselfUntouched. Deleting a project in Atarim does not affect the live site.
Note
If the site was connected with the WordPress plugin, deleting the project in Atarim does not uninstall or disable anything on the site. That is a separate step on the site itself.

Deleting a Project

The confirmation is deliberately awkward. Atarim generates a random four-digit number and will not proceed until you type it, which makes an accidental deletion effectively impossible.

  1. Go to Projects and find the project.
  2. Open its Project Actions menu and select Delete. A dialog opens warning that deleting removes the project and all its tasks and activity permanently, and that the action cannot be undone.
  3. Check the project named in the dialog is the one you mean.
  4. Read the four-digit number shown in bold. It is generated fresh each time, so it cannot be muscle-memoried.
  5. Type that number into the field below it. The confirm button stays disabled until it matches exactly.
  6. Confirm, or select Cancel to back out.
Open Dev Stack folder view with the ⋮ menu expanded on a project card, showing the Project Actions list with Delete highlighted in red.
Tip
Treat the number as the moment to stop and think rather than an obstacle. It is the last point at which archiving is still an option.

Deleting Several Projects at Once

The same dialog handles a batch, and it lists every project by name so you can check the selection before committing to it.

  1. On the Projects screen, hover a project card to reveal its checkbox.
  2. Select every project you intend to delete.
  3. Apply Delete to the selection. The dialog states how many projects are about to be deleted, followed by the full list of names.
  4. Read the list. This is the only point at which a wrong selection is visible — every name shown is about to be removed permanently.
  5. Type the four-digit number and confirm.
Every project in the selection is named — read the list before confirming
One number covers the whole batch
The confirmation is no harder for twenty projects than for one. The list of names is the real safeguard, so read it rather than skipping to the field. If you are clearing out at volume, select the same batch and archive it instead — same slots freed, and a wrong selection is recoverable.

Deleting a Folder

Folders behave differently, and this is where the real risk sits. Deleting a folder does not have to delete its projects — but the dialog offers to, and the options are easy to tick past.

  1. Open the folder’s actions and select Delete. The dialog asks whether you are sure, with two options beneath.
  2. Decide what happens to the projects inside. Archive projects with folder archives them; Delete projects with folder removes them permanently. Leave both unticked and the projects simply return to your main Projects view.
  3. Read the confirmation line. It changes to match your choice, so the consequence is spelled out before you confirm.
  4. Confirm.
Option to delete Folder
Deleting a folder removes only the folder — projects and tasks are kept. To act on the contents as well, select Archive projects with folder or Delete projects with folder before confirming with Delete Folder.
The most destructive action on the Projects screen
Deleting a folder with Delete projects with folder ticked removes every project in it permanently, in one confirmation. If you only want to ungroup the projects, leave both options unticked. Learn More About Managing Folders

If You Delete Something by Mistake

The dialog names a route, and it is worth knowing before you need it — but it is a hope rather than a guarantee.

  1. Contact support immediately at support@atarim.io. Atarim’s own wording is that they may have a backup to restore it, although restoration is not guaranteed.
  2. Include the project name and roughly when it was deleted. The more precise you are, the better the chance of finding it.
  3. Do not wait. Speed matters, because backups do not last indefinitely.
Do not plan around recovery
“Support can restore it” is not a safety net you should rely on. Archive anything you might want back, and treat deletion as final.

Benefits of Managing Dormant Projects Well

BenefitIn practice
A Projects screen you can scanFinished work is out of the way, so the list shows what is actually live.
Slots go furtherClearing dormant work is nearly always cheaper than upgrading a plan.
Client history survivesArchiving keeps the record of what was agreed and why, for whenever they come back.
Genuine data removal when it is asked forDeletion exists for the cases where a client wants their data gone.
Fewer regretsA habit of archiving means a wrong decision is two clicks from being reversed.

Example Use Cases

SituationWhat to do
You added a site to the wrong workspaceDelete it and add it again in the right one — there is no history to lose.
A client relationship has endedArchive. If they later ask for their data to be removed, delete it then.
A demo project from a sales callDelete once it is no longer needed.
Annual clear-outSort by Oldest Projects First, select the finished work, and archive it in one action.
Winding up a client folderArchive the projects with the folder rather than deleting them, unless the client has asked otherwise.
A duplicate created by accidentDelete the duplicate, keeping the one with the feedback on it.

Known Limitations

  • Deletion cannot be undone from the dashboard. Support may hold a backup, but restoration is not guaranteed.
  • Deleting a project removes its tasks, comments, and activity along with it.
  • Deleting a folder can delete every project inside it if that option is ticked.
  • Deletion is permission-based, so the option may not appear for every role.
  • There is no bin or recovery area in the dashboard — unlike archiving, which has its own screen.
  • One confirmation covers a whole batch. Deleting twenty projects is no harder than deleting one, so the list of names is the only safeguard.

FAQs

Can I undo a deletion?

Not from your dashboard. Contact support@atarim.io as soon as you can — a backup may exist, though restoration is not guaranteed.

Why do I have to type a number?

To make accidental deletion effectively impossible. The number is generated fresh each time, so the step cannot become automatic.

Does deleting a project affect my live website?

No. It removes the project from Atarim only. The site itself is untouched.

Should I delete or archive a finished client project?

Archive. Both free a project slot, but archiving keeps the tasks and client conversations in case the client returns.

Does deleting a folder delete its projects?

Only if you tick that option. Left unticked, the projects return to your main Projects view.

Is there a bin I can recover from?

No. Archived projects have their own screen; deleted ones are gone.

Can I delete several projects at once?

Yes. Select them on the Projects screen and apply Delete. The dialog names every project in the batch and asks for one confirmation number, so read the list carefully.

Is bulk archiving available too?

Yes, and it is the better option for a clear-out — it frees the same slots and a wrong selection can be undone.

Common issues

  • The confirm button stays disabled — the number must match exactly. Check you are reading the current one; it regenerates each time the dialog opens.
  • Delete is missing from the actions menu — your role does not carry the permission. An administrator can grant it.
  • A project vanished and you did not delete it — check Archived Projects first, then your workspace and filters. Archiving is far more common than deletion.
  • You deleted a folder and its projects went too — the delete option was ticked. Contact support quickly; there may be a backup.
  • You deleted more than you meant to — the dialog lists every project in a batch before confirming. Contact support immediately with the names.
  • You want the project back — email support@atarim.io as soon as possible with the name and approximate date.
  • You only wanted to free a slot — archiving does that too, and keeps everything. Use it next time.

Conclusion

Deletion exists for mistakes, duplicates, and genuine data-removal requests. For everything else — finished work, dormant accounts, a full project list — archiving does the same job for your dashboard while keeping the history that makes a returning client easy to pick back up.

Tips & best practices

  • Archive by default. Delete only for mistakes, duplicates, and data-removal requests.
  • Treat the four-digit number as a moment to reconsider, not an obstacle to get past.
  • Read the folder checkboxes every time — they decide whether the projects inside survive.
  • Never plan around support being able to restore something. Archive anything you might want back.
  • Do an annual clear-out by sorting oldest first and archiving in bulk — not deleting in bulk.
  • Read the list of names in a batch deletion. One number confirms the lot.
  • If a client asks for their data to be removed, delete — that is what it is for.

Related articles