Skip to content

David Simmons

My feedback

2 results found

  1. 387 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    David Simmons commented  · 

    Absolutely an oversight to not allow this in some form. Simple example, if you want to have a folder of reports, or sales, or salary info for each employee, you would have to have one folder for EACH employe at the top level of your file heirarchy. Can we put them all in a folder marked "Employee sales reports" or whatever? NO. Because then EVERYONE could see everyone elses information. This is broken. Other services allow it. MUST be resolved.

  2. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    David Simmons commented  · 

    I'm voting FOR this, but primarily because the "share" ability was apparently removed from google docs, if you create them within box, to be stored there. (I posted another article on this titled "Google Doc "share" from google.")
    I can see what this user is asking for, and agree it would be useful. For us though, we actually DON'T want to manage two separate file storage systems. But the way the current google docs integration works, which removes the ability to "share" the doc from within the google doc itself, is not only cumbersome, but creates potential security vulnerabilites which are simply unnecessary.
    In the use cases where we need to use google docs, I don't want to have to go THROUGH box or require box "collaboration" to be enabled, just for an outside user to access and edit the google doc. There's no reason to create this burden, or add the potential for the wrong document (or folder) to be invited for collaboration.
    If you are integrating with google docs, DON'T BREAK it's core functionality.
    Doing what this user wants would be one workaround which would fix their issue, and also allow us to keep google docs functional while also makeing those files available to view in box.

    David Simmons supported this idea  · 

Feedback and Knowledge Base