We have an issue where we cannot legally "destroy" records. Draft documents, Letters that are written but not sent and even (apparently) post it notes can count as records and must be kept for 7 years.
However users want to be able to delete. All our documents have their security settings set to container so the first idea was to setup a container where users could Contribute Contents but not view them. I found a post that  seems to imply that this can be done but in our tests it’s not working because users can find the folder.
Is there any way users can hide a document form everyone including themselves (but not admins) it so if we get FOI requests it’s still there?
Some TRIM partners provide a solution which allows the user to right-click->request delete. The utility captures a reason and then either adds a caveat or changes the access control (there are a few other options as well). That way the user thinks it's gone from the system, but you have the oppotunity to put a draft schedule on it and destroy it according to draft policy.
If you don't want a solution you could just have your users email you a reference link to the document, then you perform those same steps manually.
if your system is configured not to allow users to delete records (so your users do not have delete record permission) then there are some other setting you need to check that could be used to get remove (delete content) from records.
(so in a reverse way these are 'methods' people can use to remove content, not that I'm advocating this as a solution to your problem - so no kudos marks for this please!!)
On the Document Record type:
Allow Replace. if this is enabled a user could replace the content on a record by checking in a blank document.
(I think this is on as a defult on a record type)
If this is enabled (again I think its on by default on the record type) then also check if users also have the document delete purge permission. If they do then a user could checkin a blank document as the lastest revision and then finalise it and choose to remove previous revisions. (I think Information workers have this permission as a default)
We have a separate tab on the record entry form called 'Request for Deletion'... the end user completes the details and the Administrator picks this up by Searching for 'Request for Deletion' (a User Defined Field) = Yes... then the Administrator places in a Container/Folder that has Access Control set whereby only the Administrator can see the records contained.
Thanks TOTinQLD, that's great we have copied that setup and its working well. I have contacted Kapish about getting a delete option (that can be automated) but there was a lot of pressure from higher up to get a solution ASAP and this fits the bill perfectly.
I've just read your response... "...getting a delete option (that can be automated)..." and it's made me (and probably most people in Records/Archiving) twitch nervously... Deleting records should only be done by Administrators, after reviewing retention schedule, and never automated... too much room for error!
Glad the 'Request for Deletion' tab is working for you.
I'm not a programmer... just a lowly Records Administrator ;)
I do my 'housekeeping' daily and the records 'Marked for Deletion' get picked up fairly quickly. If you look at the PDF attached to my 1st post (the one marked as the 'Solution' above), you'll see the users do have to nominate a reason for the deletion... from a pre-defined list (note the drop-down list box button) or they can type a reason.
I like them to stop think about why they are nominating the record for deletion.
My recent comment was more about automating a 'Delete' not automating a 'Mark for Deletion'.