By default, the File Managers root directory is the portal root directory, eg. /Portals/0/. But this dir contains some "system" dirs as well, like Cache, Skins, Containers, RepositoryTemplates etc. which are not related to the File Manager but become visible if the portal admin clicks on the "Synchronize Files" link (some of my customers are very curious and click on everything!).
Basically, I want to make sure that my customers never have a chance to see these "system" dirs in the File Manager - mainly to prevent them asking me questions like "Where does that 'Skins' directory come from? I surely didn't create it!! Can I delete it???"
So, can I configure the File Manager in a way that it uses a subdir as it's root - e.g. /Portals/0/FileManagerRoot/ ?
Sure, I could simply hide or delete the "Synchronize Files" link in the filemanager.ascx, but this would affect all portals. I'd prefer a portal-specific solution!
Any suggestions? I'm running DNN 4.5.5.