can_view_path

Hey Elizabeth, 

Can you provide me more information on your use case, as well as what you have already tried? This will help me point you in the right direction! 

Thanks, 

Alex, Box Developer Advocate

Hello, 

We're setting up box for our company, and would like to incorporate the "nesting" feature that it seems can_view_path provides so that our employees can see what parent folders the subfolders they have access permissions to live. We were pointed towards can_view_path by a support employee for box, but then were told they cannot assist in the setup of that, and I am pretty clueless as to where to begin to incorporate that solution. 

Thank you, 

Elizabeth Reigel

There are a lot of ways to interface with our API, but the easiest is with the Box CLI? Running an update command on a collaboration similar to the below would update a collaborator to see the entire file path. 

box collaborations:update <insert_collaboration_id> --role=editor --can-view-path

Thanks, 

Alex, Box Developer Advocate

Hello, 

Thank you, we feel close, and are at the point of inputting the 

box collaborations:update <insert_collaboration_id> --role=editor --can-view-path

Is the collaboration id just the name of a folder we've made in box? Or if not, what is the collaboration id? And will this automatically add "can-view-path" for all users involved in that collaboration?

Thank you very much, 

Elizabeth Reigel

Hey Elizabeth, 

The collaboration id is actually the id of the specific user or group collaboration. The id can be returned by using this endpoint. Here is the example using the CLI syntax. You will actually put the folder id in the command like this:

box collaborations:get <folder_id>

There will be several ids returned, one for each user or group collaborated. Does this help? 

Thanks, 

Alex, Box Developer Advocate

I tried entering the command box collaborations:update <insert_collaboration_id> --role=editor --can-view-path and get the following error:

Unexpected API Response [404 Not Found | j3pcnthfkemmjys2.0bdf0b90f4644767b7323a03c8673ad4a] not_found - Not Found

The user I've inserted in <insert_collaboration_id> via digits or email address returns similar errors.  The user I'm applying the command against is the Owner of the Box tenant.  

Can someone assist?