This is a no-brainer feature that must be added. Let's go!

This is super important for us as well. We have multiple terrabytes of data on Box, and generally it works very well for us. However, we have many situations such as "read only on the parent folder, but everyone should have edit access on the DRAFT folder" that is basically impossible to implement today, especially as we add other "projects" that have their own parent and DRAFT folders.

Has Box added this to the project plan or already implemented this change? We need the ability to disable cascading folder / waterfall permission.

We have files on some projects that are covered under an NDA that should only be accessible to some of the project team. Very messy to have to store them in a completely separate folder structure to the rest of the project files due to the forced inheritance of permissions. Pretty basic feature really.

Come on Box team, you've had 7 years to find a solution.

It's so hard to believe that this isn't possible.

Importantly, what's described in the help page (https://support.box.com/hc/en-us/articles/360043697254-Understanding-Folder-Permissions) and by the Admin below doesn't actually work. I just invited a new collaborator to Subfolder A at Editor level. After that, I invited them to the parent folder at Viewer Uploader level. Now, they have Viewer Uploader permissions in Subfolder A also. Super frustrating and broken.

This feature IMHO is required for any mature file management platform. Please add ASAP. We need to control access at a folder by folder level. In our most immediate case, we want users to have view access to a shared access folder the admins manage, but uploader or edit access to other folders as needed - so files won't be cluttering things up. I'll escalate through our corporate BOX contacts as well. Thanks!

This feature is really needed. Currently there is no option to restrict edit access to a subfolder within a project file without moving it to a different folder, which messes up with our records management policy relating to saving files in the designated project file.
Even Sharepoint offers this function and whilst I am struggling to convince management that Box is a preferable option to Sharepoint for our files, issues like this are making it difficult to win the argument.

This feature is really needed. Currently there is no option to restrict edit access to a subfolder within a project file without moving it to a different folder, which messes up with our records management policy relating to saving files in the designated project file.

Why would this not be on the roadmap when your clients want it? Is it just not possible?

who actually thought forcing the users to accept, that inherenting permission levels from the folder above, is a useful thing from the first?

I was told by one or more Box salespeople that it would be possible to restrict permissions in subfolders differently from the parent folder.

I guess we'll be cancelling our Box subscription and going elsewhere.

So frustrating and illogical. Also, don't call this "waterfall" if it also goes against gravity half the time.

All of Box's arguments for not doing this make no sense - the comment from Anonymous Admin in July '22 suggests that what they call "Senario A" of having access to a house but not a bathroom makes no sense.

"(Scenario A) Notably, customers know that a user at the subfolder can't have LOWER permissions than the same user at the parent folder (e.g. if they own the folder, it would be odd for them to not also have owner access to everything inside of that folder)."

First of all - bad analogy, I do not have a right to barge into a bathroom even in my own home if the door is locked - there are valid reasons why that would NOT be OK. Also, let's extend this lousy metaphor to a grocery store - if a 20 year old adult owns the store, that does not give them legal right to then consume the alcohol.

The whole point of a hierarchal information structure being controlled by access levels makes no sense - most people organization information need to organize by content (i.e, Product Documentation->Product A, Product B, etc. I may want a product manager to be able to create document in the Product Doc folder but do NOT want them to even know that Product B exists - this is a common scenario and works in many other systems.

The absence of this feature is really annoying !
For a given BOX folder, shared within my team with Editor rights, with BOX.com I can't
* add a Read-Only folder for the team (like ".../Archives/2021")
* add a personal & hidden subdirectory (like ".../myDraftWork")

Creating dedicated folders outside the project directory is NOT convenient at all, as we loose the structure / logic .

BOX.com, please improve the situation !

My house has a lock on the front door and I can have a lock on a bedroom too. I'm not too certain why this a hill to die on.

Today, there is a LOT of confusion about this...

(Scenario A) Notably, customers know that a user at the subfolder can't have LOWER permissions than the same user at the parent folder (e.g. if they own the folder, it would be odd for them to not also have owner access to everything inside of that folder).

(Scenario B) BUT... many customers want to give a user at the subfolder HIGHER permissions than the same user at the parent folder (e.g. Lisa has Editor access for HR benefits subfolder, but only Viewer access for HR parent folder... analogously, for a hotel you have "Editor" access to the "subfolder" room you are given a room key to, but you don't have access to sleep in the hotel lobby that everybody has "Viewer" access to).

Today, Scenario B is possible through proactively giving the person higher permissions at the subfolder (e.g. Editor) and then lower permissions at the parent folder (e.g. Viewer), but a lot of customers don't do this proactively, because they start by giving the person access at the parent folder, and they want to give the user permissions on the subfolder retroactively (e.g. maybe the subfolder didn't exist when the parent folder was created). When they change permissions at the subfolder retroactively, they get the error "Change Role for Parent Folder," regardless of if they are giving the user higher or lower permissions at the subfolder.

Giving customers the option to retroactively give users higher permissions at the subfolder would be immensely valuable.....

This would indeed be a useful feature.

This needs to be added to your near-term roadmap.

This functionality is definitely required. Box needs to do something to add this functionality,

This needs to be added to your near-term roadmap.