We have systems integrating with folders on Box.com. These functions either provide workflow timestamps, or move files from folder to folder. In order for these integrations to work seamlessly, folders cannot be accidentally or purposely renamed.

-Display the number of search results hits
-Save search results (query and results)
-Run search again and show differences since the last search (this is helpful to see what's been added or removed since the last time the search was run)
Include all filte

Users should be able to run a report of any folder they are an owner or co-owner of to see the list of external collaborators. This would be nice so they could periodically review it and remove stale collaborations.

Create a report showing all locked files.

I would like an additional (apart from grey, blue and yellow) color (red?) for folders that are shared with external people.

We would like to be able to custom color code their folders.

Please, please, create a separate view on the web to just showcase files and folders that are shared with me; rather than files/folders that are of my ownership. Similar to what other file storage providers offer, like OneDrive.

We accidentally deleted a root level folder for millions of folders.

This may be done by locking the folder, where it could allow users to create/edit/delete the contents within the folder, but not allowing the locked folder itself to be rename/moved/deleted.

This may also help Box Sync (and possibly Box Drive) users, as many Box Sync users often delete the top level folders by accident.

As a user, I've likely been added to numerous folders that I do not need to access daily or even often, but still need to remain a collaborator in. A 'hide folder' option may help with this, where a user would be able to hide a folder form their All Files view, but the user would not actually be removed as a collaborator from the folder. They would then be able to access all 'hidden' folders via a menu option on the left rail (or elsewhere).

HTML files appear to no longer be rendering the HTML. Instead, they are just showing me the content of the HTML code.

Users with multiple Box accounts (e.g., personal, work, etc.) should be able to sign onto all their accounts and be able to quickly switch between the accounts. This could be similar to account switching for Google services, Dropbox, etc. Currently it is very cumbersome to do this. Box has already implemented similar functionality as part of the Box Android app.

Please consider improving this within Amsterdam

There are a number of use cases that can be supported by separating the Move / Copy button into unique buttons:

1) Folder or file templates: Users with Viewer access (can download) should be able to COPY a file or folder elsewhere. Currently this is not supported -- the user must download, which loses BoxNotes and Bookmarks.

2) Separating "records" from reference material -- If Retention is set on a file, the user may want to copy a version elsewhere that is not subject to Retention

Customer is requesting the ability to change the default collaborator level upon adding a new collaborator. The default level is now Editor, but the customer wants to set the default to Viewer Uploader or something else to protect against provisioning too much access to users.

Additionally, the customer wants to collaborate with many customers (external users) and would like to provision appropriate access to those users (preferably not Editor).

Box currently doesn’t support the notion of file sensitive file and directory names like Linux does, so backups to Box, for example with rclone, lose similarly named files that only vary in case.

For example, you can only have File1.txt and file1.txt, but no both in Box.

In comparison, there’s no such limitation in Google Drive and Linux file systems, for example.

Please add support for file name sensitivity.

The customer would like an ability to rename favorites file/folder from sidebar.
It’s so convenient for user. he’d like such as bookmark bar of browser.

If i have a folder in the following structure
/1/2/3
and I invited User B to Folder 3
When User B access Folder 3 he would have no idea that folder 3 is actually in the path /1/2/3.

On Box platform however, there is an optional parameter "canviewpath",
while this can only be used by the folder owner it adds to ability to let collaborator see the folder from root to target folder.