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.
258 results found
-
0 votes
We do not plan to suppress these updates. However, we will reconsider if we get additional feedback from other users.
-
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.
-
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.
-
Allow watermarking to reveal External ID, as opposed to randomly generated App User Email
This would connect the viewer to a legal obligation through the document experience.
0 votesThank you for the feedback! We’ll add this to our backlog, and get back when we have further updates.
-
Support image tags in Metadata preview.
Currently images from external sites are not supported.
1 vote -
The ability to pass unique request ID to each service request to assist with debugging
We want to pass a unique request ID to Box so we can easily track and debug any requests that fail within their application.
0 votes -
Add Managed Domains list to API Endpoint
We would like to be able to make an API call to retrieve the list of managed domains for or Enterprise. We can only do this from the Admin Console today.
0 votes -
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.
-
Expose Box Server Time for setting JWT exp claim within expected values
Currently, there are a few different places that developers can use to sync the time of their requests which can lead to some confusion/issues with properly setting the exp claim when generating a JWT assertion.
For example, pool.ntp.org offers up a time that's ~25 seconds ahead of epochconverter.com (where support currently suggests that folks sync their time from).
Exposing the "current timestamp" somehow, or syncing up with a framework that allows users to be in sync with Box time will allow for fewer questions/issues with the JWT claims process.
0 votes -
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.
-
0 votes
We don’t offer an API endpoint for these types of queries today, so it’s not possible to add.
When you create a user that already exists, you get a 409 error code returned – user already exists. Is this sufficient?
-
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.
-
Add offline functionality to iOS SDK
Offline functionality is already available through the Box for iOS app but it's built on the app level.
Developers are interested in using the same logic used by Box instead of writing their own.
0 votesOur customers tend to have different requirements for an offline feature. We’ll monitor demand and re-evaluate.
-
Pass Basic Auth (Authorization Header) to Client Callback URL & Preliminary Callback URL when Both are Present
Using an API-based web app integration, from the "More" menu in the web app, if developer requires basic auth to complete the request, authorization header is only passed to the Preliminary Callback URL and never the Client Callback URL - even if Client Callback is the only URL present.
Expected Behavior:
Allowing the developer to choose whether basic auth is required would imply that we would always pass the Authorization header with our requests so they can validate.0 votes -
0 votes
Good feedback, although, due to other priorities we will likely not be getting to this anytime soon.
-
Periodic replication of Sandbox environment with Production settings/folder structure
As we become more complex with usage of Box, we maintain Sandbox environments and are using it to test Governance Policies, integrations, and more.
Other SaaS providers (e.g., Workday) will push a replication of Configuration Settings (with an option for the customer to not replicate) from the Production to Sandbox environment. This helps keep the two in sync.
It would also be enormously beneficial if the folder structure and dummy users (not content) could be replicated into the sandbox environment for a better sense of how changes will affect Production.
13 votes -
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.
-
Request to Add Overwrite/Version Functionality to File Copy Operations via API
Currently the only way to add a version to a file is to download it and upload the new version with the If-Match header.
We are archiving files when a new file version is uploaded to a "main" folder, and to do that we have to download the existing version to our server and then generate a separate request to upload the file.
Ideally, we would be able to combine the requests into one - a COPY (https://box-content.readme.io/reference#copy-a-file) that can overwrite an existing file in the destination folder if the appropriate etag is supplied during the copy request.
5 votesThis is not something we will build due to other roadmap commitments.
Alternatively, you could always upload latest version to “backup folder,” delete file from “current version” folder, then copy “backup folder” version to “current version” folder.
This will get you 100% version history in backup folder and avoid the need to download & upload the file a second time.
- Don't see your idea?