Prevent Users from Deleting Tasks

It’s very sad to see such difficulty in providing a simple feature that is more than essential in any business big or small, and instead the only response you have is to send generic messages to users saying you’re sad to see them leave.

Anyway, we encountered the same problem fortunately in the research stage, before implementing the program in our company, and after seeing so many complications over this topic we just decided not to use the program.

1 Like

Has this concern been addressed? We have a similar issue.

1 Like

It’s disappointing to not being able to restrict users from deleting tasks allocated to them. Tasks are just missing, and there seems to be no sanctity of work being managed on asana, as deletions cause the project to be lost in it’s tracks.

1 Like

I can’t understand why asana treat this extremelly important issue as if it is not. Tasks collaborators should not be able to delete tasks, neither to edit some very important fields like estimated time or project data custom fields. Really disappointing…


Currently, anyone that has edit permission can delete all tasks on a project. They can permanently delete tasks. This doesn’t make any sense whatsoever. This feature has been heavily discussed by clients for the past 4 years, yet nothing has been done in this regard. What is so hard about allowing project admins/owners to define only they can permanently delete tasks, and users can only delete them? This is such an easy solution that would safeguard the tracing and accountability of tasks. It’s not even the best solution, but at this point I only ask for something that doesn’t put me in a situation where anyone in a project can delete everything and i don’t even know what was written in those tasks

1 Like


I usually give my client the following examples: do people in your office go around and burn papers on desk all day? :thinking: Probably not, and Asana is like the digital version of real life, where we usually trust people… I know that feels weird sometimes, some companies just don’t trust people.

Then why don’t you comment there, but instead create a new thread? This is not something we encourage on the forum.

1 Like

Welcome to the Community Forum @Sérgio_Silva2!

I have merged your post into an existing feedback request thread. Please don’t forget to leave your vote there.

1 Like

For my workplace, it’s not about a lack of trust in people, it’s about safeguarding against human error and varied tech skills.

I can totally trust my co-worker isn’t going to set a piece of paper on fire, but that’s because they know how to use a lighter. I have coworkers who really struggle with this software and tech in general (in spite of ongoing learning and support), and they frequently make mistakes, such as accidentally deleting tasks.

I would love to say that all of my organization’s staff & clients are capable of using Asana without error, but we have a wildly varied level of tech skills. It’s still very, very helpful, which is why we continue to use it, but the reality is we need guard rails to support the different skill levels.


Understood, it makes sense. With Asana’s focus being more and more on Enterprise, this is the kind of feature Enterprise client expect (and they are asking about it on the forum) so I am hopeful things will change for the better!

Thanks for sharing


@Marie Project Members can also delete Sections, we have written some automations based on that and when sections are being deleted, its creating huge problem.

I too would like the ability to lock a task from it being deleted. I need my team to be able to edit and work on it, but I need to make sure the task itself is not deleted. That would be disastrous! There needs to be a 3rd level of permissions.

1 Like

last week the editor level was made available (previously there was only project administrator / for commenting) - maybe a good idea would be to create access without the ability to delete tasks? This would prevent important information from being deleted from projects to which a large group of users have access

1 Like

Hello @anon67472475,

yes correct the project permission „Editor“ is new.
As commenter people won‘t be able to delete tasks if that helps?
I have also merged your task into a product feedback request thread regarding preventing users from deleting tasks. Just scroll to the top of this thread to vote for it.

This is a lame answer

What’s taking so long?

Hello Andrea! This is true that as commenter people are not able to delete tasks but there are also unable to create and edit them and this is a real issue stopping the workflow.

1 Like

@Aleksandra_Albera correct and then when they are assigned a task they gain full functionality of that specific task

1 Like

This is a colorful analogy, but not a fair one, I think. It is not normal in any office to light fires at all, and therefore the possibility of colleagues burning my papers from my desktop is far-fetched. Still less likely is it that they would dig into my desk drawers and combust whole folders at a time. Most offices also have smoke detectors, and burning papers will leave many traces showing that something very abnormal has happened and needs to be fixed and prevented in the future.

Whereas, in using Asana, it is a routine activity to edit tasks, including bulk moves and other good-faith actions that as we know, can result in the destruction of user-created data in ways that take users by surprise. Large amounts of data can disappear with literally no evidence they are gone. No alarms go off. No user-accessible evidence is left. After 30 days, even much of the evidence that only Asana support can also see is also gone. (Right?) It is the perfect crime. :exploding_head:

I doubt if most of us fear malicious edits or deletion as the primary issue; we trust our coworkers to be reasonable and non-destructive. It’s just that with all the multi-homing, edit by moving (e.g. cleaning up a timeline), edit by sorting, wanting to tidy up umpteen ancient tasks and projects without proper tools for doing so, users have many reasons to do things that may accidentally destroy or corrupt data.


More and more, when we start a deployment with a client, we make sure they align with Asana’s philosophy: transparency and openness. Even if that philosophy seems to be evolving, the foundations are still deeply linked to “trust over constraint”.

1 Like

Can’t believe we are still waiting on this! Please implement it Asana. We cannot do organizational and project management without the ability to stop (specific) users from deleting tasks they did not create.