I'm curious what sort of situation you have where you trust a user enough to have a copy of a particular directory tree, with the ability to copy it elsewhere and edit it, but you're concerned about them being able to make changes to it.
Huh? Have you ever worked on a shared document before?
To an end-user, the directory tree is a system of record. Many types of files need to "freeze" at a certain point in time -- say a letter that needs to be crafted by multiple people, or a budget worksheet.
In the case of the budget sheet, I don't mind if you copy the file and change some numbers to figure things out -- you're on the Team, after all. But I may mind if you decide to modify a file after we have a consensus that it is "done".
Is that a serious question? I often trust users enough to read my stuff, but not to change it. I feel like I'm in some kind of alternative universe when you ask me a question like this. Access control is basic file system stuff, and has been forever. My understanding is that DB can't coordinate access control across the platforms that it supports. I don't understand why they can't build their own access control layer.
Wrong. If I share a document with another person who is only supposed to read it, and that person deletes it, how long before I notice it's gone? What if that person edits the document? Will I ever notice?
Saying that access control is unnecessary for Dropbox "for Teams" is absurd. Here's an easy example: My law partner and I share our documents via Dropbox. I want him to see my docs, be able to read them, save new versions, etc. I don't want him to be able to change my directories.
