Put handler QueryDocumentDelete and not remove documents from the database, and for example, change Form on "DeleteDocument", that is "move" documents to own recycle bin. And access to recycle bin, restrict administrators.

Hi Vlad,

thank you for your response. This means you need in-house designer skills which is not the case in smaller environments. And also means that you need to manage those undeleted documents. How long do you keep them? With all the risks that they may get archived by external tools, etc. ...

Mathieu
If implement what you ask for, it will be impossible to recover the document.
I propose a solution that will permanently delete the document (later), and recover it.

> How long do you keep them?
This is more of an organizational issue.
I would prefer to focus not on the storage time, but to limit of removal of documents that may be important (eg registered, which were assigned a status, etc.).
So removed will only unimportant documents (mostly drafts), and the others are not relevant at the moment, but necessary for the history to move to the archive.
All these and other constraints (eg delete documents give only the author of the document or administrators) can be programmed in the event database QueryDocumentDelete. This is the only right and complete solution.

I vote for the need of logging of documents removal:
1. In User Activity in the properties of the database
2. In Session Activity in log.nsf

It would be nice to have the option, indicating that UNID of documents shold be logged. Not only for the removal, but also to read/modify.
Also would be nice to have the option, indicating what events shold be logged, i.e. DbOpen/Db Close, ViewOpen/ViewClose, etc.

It would be possible to introduce a logging section for server or configuration document. Which combines elements of existing logging and add new ones. Concept should be thought out. For example comes from Extracomm SecurTrac.