Posting evidence of this would be useful, because Drive is pretty comprehensive in terms of compliance. Also not sure what you mean by "workflow needs". Why would you use a file storage service to manage workflows in the first place?
> Person A can only read document X because they are performing duty b on project y.
How is this _not_ a binary can/can't read scenario? The person can either read it because they're performing the duty, or can't ready it because they're not.
It's not binary because they should only be able to read it while performing duty b. There needs to be something that enables/disables access when they start/stop working on it, or checks access before the read it.
Because most workflows involve some kind of document. Automatically routing that document to different people and standardizing the way they interact with it can be very beneficial.
Wouldn't that what the Drive API can be used for? I may be answering my own question here, but I imagine that would be the most useful part of this Box/Drive partnership. :D
