New named Dropbox structure

Hello,

It appears my root folder is no longer "/", but is now a system-created folder called "/CheerSounds/" (or in other words, "/<username>/"), and that now appears as the root of all connected client apps.  I can't make sense of it, but it has created some big issues for our workplace.

Our log shows that a series of policy changes and folder changes occurred at 02:06 est on 11/26 which have interrupted our business operations in the most severe way. The logs show that the changes were made by user unknown and location unknown.

On our account, username "CheerSounds", it seems that the contents of our root folder "/" has been relocated to "/CheerSounds/" . We are unsure of how this folder was created; there is no log of it ever happening. It's permissions are set to "Only Me".  More interesting, our connected dropbox client apps (mac, windows, linux) can not see the actual contents of "/" any longer, instead they only show the contents of "/CheerSounds/" as if that was the root!  Was a system-wide change made to tell client-connected devices that the root is actually "/<user-name>/" ?

Also concerning, our largest and most important folder "/CheerSounds v2/" now exists in both the actual root "/CheerSounds v2/" and in the new folder  "/CheerSounds/CheerSounds v2/". It appears the moving/copying of this folder failed and left only a partial copy in "/CheerSounds/CheerSounds v2/".  Our client systems have all automatically synchronized to "/CheerSounds/CheerSounds v2/" , leading them to believe that the failed copy is actually the removal of hundreds of thousands of files, which all of our client computers have now aligned to. This resulted in the removal of hundreds of thousands of files from all client devices. The client devices indicate they are "up to date". 

My question is: was a change made to create a virtual root for client devices?

I cannot explain or understand why the "/<username>/" folder was created by "unknown user" from "unknown location" or why all of my files have been moved into it, or why that new path appears as the root folder for all of my dropbox connect clients.

As far as why the file copy may have failed: We have incredibly long filenames on some of our media, often being exactly the limit of 256 characters of a file path. My guess ... is that Dropbox intended to move the old root "/" into "/CheerSounds/" which would now (somehow) the be root for dropbox client applications...but the file copy of "/CheerSounds v2/" failed due to some of the file paths within that folder being 256 characters long with no room to spare for the new, longer path of "/CheerSounds/CheerSounds v2/........"

Regardless of what happened, our entire office of multimedia projects is left in a compromised stated which I must resolve Asap! Any and all insight is appreciated  so that I may remedy this and not impact the entire office for long.

Thanks,
Carmine Silano
CheerSounds Music