Help shape the future of Box
Welcome to Box Pulse, our product feedback tool powered by UserVoice. Got an idea for how to improve Box? Share it with us and gather support or vote on other people's ideas. Your feedback is essential to informing roadmap decisions and shaping the future of our products. Thanks for joining our community!
See user guide here.
9818 results found
-
9 votes
This is a relatively expensive request for a modest payoff. We will be prioritizing other features on our roadmap.
-
9 votes
-
email address given in upload widget available form api call
when you upload a file via the upload widget a user will give an email address. the client would like to use the api to retrieve this in a api call. it does not seem to show in the description or in event steam nor as comment
9 votes -
9 votes
-
9 votes
-
9 votes
-
9 votes
-
Ability to customize download policy thresholds
Currently the policy thresholds are automatically set by our algorithms, and the policy is triggered on a per minute rate basis and one hour time window. This has caused alert fatigue for the customer because so many notifications are generated every few minutes based on these thresholds that they aren't able to update or customize.
9 votesWe will be looking at how to reduce the noise but it might not be through enabling customization.
-
Not all user settings can be controlled via our APIs.
Some user settings are missing from our APIs
eg: acknowledge collab invite, user avatar, mail notifications etc9 votes -
Ability to re-arrange All Files page on Drive, including external folders, for organizational purposes.
We would like to be able to move non-owned and external folders around for organizational purposes on their private Drive, without impacting the actual external/owner of the folder. For example: Company X shared Folder A with me at Company Y. I would like to move Folder A to my Company X folder in Drive so it's not clogging my All Files page (without this impacting Company X's folder).
9 votesThanks for the suggestion! We’re looking at ways to improve content sprawl in the future on Box Drive. We’ll consider your suggestion, along with other options, to help solve this problem.
-
Display pop-up when opening a locked file.
The lock icon is small and users can overlook this and try to edit the file without knowing that it is opened read-only.
9 votes -
9 votes
We currently do not have this planned on our roadmap, though we want to recognize that content sprawl is an issue and we are working to address it! Please keep the feedback & use cases coming to help us prioritize this in the future!
-
9 votes
We evaluated this previously, but have decided not to make changes yet given the user experience tradeoffs. If we get more requests of this, we can re-evaluate.
-
9 votes
Thank you for the feedback! This is not currently a priority on the roadmap. That said, we will continue to monitor and revisit based on user feedback in future planning.
-
Pass pictures or thumbnail images via SSO
Request: pass up the "thumbnailPhoto" attribute out of AD (picture in hex form) to Box.
9 votes -
Improve event information on shared link changes
When running Reports > Usage Logs > select all for "File Sharing" in the Admin Console, you currently only see that a user modified a Shared Link access level. This new feature would allow admins to see what access level the Shared Link was prior to and after the change.
This is important if an admin wants to know how accessible the content was when the Shared Link was initially created and shared.
9 votesNot currently planned at this time.
-
9 votes
-
Prevent LFO from occurring due to Box Relay
When running folder actions (copy/move/delete) in Relay workflows, if the source or destination folder contains a large volume of content, that folder may become subject to LFO, causing files to be locked and preventing other users from accessing them.
Therefore, when a user attempts to configure a flow with a folder that could be subject to LFO, we want to prevent unexpected LFO by clearly indicating on the flow creation screen that the workflow cannot be created due to LFO—for example, by displaying an error message or making the folder unselectable.
〈Box RelayによるLFOの発生防止〉
Relayのワークフローでフォルダアクション（コピー／移動／削除）を実行する際、コピー元またはコピー先のフォルダに大量のコンテンツがあると、そのフォルダがLFOの対象となり、ファイルがロックされて他のユーザーがアクセスできなくなる場合があります。そのため、LFOの対象になり得るフォルダをフローに設定しようとした時点で、フロー作成画面でエラーメッセージを表示する、または該当フォルダを選択不可にするなどの対策により、「LFOの影響で当該ワークフローは作成できない」ことを明確にし、想定外のLFO発生を防ぎたいと考えています。
8 votes -
Redundant Shield alerts
Box Shield should be able to recognize when the same file or file set appears in multiple locations and treat it as a single item, rather than generating duplicate alerts across each instance. This would allow users to acknowledge (or dismiss) an alert globally—once for all occurrences—rather than having to clear it separately for every flagged file.
8 votes -
The upper limit on the number of file requests that can be "bulk deleted"
Due to Box's specifications, you can delete file requests all at once using the following steps.
However, if you try to delete nearly 1,000 file requests, you'll receive the error message "Failed to delete link." The following steps prevent you from deleting them.[Admin Console > Content > File Requests > Select multiple file requests > Click the trash can icon that appears]
For security reasons, we need to periodically delete large numbers of file requests to prevent unnecessary requests from being available for a long period of time.
However, currently, the only way to delete nearly 1,000 file requests…8 votes
- Don't see your idea?