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.
221 results found
-
New field that indicates whether that specific folder has any collaborations of its own, i.e. not inherited from a parent
We have a big problem on our hands when it comes to obtaining all of the collaborations a user created inviting others to their content. There simply is no quick way of doing this, especially on users having massive folders. We discovered that the GET action on the /Folders endpoint has an available request field called “hascollaborations” which indicates whether the folder has any collaborations. I really hoped we could leverage this to cut down on the unnecessary calls to the /Folders/{folderId}/collaborations endpoint if the folder being iterated over had no collaborations, but unfortunately it returns “true” even if…
1 vote -
iOS SDK
'Mark for offline' capability in SDK. Either read-only or edit-sync is a critical requirement for field worker use cases.
With current SDK developers need to build this which is expensive and risky.
1 vote -
Doc feedback
The layout and the padding feels weird. This applies to both the navbar as well as the content.
1 vote -
Start accepting an array of strings as 'aud'
Hi. I'm trying to use jwt authentication with box. I'm new to JWT. The library I'm using seems to send the 'aud' value as an array of strings, and looking at the specification for JWT, that's what it's supposed to send. This doesn't work with box though, box only allows a single string as 'aud'.
1 vote -
Could add "item_execute_integration" to scopes page.
could add "itemexecuteintegration" to https://developer.box.com/docs/scopes#section-application-scopes ?
I think the developer gets angry or confuse.
1 vote -
Add length of field to API documentation
It would be nice to explicitly mention the length of some of the fields. In our enterprise account all the users had 10-digit UIDs, so I thought that was the standard length, but we had some users with preexisting lite accounts rolled in and a few of them had 8-digit or 9-digit UIDs. I see now that the example UID provided had 9 digits, so my bad there, but I initially just looked at the 'id' attribute under 'user object' to try and find the length and it would be nice I think to have something like 'id / string…
1 voteThanks for the suggestion. We generally don’t provide lengths for fields unless there is a concious decision to define a specific length or range as a contract. Given that the type of field for user id is a string, the fact that user id values ranged from 8-10 digits is an implementation detail, not a guarantee.
-
New event type for modification of upload-email properties
A new event type for modification of upload-email properties, such as access type (in addition to the existing enable/disable events for upload email functionality)
1 vote -
Improve CORS whitelist wildcard support
I would love to be able to use wildcards in CORS with a little more specificity. In particular, for review apps on Heroku, you will have a url that is auto-generated for each pull request, so something like http://my-app-dev-pr-523.herokuapp.com. I would like to be able to add http://my-app-dev-pr*.herokuapp.com to the CORS list but it currently flags that is an improper URL so I have to do the much more broad (less secure) http://*.herokuapp.com
1 voteThis is not currently planned
-
Folder upload endpoint for API
The ability to copy a folder from a local machine and upload it via the API
1 vote -
Rollback option when db crash
After creating folder or uploading files into box there will be chance of occuring backend database crash or lose connection between datasource . In this case we should roll back our transaction(like revert folder creation or file upload).
1 voteMany actions in both are idemptotent and can be safely retried. For those which are not, it is the responsibility of a client to implement transaction guarantees if required. There are common patterns for this such as the two-phase commit and SAGA pattern. If there is more information for a specific capability that is required to faciliate these, please add that to the comments.
-
Expose ability to restore versions of files via API
It would be beneficial to expose this information via API when interacting with file versions to enable this for App Users via a portal
1 vote -
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 -
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 -
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 -
1 vote
This is not planned.
We don’t see enough customer demand for this yet, and supporting every additional content type takes a significant amount of engineering time and effort.
-
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.
-
Support image tags in Metadata preview.
Currently images from external sites are not supported.
1 vote -
Thumbnails should be able to be requested in a batch.
You should be able to download all thumbnails for the items within a folder.
1 voteGreat suggestion – we don’t have any plans to do this anytime soon, however.
-
1 vote
-
1 vote
- Don't see your idea?