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.
9665 results found
-
Collaborators Page - Add 'Common Folders' Column Back to Page
In Legacy, the Collaborators page had a column called "Common Folders" that told me (as a user) which folders I was collaborating in with the given user.
In Amsterdam, this column was removed, meaning the page only tells me WHO I'm collaborating with, but not WHERE I'm collaborating with them (aka in which folders)...which makes the page FAR less useful.
REQUEST: Add the 'Common Folders' (or something similar) column back to the Collaborators page so that the page can tell me both
1. Who I'm collaborating with across my entire account
AND
2. Where I'm collaborating with each user (aka…7 votesInteresting feature request! However, we’re not able to prioritize it at this time due to competing priorities.
-
Upload Policy Type for folder locations
'Upload' Policy Type does not provide the option to apply at a folder level. It would be ideal if all policy types had the option to apply it to specific folders.
3 votesWould love to understand the use-case more on this one.
-
Add ability to trigger email confirmation when adding an email alias from blacklisted domain
Example: gmail.com is a blacklisted domain. If an admin tries to add a gmail.com alias for a managed user via the API, the call will fail with a 400 response.
2 votesThis request is not on our short-term roadmap. We will update you if anything changes.
-
Granular permissions per user for sharing public links/classified documents
The administrator should be able to set the default classification for all new documents (e.g. For Official Use).
Each user should be able to set their own default classification (which will override the system setting (e.g. Classified).
Each user should be able to change the classification for any new or existing document where she has sufficient rights. For existing documents, she should also be able to select multiple documents, and then change the classification for all those documents in one go.
1 voteDefault classification label is not planned because it could be misleading to end users. However, to address the concern of content being leaked before it is classified, you can create an access policy applying to “All content without a classification label” in Box Shield.
-
15 votes
This is an interesting feature! However, it does not have enough demand in order to be prioritized.
We are happy to reconsider with additional feedback.
-
True 'Select All' - Expand 'Select All' Beyond Just the Current Page of a Folder
REQUEST: Add an option for 'True' Select All such that when a user performs a Select All (via command+a / control+a), they have a new option to also select all items in the current folder, not just the ones on that current page.
BACKGROUND: When folders have a lot of items, there can be many pages and pages of items. The webapp's current 'Select All' functionality ONLY allows users to select all items from the given page (which is only 20 items for most users since the 'items per page' default is 20, though users can manually increase it to…
7 votes -
Search - Allow KeySafe Customers to Manage Their Own Search Index
Customers would like the ability to modify the Box search service to point to a customer specific index from within the Box UI since KeySafe disables 10k character capabilities.
9 votes -
4 votes
-
0 votes
-
Differentiate between Create Files and Create Folders in Collaborator level permissions
For certain cases, we want to be able to allow internal and/or external collaborators to be able to upload/create a file but NOT be able to create a new subfolder.
0 votes -
Usage Logs and Admin Events don't report version reversion
ITEMMAKECURRENT_VERSION is a Standard User Event in the API but doesn't show up in Usage Logs or Admin Events.
When a previous version of a file is promoted as the latest version, we do not receive an enterprise notification for that.
If we quarantine a file (create tombstone as say version 2) and the user makes the v1 version as latest (v3), then the event received is of type user event and not an enterprise event, which makes us not be able to process such a change.
1 vote -
0 votes
-
Ability to change the default attachment setting "Use Box when attaching local file" upon or before installation/deployment
Instead of needing to change it for each user.
0 votes -
0 votes
-
Only allow managed users/collaborators of an enterprise to log into customized login page
Ideally, users who use their subdomains to login should be our collaborators and users only.
0 votesThank you for your note! This is a relatively narrow use case. We will reconsider with additional customer demand.
-
Folder Level App Integration in Developer Console
Is there any plan to allow developers to give folder access to Web App integrations without having to request a special permission from Box?
In the current process, Developers can enable the context menu for folders to present integration features, but to do so they must contact Box first. "Send a request to Box for pre-approval to build a folder-level integration."
We would like the ability to add folder level integrations via the Developer Console without having to contact Box Support.
0 votesThanks for the feedback. We don’t have anything meaningful to share at the moment, but will let you know if and when that changes.
-
0 votes
-
Report to view amount of content synced for each user
This would be highly beneficial for admins to see if users have too much content Syncing. In addition, admins can keep their users from syncing too much content and having sync issues.
0 votes -
1 vote
This is a non-trivial change to our architecture and user-experience. We will consider this as we review our organizational structure for content within Box.
-
Please expand user name character field limit from 50 to 100 words.
Global companies need local characters such as Japanese and English for name field and 50 is short for some names
4 votesThis suggestion is not under consideration for the current or future roadmap. Once we see more traction from customers who want are requesting this functionality, we can revisit our decision.
- Don't see your idea?