In your process, you have a couple of different capabilities that, when used together, make for an outcome that does not seem logical.

The two processes are:
1. The ability to set it such that a user uploading from the front end has to get approval first before the file is available to the community of users that can see the files.
2. The ability to allow or not allow a file to be uploaded that has the same name as an existing file… in essence over-writing the the existing file with the new file.

When these are used together, the current process goes that the newly uploaded file that has the same name as an existing uploaded file goes ahead and overwrites the older file even before the admins have approved this new file. This seems very counter-intuitive.

I realize that we could just not allow files with the same name to be uploaded but that goes against a smooth workflow we are seeking. We actually do want our users to be able to upload what they think are improvements to an existing file. And, once the admins review this file, for that to then automatically over-write the existing file. But, we need the admins to be able to approve or reject the uploaded file by the users before the prior file of same name is either replaced or remains depending on the actions of the admin.

Any thoughts about putting the files uploaded that require admin approval in a temporary folder off to the side then automatically put in the final destination once the admin approves them?

Thanks.