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.
232 results found
-
Event stream missing a share_level or similar attribute
By pulling the events with the API and comparing them, it appears both are missing a share_level or similar attribute. This attribute is also they can detect when users share files outside the company.
3 votes -
Allow for one-off permissions changes to individuals in a group.
When inviting a group to a folder, we would like to have the ability to give a different permission to just a specific member within the group. Currently if a group is invited to a folder, all members will get the same permissions. Te only workaround is invite the indiv user separately. However, this is not an officially supported functionality of Box.
2 votes -
Enable SSO through OAuth2 and not only SAML 2.0
We use an in-house IdP. This IdP leverages OAuth2 OpenID. It does not use SAML 2.0
Therefore we need Box to have the capability to enable SSO through OAuth2 and not only SAML 2.0
6 votes -
The 'Edit User' event does not show which parameter has been edited
Any changes to a user that are displayed in the User Activity report or event log just display 'Edit User'. This means that changes such as name, email, device pinning, enable box sync, share contacts etc. just display as 'Edit User'.
1 vote -
We need a Box role that does not allow the "view item list in folder" function.
There is a use case where external people are using Box to upload content. The folder where they upload in is a shared folder. Even with the role of uploader, people still can see what others uploaded.
Currently we worked around this problem with an automation that moves the file as soon as it is uploaded.
Can you build another permission level, or a selector for disabling the invite items in folder capability ?
1 vote -
Decouple the requirement for a SINGLE UNIQUE email address as a primary dependency for accessing the Box service.
Practical example: Slack allows the same email to appear in their system multiples times, accessing separate Enterprise/Team sites. See login here, which prompts for the unique URL for login.
2 votes -
Request for a web page that better captures domains AND IP ranges for Box, including an XML feed to subscribe, changelog, etc
Can Box emulate Microsoft and create a web page like this. Originally (about 3 years back) this page was bare bones and just contained services, urls and IP ranges. Network admins had to scrape the page to grab the IP ranges they needed and use IFTTT. They have since added an XML feed and a way to subscribe to changes. They post updates once a month or so before they go into effect. Every bit of info on this page (including placement of links) has evolved based on user/admin feedback. https://support.office.com/en-us/article/office-365-urls-and-ip-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2
1 vote -
1 vote
-
Ability to enable or disable "Automatically accept collaboration invitation" through API
We want to govern collaboration policies and disable this option through API
4 votes -
Viewer does NOT see Download button in Context Menu ('...' menu) nor in Action Bar when multiple items are selected
.Given that Viewers have the ability to download watermarked files, the Download button should appear everywhere as normal. This ticket is to add the Download button in the following two locations for Viewers:
* File list context menu ('...' menu)
* Action bar when performing a multi-select2 votes -
Allow authentication across multiple Box applications through one "passport"
There are many ways in which to authenticate to Box through Mobile, Sync, Drive, Web etc. Is it possible to have a single unified check wherein we could then open any end-point for Box to authenticate?
1 vote -
FTPS access for collaborators to a subfolder rather than through root level credentials
Use Case: Research studies using radiology images that come in large image sets from tools like MRI scanners which can have hundreds to thousands of images which make it impossible or impractical to use the web interface.
However, they are still external collaborators who should have the ability to send files.
2 votes -
Direct DICOM upload endpoint desired
Our admin would rather not use the DICOM import tool to upload DICOM images to use with the Viewer (and they don't have a PAC server). We're also uploading non-DICOM files that are relevant to the study, so having two separate UIs for an upload is inconvenient.
1 voteThank you for this request. However, we will not be focusing on this feature this year. We will revisit this with additional demand.
-
Single File Collaboration - Preview Permission
The current implementation of Single File Collaboration is lacking the Preview permission.
As organizations transition to the single file model, the functionality should align to the folder permission model as closely as possible to maintain ease of use and consistency within the application.
The current behavior is to set the permission to Editor and require the user to navigate to multiple windows to downgrade rights to Viewer. The Viewer role still allows content to be downloaded to a local machine.
We request Preview rights so that functionality like Watermarking can still be leveraged and to minimize data spillage.
6 votes -
Standardize or lock down naming conventions
The ability to set restrictions on file naming conventions would greatly help admins query their data.
5 votes -
1 vote
-
Break waterfall permissions
Allow for restricted permissions within a shared folder (so permissions are not inherited from the parent folder)
411 votesWe understand the request, but unfortunately this is not on the near-term roadmap.
-
Support Gov Cloud on Azure
This is in addition to AWS
1 voteWould love more detail on this request.
-
FTP not available to external users for Enterprise accounts.
Currently FTP for Box is only available to Business and Enterprise accounts for bulk migration of data. It is not available for Personal accounts (Free or Pro).
This is problematic for Enterprise users that have external vendors, partners, customers (collaborators) that need to upload a large data set to their Enterprise account through FTP.
Since these external collaborators are Free users, they do not have access to FTP but are still collaborating with us.
REQUEST: Add support for FTP uploads for external collaborators that are specifically collaborating with a paying Enterprise Box account?
8 votesThis is not currently planned. We will reconsider this with additional demand.
-
Route files to a specific user via the embed widget
We would like to be able to pick what user content goes to with one widget.
2 votesI think this would be better addressed with platform elements. This way, you can build out the exact functionality you seek.
- Don't see your idea?