Protect project attachments

[Mijar007]

Users generating an attachment are its Submitter. The Submitter role cannot be transferred. Therefore the Submitter keeps all admin rights and can alter a projects attachment after leaving or being set as inactive. That is risky.
On the other side can an Asset Housekeeper do the same, which could be unwanted. A typical attachment example would be an experimental protocol, which could be shared with different projects and adapted over time.
I suggest that a fork of an attachment will be generated if either: An inactive or non-project Submitter or the the Asset Housekeeper modify the file for the first time after the Submitter left the project.
Depending on the license it may be necessary to inform or ask the Submitter for permission.