Are they using window 7 and try to delete it in windows explorer?or you can close to show the "previews pane" and try to delete and see.
I think you have two options:
- Grant delete permissions in every state the file has been in.
- Create a state called "Deleted" or "Trash" (or something), grant delete permissions, AND check the box "Ignore permissions in previsious states"
Knowing this, a best practice is not doing the delete if the file has EVER been in through a released state to avoid deleting formerly released versions and/or losing history. Come to your own conclusions on what your options are based on your regulatory requirements and company policy.
However I do recommend to approach this one with caution.
Hope this helps!
How about a Trash folder? Does anyone use that to allow users to mark stuff for deletion? Seems similar to the Deleted State idea but avoids creating another state.
It seems users can move files (in certain editable states) to folders even when they can't delete (because the file was previously in a protected state). Then an Admin can empty the trash folder periodically.