Skip to main content
Solved

Folder tree viewing issues


Chris Hunter

I realize this is probably the wrong forum.  And I am sure I am overlooking something simple - but I am having an issue with new users view of folders within Box.  I haven’t had this problem in the 2+ years we have been using Box and I have spent more time than I care to admit trying to figure it out.  


For the last two years my existing users will navigate to the folders in Box via the path - All Files>Salesforce Root Folder>Object Folder>Record Folder. All collaboration is granted via the Box for Salesforce integration. They don’t have collaboration rights granted to anything but the selected Record Folders - but they are housed in the above tree and makes their All Files page much cleaner.

The issue is that my recent new users (last 2 months) are not getting this same tree.  Instead it is All Files>Record Folder.  And results in a cluttered mess on their All Files page.  Ultimately they can still get the folders and files they need to do their job - but the user experience isn’t great.

Outside of granting them viewer privileges to the root folder I can’t figure out a solution (and that isn’t an option). I have confirmed group affiliation and profiles to match between existing and new users.  And can’t tell any difference other than the date of their user creation.  Any one have any thoughts on what triggers them to fall under the tree?

Best answer by Jey Bueno Box

Hello ​@chrish Just to add, the Box Access Level custom setting enables mapping different Box collaboration roles.

 

Note that this will not immediately remove the folders from users’ All Files page. You will need to interact with another Salesforce record with the same type (e.g., open the Box component on another Account if you’re seeing SF accounts on their All Files). Once you do, the new collaborations created with can_view_path should cause all the other collaborations on matching record type folders to move under the Salesforce folder tree.

 

Feel free to reach out to us if you have other questions or concerns. 😊

View original
Did this topic help you find an answer to your question?

6 replies

  • Participating Frequently
  • 8 replies
  • March 7, 2025

Hi Chrish, 
It sounds like the the can_view_path seems to be disabled. Did you recently start using the Box Access Level custom settings? If so there should be a checkbox to enable this. 


Jey Bueno Box
  • Community Manager
  • 343 replies
  • Answer
  • March 11, 2025

Hello ​@chrish Just to add, the Box Access Level custom setting enables mapping different Box collaboration roles.

 

Note that this will not immediately remove the folders from users’ All Files page. You will need to interact with another Salesforce record with the same type (e.g., open the Box component on another Account if you’re seeing SF accounts on their All Files). Once you do, the new collaborations created with can_view_path should cause all the other collaborations on matching record type folders to move under the Salesforce folder tree.

 

Feel free to reach out to us if you have other questions or concerns. 😊


Chris Hunter
  • Author
  • New Participant
  • 3 replies
  • March 12, 2025

Thank you very much for the responses.  I hadn’t previously had to make any adjustments of the Box Access Levels in the past for my existing users.  But I have now created the new org rules for the can_view_path for my users and it appears to have resolved this issue in my org.  Greatly appreciate the help on this!


Jey Bueno Box
  • Community Manager
  • 343 replies
  • March 12, 2025

Awesome! Glad to know that it worked. I’m curious, since this only applies to your new users—did you recently upgrade your Box for Salesforce package? It’s possible that the upgrade paths caused the addition to break the default can_view_path setting.


Chris Hunter
  • Author
  • New Participant
  • 3 replies
  • March 12, 2025

No I hadn’t upgraded it since March 24.  I did push the upgrade yesterday after I made the changes (and verified it was resolved). 


Jey Bueno Box
  • Community Manager
  • 343 replies
  • March 12, 2025

I see, thanks for the information. It really helps us better understand the issue, and we’ll figure out with our internal team what may have caused the changes. I appreciate it! 😊


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings