Separate Delete permissions from CRUD access

Product Suggestion

Introduce a standalone Delete permission that can be managed independently from standard CRUD (Create, Read, Update, Delete) access controls.

This would allow administrators to grant users the ability to create, view, and update records without automatically providing permission to permanently delete information from the system.

The functionality could support:

• Independent delete permission toggles

• Role-based delete access

• Additional confirmation prompts for deletion actions

• Enhanced audit logging for deleted records

• Granular permissions across different modules and record types

This would provide organisations with greater control over sensitive actions while maintaining operational flexibility for day-to-day users.

Problem Statement

Delete functionality is currently grouped within broader CRUD permissions. As a result, users who require standard operational access may also unintentionally receive the ability to delete records.

This increases the risk of:

• Accidental deletions

• Loss of important records

• Additional support requests

• Audit and governance concerns

• Reduced control over sensitive system actions

Suggested Improvement

Separate Delete into its own configurable permission that can be assigned independently from Create, Read, and Update access.

Potential Benefits

• Reduced risk of accidental deletions

• More controlled access to record removal

• Clearer permission management for administrators

• Fewer support queries linked to deleted records

• Improved audit and governance controls

• Greater flexibility when configuring user roles and permissions