Hi there, 

Welcome to the Box Community! 

This issue should be best addressed by our Product Support. I have created a ticket for you and kindly check your email for updates. 

Thanks!

Hi, i was just looking for the answer to this question too. Please can you share the answer so I can review the same option for our parent/sub folder restrictions too.

Hi: Can you share the answer to this question? This is a common request.

Hi Anna and Neil, in response to the following query extracted from my original post:

"The advice given in the support pages is that any changes to collaboration on a subfolder will affect the collaboration on the parent folder as well. Does that mean it is not possible to have a subfolder which has a much smaller group of collaborators without affecting the parent folder?",

the support team provided the following answer:

"That is correct, you cannot change the subfolder permission as it will affect the parent folder. A workaround for this is to move the subfolder to the root level."

You can have a group with Viewer access at the parent level and then create another group (or individuals) and supply them Editor access to only the subfolder. 

If you have given the group Editor access to the parent folder, then you can not restrict a subfolder to only Viewer (or no) access.

I believe this permission limitation is intentional by Box, but I find this limitation to Box's waterfall permissions structure to be almost annoying enough to get me to switch to another platform.

I'm seeing so many community posts about this.  It's absolutely mind-blowing that there isn't yet an ability to manage permissions per subfolder. Deviating from a logical and traditional organization of folders, having to make additional parent folders is insane. 

Has this changed in the last year? It's become inportant to our team as well.