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.
68 results found
-
Read only metadata templates or values
The ability to set metadata on files and have it be read-only (aka not editable by end users).
4 votes -
Support deleting the current version
Currently there is no way to delete the current version or head of the version history. The only way to achieve the same effect is to promote a previous version and delete what was once the current version.
3 votes -
Preview of multi page illustrator file only shows the very first page
Currently, Box Preview for illustrator files only shows the very first page even the file contains multiple pages.
4 votes -
I am interested in being able to specify more than one redirect URI when configuring a standard auth app. They
Specifically, is this possible using regex?
1 vote -
Enable remote uploads with Box API
Allow remote uploads with our upload API. OneDrive and Dropbox allow this method.
Dropbox: https://www.dropbox.com/developers-v1/core/docs#save-url
OneDrive: https://docs.microsoft.com/en-us/OneDrive/developer/rest-api/api/driveitem_upload_urlWe would like to upload files from external services directly and do not want to download the file to the client. Being able to upload files directly from external services will avoid deduplication of files.
4 votes -
Improve experience of GETting all users for large enterprises
Large enterprises will often run nightly jobs to get a list of all users to sync w/ their own AD or for other purposes.
It would be nice to be able to get the entire population via a single API call (say, return a link to a csv file or a .zip of several csv files) or at least increase the limit. For customers with >50k users, it can be painful to make many API calls to get the whole list of users.
4 votesWe do not currently plan to provide all users via a single API request. For nightly synchronization of large user populations such such as the one described in this request, a more appropriate method would be to request relevant user and group events for that day from the enterprise events API and apply the changes there. When using this strategy, a full synchronization should only be required initially and in the case of some corruption or drift between the two systems.
-
Create Persistent Access Tokens
We want to embed a folder into our sales portal. We want our users/partners to be able to search within the folder.
We don't want to manage a separate code repo just for generating a downscoped token. Would be great if Box could support downscoped permanent tokens to cover these use cases.
We cannot search with in a folder with an embed widget.
1 vote -
Disclose Box service host names via API
Open up Box host names via API so that a customer's proxy server can automatically fetch our end points and digest it in to their solution.
There is a partial list available on our community page but it is not complete and difficult to fetch programatically.6 votesThank you once again for the feedback. We have evaluated the feedback but don’t think will have anything meaningful to share in the next couple of quarters.
Meanwhile, we will continue to keep our ear to the ground for additional feedback, and let you know if anything changes on our side.
-
Allow Recents to be filtered via API
Currently Recents is implemented globally across all Box content the user has access to. Ideally, Recents could be filtered to some ancestor folder IDs (like Search is) to show Recent items only within a particular folder.
The use case is a custom application which is integrated with a company's primary Box instance. A custom app wanting to leverage the Recents feature does not have a way to get Recent items relevant to just the application content.
1 vote -
Add folder upload support to UI Elements
Currently, Content Uploader UI Element only supports uploading files. We want the ability to expand that functionality to folders.
3 votesGreat suggestion! We’ll look into it.
-
1 vote
-
Expose the functionality for auto-deleting folders and files on a specific date via the API.
Currently, the web app has a file/folder setting in which a folder or file can be deleted on a specific date. We don't expose this service via the API.
We work with documents in packages (folders) and so when the documents expire and are deleted, we would also like the containing folder to be deleted as well. All of these packages are customer applications and so if not cleaned up then they will accumulate over time.
Right now, retention deals with files only, leaving behind the folders. The auto-delete on the folder is perfect for this purpose except that it…
3 votes -
Support for Collections in Content Explorer & Content Picker
Some of our use cases revolve around searching for specific metadata field or date range.
If UI Elements were able to be initialized with a collection, this would allow us to pass in a specific collection of files and display them easily even though those files may live in disparate folders.
2 votes -
1 vote
-
Return collaborated files (single file collab SFC) under a folder via API
Currently, there are two API calls surrounding getting a list of collaborations:
https://developer.box.com/v2.0/reference#view-a-folders-collaborations
https://developer.box.com/v2.0/reference#get-file-collaborationsHowever, say a collaborated file exists under a non-collaborated/private folder. Now say the folder is large. It would be less easy to get a list of collaborated files under this folder without iterating through every single file.
1 vote -
List and Grid support in the Content Explorer JavaScript Libraries
The java script libraries for content explorer do not appear to have an option to include toggle list/grid views which is available in the Box Drive experience.
4 votesGreat feedback – something we’ve discussed in the past and definitely want to do. Just not prioritized / planned on the roadmap currently.
-
Add a Webhooks v2 event trigger for restoring a file version
If a file version is restored (via the webapp or API), there is no associated event trigger that captures this action. If an admin is monitoring a file for changes, no webhook is triggered for this action.
7 votesThis is not currently planned. We will consider it with additional use cases and customer demand.
-
Make the digest header in the Commit Upload endpoint optional
Currently, Commit Upload endpoint requires passing a Digest header for the sha1 of the entire file.
Given that the integrity of each file part is already verified, consider making the Digest header in the Commit Upload endpoint optional
1 vote -
Enable API apps for select users
Right now, we can disable published APIs for all users, or enable them - we'd like the ability to restrictively enable.
3 votesWe currently do not plan to selectively enable or disable access to the Box API for specific users within an enterprise.
-
Adapt Annotations to achieve Accessibility guidelines
Box View does not conformance with W3C Web Content Accessibility Guidelines, version 2.0 (WCAG 2.0) at conformance levels A and AA - specifically, annotations can only be viewed around mouseover. This is a blocker for us as we work with public universities who have to meet those guidelines.
1 voteThank you for the feedback. It’s on our backlog and we’ll do our best to get to it as soon as we can.
- Don't see your idea?