A colleague asked for guidance on how to replace files in collections. She reported that in WB1 when uploading a file with the same name as a already existing file, the file is not replaced but instead a new file with the extension " (1).extension" is created (see screenshot). I tested how the behaviour is in WB2 and there the file is replaced without asking for confirmation. I think a good solution would be to leave the decision to the user whether the file should be replaced or saved with an extension. But at least the two workbenches should do it in the same way.