Skip to main content

Hi,

When changing a collaborator's role in a subfolder, their access level will also change in the parent folder and all its subfolders as described here:

https://support.box.com/hc/en-us/articles/360043697254-Understanding-Folder-Permissions.

Is there a way to NOT change the access level of the parent folder when changing the access level of a sub folder? And use a waterfall model? I would like to change the access level for the subfolde only ant NOT change the access level of the parent folder. 

Example:

Main Folder
     Client A
          Project A
          Project B
     Client B
         Project A
          Project B

Everyone in my organization has 'Viewer' access to all files. Now I want 1 collague to have 'Editor' access to the Project B folder of Client B. How can I make this happen without giving the colleague 'Editor' access to the parent folder?

Kind regards,

Tom
          

Hi Tom, 

Welcome to the Box Community, I'm happy to help!

There is no way to change the current Collaborator permission on subfolders without changing their permission on the parent folder.

You can, however, give a collaborator a higher access level at a subfolder. To do this, you must first invite the collaborator to the subfolder, then invite the collaborator to the parent folder.  This means you are going to have to remove that colleague from the parent folder and subfolder and then re-invite that colleague following this order: first, invite your colleague to the "Project B" subfolder as an Editor,  and then invite him to the "Client B"
folder as a Viewer. This order should allow you to achieve this goal.

If you have any questions, please let me know and I will do my best to help you!

Best,

Thank you for the clarification! 
The functionality that I described would be ideal in our organization. If there are more people interested in this functionality, it could be something for future development perhaps... For now, we'll find a way to work around it. 

KR

Tom

Terms & ConditionsCookie settingsAccessibility statement