Separate Permissions for Cancel vs Delete Booking

We would like to request more granular permission controls for booking management, specifically the ability to separate "Cancel Booking" and "Delete Booking" into distinct permissions.

Current Issue

Currently, users with booking management access can both cancel and delete bookings. This creates operational risks where staff may unintentionally delete bookings instead of canceling them, leading to:

• Loss of booking history
• Data inconsistency
• Reporting and accounting issues

Requested Feature

Introduce separate permission controls:

• Cancel Booking Permission
  • Allows users to cancel bookings (status change only)
  • Keeps booking data for audit and reporting
• Delete Booking Permission
  • Allows permanent deletion of bookings
  • Should be restricted to admins only

Use Case

In real-world property management operations:

• Staff should only cancel bookings
• Only admins should have the ability to delete bookings

Benefits

• Prevents accidental data loss
• Improves data integrity
• Supports audit and compliance requirements
• Aligns with real-world operational workflows

Additional Suggestion (Optional)

• Add a confirmation or soft-delete option before permanent deletion

Closing

This feature would significantly improve operational safety and control for teams managing high volumes of bookings.

We appreciate you taking the time to submit this feature request! If you know other users who would benefit from this, we'd encourage you to share it with them so they can add their support by way of an upvote at the top of the page.