We have a folder that is shared with our entire organization via a shared link with a vanity/custom URL in this format:
https://{account}.app.box.com/v/{custom label}
We have published a number of links to various nested items in that folder (sub-folders/files) on our intranet e.g.:
https://{account}.app.box.com/v/{custom label}/folder/{folder id}
https://{account}.app.box.com/v/{custom label}/file/{file id}
This works fine for most users, however for some users clicking on those links will simply redirect them back to the parent folder where the custom URL was set (e.g. https://{account}.app.box.com/v/{custom label}) and not the target file or sub-folder as one would expect.
This behavior appears to only affect users who are existing collaborators on the parent folder directly. Users who only have access via the shared vanity/custom URL are able to navigate to those nested links just fine.
Is there a way to force Box to follow the link to the correct path? Or fallback to the standard URL pattern (e.g. https://{account}.app.box.com/file/{file id}) if the user is properly entitled to access it?