My feedback

1 result found

1. Break waterfall permissions

   381 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   75 comments  ·  Help shape the future of Box » Core & Technical Infrastructure  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   not planned  ·  AdminJack Hirsch (Product Director, or Executive, Box) responded

   We understand the request, but unfortunately this is not on the near-term roadmap.

   An error occurred while saving the comment
   Anonymous commented  ·  May 7, 2021  ·  Delete…

   I'm also trying to allow a collaborator to see everything in a top level folder (as a Viewer) -- but to only be able to edit items in a subfolder (as an Editor). Having to put the subfolder at the same folder as the project itself in order to accomplish this complicates teamwork substantially.

   It's plainly logical to allow users lower down to have more rights. Our internal corporate servers function this way -- we can't change things at the top level, but we have complete rights in certain folders lower down. I expect most corporate servers work this way.

   I know our company has been considering contracting with Box to provide full remote server services. But we certainly won't be able to unless top level folders can be tightly controlled, with subfolders that allow the same users more rights.

   Please rectify this. "Waterfalls" only fall down -- they don't also travel upwards.

   Save Submitting...