Hard Delete Option in Command Menu

[n2ojim]

Scope & Context

We want to provide users with a faster way to permanently delete records directly from the interface, without having to first send them to the trash/recycle bin and then empty it manually. This is particularly useful for quickly cleaning up test data or mistakes.

Current behavior

Currently, when a user wants to delete a record via the command menu (Ctrl+K / Cmd+K) or the record options, there is only a "Delete" option. This action performs a soft delete (moving the record to the trash). To permanently delete the record, the user must navigate away, find the deleted records view, and delete it again from there.

Expected behavior

We want to add a new option called "Permanently delete [Record Name]" directly in the command menu (Ctrl+K / Cmd+K) and in the table/record option menus.
This option should be placed immediately below the standard "Delete" option. Selecting it should trigger a hard delete of the record, completely removing it from the database after a confirmation prompt (to prevent accidental data loss).

Technical inputs

• Update the Command Menu (Ctrl+K) and table row dropdown components to include a new MenuItem for "Permanently delete".
• Implement a confirmation modal (Dialog) that appears when this option is clicked, warning the user that the action is irreversible.
• Trigger a hard delete GraphQL mutation (e.g., destroy or hardDeleteRecord) instead of the standard soft delete when confirmed.
• Ensure proper permissions checking, as hard deleting might require higher privileges than soft deleting.

[Amresh-01]

can i work on this issue
Please assingn this issue to me

[singhharsh1708]

Hi! I'd like to take this one. 👋

Proposed approach (reusing existing infra):

• The hard-delete plumbing already exists — useDestroyManyRecords / useIncrementalDestroyManyRecords / useDestroyOneRecord (currently used in the deleted-records view). I'd surface a new "Permanently delete" command-menu item that calls the existing destroy path rather than adding new mutations.
• Add it as an engine command (DESTROY_RECORDS-style key) shown directly below the standard "Delete", in both the command menu (Cmd/Ctrl+K) and the record/table option menus.
• Gate it behind a confirmation modal warning that the action is irreversible.
• Respect permissions — only show it when the user has destroy/hard-delete rights.

A couple of quick questions before I start, to avoid rework:

1. Should "Permanently delete" be available for active records directly, or only mirror what the deleted-records view already allows?
2. Confirmation modal on every hard delete (vs. an opt-in setting) — preference?

Happy to adjust to your conventions. Thanks!

[n2ojim]

Only Mirror what the deleted-records already allows would be great.
Confirmation modal on every hard delete (ie: "Warning, this will permanently delete XXX records")

Thx !