3 ms·
Same here. We also have clients who have started to use dropbox for file sharing with us. This is giving the legal department heartburn...
by jstalin 14y ago
Same here. We also have clients who have started to use dropbox for file sharing with us. This is giving the legal department heartburn...
- thwarted 14y agoBecause of files exposed to outside parties? How is this any different than people emailing files around (which legal departments still do themselves quite a bit)?
- quotemstr 14y agoBut Outlook lets you mark an email as "do not forward". That makes it safe, right?
- meaty 14y agoYes if you have the relevant group policy rules and filters in exchange.
- erjiang 14y agoDocuments in many places complicates things. For example, if you have to go through discovery, all of a sudden you have to make sure you find things on every single service you've stored them. That's (part of) legal's job, and the number of different services you're using is a multiplier on a lot of things. What gp described just seems inefficient in general.
- thwarted 14y agoExactly, and documents emailed around exist in many different places, in many different mail boxes and on many different machines.
- kenjackson 14y agoAlthough corporate emails all typically exist on an exchange server. Better in email than 100 different Dropbox accounts.
- thwarted 14y agoI won't question the (proper) assumption that enterprises typically use Exchange, but I will say that this is why solutions like Dropbox exist and are adopted in enterprises: because it's easier to get the information where it needs to be than what "enterprise" solutions offer.
- InclinedPlane 14y agoIt's more that the greater number of channels the more difficult it is to harmonize corporate policies across all those channels. For example, communicating via email entails data retention for a period of time as a matter of law these days (SOX, etc.) What happens when people start using a shared dropbox instance to send, say, todo lists, short messages, power point slides, tech specs, etc. to each other? What's the intersection with the types of communication which are sufficiently "email like" to trigger a concern in terms of data retention? And then that brings up a whole host of technical issues and so forth.