Admin action "Access Personal Folder" changed without notice (for the worse)

  • 3
  • Problem
  • Updated 9 months ago

Revert the way "Access Personal Folder" works when an admin needs to access an employees personal folder.

Normally, when an admin manages an employee in ShareFile, and clicks "Vies folders and activity logs", they could click "Access Personal Folder" in order to open that employees personal folder in order to give support on various tasks, mostly giving people access to project folders hosted in the employees personal folder.

This have been changed to just pop-up a list of folders that the admin can then download.

I have scoured through the release notes for ShareFile Web, all the way back to 18.5 and nowhere is this change described or explained. Making a major change like this that directly impact on our daily use, without prior notics and another way to continue doing our work, is simply not okay. I expect this to be changed back, or an alternative being presented ASAP.

Photo of briped


  • 10 Posts
  • 0 Reply Likes
  • annoyed and frustrated

Posted 9 months ago

  • 3
Photo of Cindy Morda

Cindy Morda

  • 20 Posts
  • 5 Reply Likes
Yes, I agree.  This needs to be changed back IMMEDIATELY.  We cannot do our jobs as Administrators.  The only option we have now is to change the user's password and log in as them so that we can have full access to their folders.
Photo of Chris Anderson

Chris Anderson, Product Manager

  • 338 Posts
  • 54 Reply Likes
There is currently a workaround that can be used for the time being. A video of how the workaround works can be found here:

The short is that you can get the users Folder ID when the modal opens if you look at Chrome/IE dev tools. From there you can open it as a normal shared folder. I will reach out to each of you individually, via email, to get exact use cases so we can solve them appropriately. 
Photo of Chris Anderson

Chris Anderson, Product Manager

  • 338 Posts
  • 54 Reply Likes
Brian / Cindy, we just released a hotfix that rolls back this change so the page / setting should continue working as it did previously. I apologize for the inconvenience that was caused. 

I also wanted to thank you for speaking with me yesterday via our phone calls. As we discussed during our calls, I relayed both of your use cases to our internal teams so when we update this page next time, your use cases will still be covered and supported.