In the example above, if you’ve already shared the Finance Committee folder, you can’t share its parent folder Board of Directors until you unshare the Finance Committee folder. You can’t do multiple shares at different levels of a folder hierarchy.So if you share a folder called Board of Directors with your entire board, its subfolder called Finance Committee also has to be shared to the entire board – you can’t limit access to that subfolder to just the finance committee. More surprisingly perhaps, permissions can’t be adjusted below the root folder you are sharing. Permissions granularity is limited (Read/Write, Read-Only and No Access are your only choices).And this is a big deal because unsharing and resharing means everyone who is sharing the folder has to resync the folder to their local Dropbox for Business folder. You can’t rename the root of a shared folder without unsharing it, renaming it and resharing it. Get your root folders named right the first time.Dropbox for Business is a little bit different: Like most of the nonprofit world, we are used to the Microsoft approach to using and supporting file servers. One set of limitations we’ve discovered relates to folder sharing. The learning curve challenges are real, but our clients largely find the benefits of Dropbox for Business outweigh these challenges. We’ve found client satisfaction with Dropbox for Business to be quite strong once the service is operational and users have learned how to use it. In this post I’ll cover Community IT Innovators’ lessons from the field – things we’ve learned, or learned are important, about Dropbox for Business – from actual implementations and client use. We’ve compared Dropbox for Business to OneDrive for Business and SharePoint in past webinars, reviewing the service’s advertised specifications, coupled with insights into how nonprofit organizations work and what they value in a document sharing service.
0 kommentar(er)
