Audit / Track who Moved File / Folder

[johannes.bauer]

Description:

Customer has a defined folder structure with naming and numbering convention and files and folders are propertly organized

Challenge:

If users want are not following the correct process they move files around to wrong folders and even to the root folder within Vault.

The Admin needs then to move those files back and remind the users to follow the process, but some times this is not enough.

Proposal:

Track / Audit who moved files the last time from what folder to what folder and make that visible for the admin in the details tab.

[kennyjohnson1]

I think there should be an option to track file moves within Vault. It is not uncommon to have a "where did that file come from?" question when you have multiple users working within a project area. We can turn off delete controls to some users, but they still need a place to move their "To be Deleted" files for approval - it would be great to know who thought a file should be deleted without having to develop a folder structure for each user. I also am trouble shooting a project that is not following the established file structure - I cannot tell who placed the wrong files in their current locations, and it is only because I know where the file was originally that I am able to rule out the person who last check-in the file as the mover. Please vote to have an option to turn on comments or tracking of files when they are moved in Vault. Thank you, Kenny

[catot]

I agree, this would be very useful. I suggest to implement something like a property called "Path (Historical)", which then could be visible in the History-view by default.

[Anonymous]

Creating a path historical property would be an interesting solution for folder tracking.

Could another solution for files be to create a new file version in vault for each "move" operation?

This new version would have an automatic comment containing the old file path, and the version would be created by the vault user who moved the file. 

[radu1234]

I would really like to see this functionality implemented in Vault. 

Radu

[paulo_figueiredo_wsp]

Admin community welcomes this feature.

[limin.chung]

Hi @paulo_figueiredo_wsp @radu1234 @catot @kennyjohnson1 and voters of this idea,

Thank you for your interest and support for improving the Autodesk Vault logging experience. The Vault team is currently exploring this area and would like to better understand how you use logs today, the challenges you encounter, and what improvements would be most valuable to you. If you work with Vault logs for administration, troubleshooting, monitoring, or support, we’d really appreciate your feedback through a short survey in the NDA-based Vault Feedback Community:

👉 Autodesk Vault Logging Experience Survey

Note: if this link doesn't work, you could sign in to Autodesk Vault Feedback Community to access this survey on the Activities menu. 

Your feedback will help us better understand customer needs and inform our exploration of the Vault logging experience.

Thank you in advance for your time and feedback!

[kennyjohnson1]

This request was from 9 1/2 years ago!  SolidWorks had this solved at the time of the request.

No, I will not participate in a survey - the request and reason for the request are clearly stated in the original 2 posts.

This is another example of why Autodesk is no longer the gold standard in CAD software and Engineering solutions. Work arounds and third-party solutions are needed for products' poor development and launches.

[vali_dobrea]

Hi @limin.chung it seems that the link provided for the survey does not work! 

[limin.chung]

Hi @vali_dobrea, Apologies on the link it could be the community was updating just now. You may try clicking on this following link at your convenience time again. Thanks in advance.

• Autodesk Vault Logging Experience Survey

Note: if this link doesn't work, you could sign in to Autodesk Vault Feedback Community to access this survey on the Activities menu. 

[limin.chung]

@kennyjohnson1 Thanks for the candid feedback. We understand the frustration given how long this request has been open. The team has had to balance this alongside other development priorities, and we sincerely apologise for the disappointment this has caused.