Well, the thought was to look into adding a field on the file (I did mention I was just spit balling right) that when checked was trigger the flow to delete it, but it looks like there is an Idea out there now for this too, meaning we can’t trigger anything to delete the specific file based off automation either.
Automation is out then, meaning we’re back to permissions based deletion, which is the limitation of Salesforce at the moment.
In your test environment, your last two options are:
- Put the user who needs to delete the files higher in the role hierarchy than user who created the file (meaning you’ll probably want to place them at the top if the file deletion piece is of the utmost importance, but that will also need other consideration since they’ll basically have visibility to many more things).
OR
- Configure Account sharing rule so that the user who needs to delete gets read/write access to Files owned by other users.
https://www.youtube.com/watch?v=LavxYG7_WQghttps://www.youtube.com/watch?v=JTrkKziqh90Peter Reid
VP, Sr. Product Manager - Salesforce
