Custom rule for deleting a record, possible?
When you go into a table's access panel to view the roles and their permissions against it, you have the option to make custom rules for the viewing and modifying of a record. There is no option like...
Forum Discussion
The way I handle deletions is to build a custom method for users to "mark" a record for deletion. This triggers a change to the record which can hide it from the Users; but not from administrators. Administrators are then notified by email (notification or subscription) of records to delete. They make the final decision to delete or not. Once data is deleted it is gone. Mistakes are easily made. This method for me ensures that data is not "accidentally" deleted, which results in a lengthy process with Quick Base to retrieve lost data. Also, often data is "connected"; so that means the deletion process is likely more than just a single-table of records.
Another methodology I deploy is to create a delete-only Administrator Role. This means that even Admins cannot delete records unless they switch to a role using the "test as a role" feature. This prevents even Admins from accidentally deleting records they do not mean to (and trust me, this happens more often than it should). If they have to switch roles, it means they know they are deleting records from a given table.
You can then have other triggers delete child-connected records; or build a button to do all the deletions itself. Make this button visible only to the Roles that should be allowed to delete.
This helps protect your data; and protects you from additional administrative work/liaison in the event of a mistake. It's much easier to "uncheck" a box or empty a date value than to retrieve lost records.
Another methodology I deploy is to create a delete-only Administrator Role. This means that even Admins cannot delete records unless they switch to a role using the "test as a role" feature. This prevents even Admins from accidentally deleting records they do not mean to (and trust me, this happens more often than it should). If they have to switch roles, it means they know they are deleting records from a given table.
You can then have other triggers delete child-connected records; or build a button to do all the deletions itself. Make this button visible only to the Roles that should be allowed to delete.
This helps protect your data; and protects you from additional administrative work/liaison in the event of a mistake. It's much easier to "uncheck" a box or empty a date value than to retrieve lost records.