# Confirmation when the Delete key is hit on a table row

**URL:** <https://connect.superhuman.com/t/confirmation-when-the-delete-key-is-hit-on-a-table-row/42431>\
**Category:** Product Feedback\
**Created:** [August 28, 2023, 12:48am UTC](https://connect.superhuman.com/t/confirmation-when-the-delete-key-is-hit-on-a-table-row/42431 "2023-08-28T00:48:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![LxAU](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/lxau/32/36719_2.png) [@LxAU](https://connect.superhuman.com/u/LxAU)\
**Post date:** [August 28, 2023, 12:48am UTC](https://connect.superhuman.com/t/confirmation-when-the-delete-key-is-hit-on-a-table-row/42431/1 "2023-08-28T00:48:01Z")

</div>

Today, while I thought I had Outlook focused, I hit my Delete key with the intention of deleting an email. I actually had Coda focused on a table though, and because I had grouping enabled, I deleted 25 table rows as a result.

Luckily, I noticed this and Ctrl+Z got them all back. However, if I hadn’t noticed the deletion in that moment, the data might not have been recoverable—and I’ve also since found (and had to manually re-enter) some missing groups I’m sure I’ve previously entered.

Obviously the main problem here was user error, but the fact that 25-ish rows can be deleted with a single keystroke (and no ability to enable confirmation) seems like an unfortunate UX.

I’d love a setting along the lines of “ask for confirmation when deleting table rows” and/or “ask for confirmation when deleting multiple table/rows”.

I can’t justify a Team plan at this time to lock table row deletions.

---

<div class="post-metadata">

**Author:** ![Ian\_Nicholson](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/ian_nicholson/32/7561_2.png) [@Ian\_Nicholson](https://connect.superhuman.com/u/Ian_Nicholson)\
**Post date:** [September 1, 2023, 4:06am UTC](https://connect.superhuman.com/t/confirmation-when-the-delete-key-is-hit-on-a-table-row/42431/2 "2023-09-01T04:06:01Z")

</div>

Agreed! Way too easy to delete something and not catch it.

---

<div class="post-metadata">

**Author:** ![Lisa\_Doucet](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/lisa_doucet/32/29769_2.png) [@Lisa\_Doucet](https://connect.superhuman.com/u/Lisa_Doucet)\
**Post date:** [September 12, 2023, 5:59pm UTC](https://connect.superhuman.com/t/confirmation-when-the-delete-key-is-hit-on-a-table-row/42431/3 "2023-09-12T17:59:06Z")

</div>

This is a great suggestion !

---

<div class="post-metadata">

**Author:** ![Cooper\_Mayne](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/cooper_mayne/32/38742_2.png) [@Cooper\_Mayne](https://connect.superhuman.com/u/Cooper_Mayne)\
**Post date:** [November 9, 2023, 12:47am UTC](https://connect.superhuman.com/t/confirmation-when-the-delete-key-is-hit-on-a-table-row/42431/4 "2023-11-09T00:47:00Z")

</div>

Very much agree with this!