I think I must be losing my mind in my old age
Vault does require write access to the files in order to move them.
Another thing you can try;
Go to the lifecycle state and change the security to allow the user to have write access.
Then the user can perform move without the need to change the state.
Dont forget to put the security back when you are done.
I just looked at 2012 (for which I had an environment handy), and for moving files, you must have write access to the source folder, the destination folder and the file itself.
Nevermind, I figured out why my permissions aren't as expected. I guess I didn't understand the groups, roles and lifecycle permissions enough. I figured it out now after speaking with someone and figure out why I cannot perform any actions on released files. Thank you everyone for helping.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!