There is not a role that allows team members to create and modify tasks in a project but restricts them from being able to delete anything. Has anyone needed this level of access and found a workaround?
Commenting to keep this visible. I’ve gone through the six years of comments. Based on the apparent need for a role that will allow users to add and edit tasks in a project but now allow them to delete tasks or projects doesn’t seem like it should be that hard to create. I wasn’t able to find a reliable work around in the six years of comments I poured through but maybe I missed something?
We would like to see this implemented as well. The fact that any member can delete a board or card is ridiculous. The ability to recover and restore the board to the pre state is impossible after this damage has been done. Seems like an easy fix that has gone unnoticed for years.
1 Like
Welcome to the forum, @Todd_Thams! If you haven’t already, make sure you upvote the request. In the meantime, there are some things you can do to prevent accidental deletion of both projects and tasks (make people commenters/viewers on projects, prevent non-project admins from multi-homing tasks, etc.). You also can restore deleted tasks and projects for 30 days.
Hi Stephen_Li,
Thanks for the welcome. Can you expand on your message.
We are currently on the Advanced Subscription. Our levels are Admin and Member. We just tested yesterday and a member can delete the column and all cards/tasks. You are correct that we can restore, but it doesn’t restore to the same as before. Image 7 columns and 100 tasks… We would have to rebuild the entire board.
This seems like a really simple thing to build and a reasonable request to prevent data loss. I mean restricting the ability to delete anything is common.
I can so many scenarios with perhaps a disgruntled employee or contractor causing harm that could have easily been prevented by a setting.
If I’m missing something, please share.
Thanks
Todd
This would be at the individual project (board) level, see this article for a high-level overview and this one for a more detailed breakdown (esp. the chart at the bottom showing which project access levels can do what).
It’s not a total solution (definitely still upvote this topic) but it does give you some guardrails (e.g., in our org, our default access level for projects is commenter, so people can neither delete projects nor tasks unless directly assigned to them).
RE: restoration from deletion, I’m not totally sure what you mean, as restoring a project or task should return it exactly as it was immediately before deletion (this has been my experience, at least, including for projects with significantly more than 100 tasks).
2 Likes
Upvote & share so its more public and hopefully inspires faster aciton: https://x.com/HempCollect/status/1911872292604530997
1 Like