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.
222 results found
-
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.
5 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)
380 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.
-
Extend box' capabilities with client protocols.
In banking a lot of external content is accessed: reports from Bloomberg, other financial information, etc. Most of these pieces of information reside on FTP / SFTP / FTPS / Webdav systems.
It would be nice if box could be extended in such a way that users have the possibility to access this content from within box. The idea is to have a new folder type (external content), which can then be configured with a connection string, user name and password. Users could then just browse those external sources from within box.
Ideally a copy and paste should also be…
1 vote -
Add Data Center in China
We have data residency requirements for China.
11 votesThis is not planned for the short-term roadmap. We will reconsider with additional customer demand.
-
Trashed items: include details about the deleter
When a user makes a GET call for all trashed items, the response does not include details (name/user ID) of the user who trashed each item. This is inconsistent with the Web App view of a user's trash. The Web App view includes the name of the item deleter.
5 votes -
Usage Logs - Better Reporting when Shared Link Permissions are Changed
Right now you can see WHEN a user changed the value of a shared link (closed to open for example) but not to what, so if a link was changed, we have to guess as to what level of access. This seems like a gap security wise and may lead to us shutting down shared links.
14 votesWe are still looking to understand what sort of information customers would like to see in the Usage Logs regarding Shared Link Permissions.
-
Introduce a combination of version labels and version dependent permissions.
Compared to legacy ECM systems, versioning in box is limited to data states over time. There is no notion of a document lifecycle attached to a certain version (WIP, draft, published).
The mandatory check in/out of legacy ECM makes the system very user unfriendly. However, it would be nice if we could somehow label certain versions. The list of labels could either be fixed, or user definable.
If we combine this feature with a new permission: "view documents with status published", we could now have one directory where people work on their documents, but external people would only see the…
1 vote -
The ability to perform advanced searches despite having KeySafe enabled.
They are open to, similar to the KeySafe concept, having a way to plug Box search into their own index.
8 votes -
Just in time User Provisioning / Licensing
The current way of licensing is old school. Instead, you could leverage Okta's just-in-time provisioning: https://help.okta.com/en/prev/Content/Topics/Security/Security_Authentication.htm?cshid=Security_Authentication_JIT#Security_Authentication_JIT
Then (with SSO required & on the fly), Box grants everyone in an org an acct after logging in thru SSO, they're auto-provisioned a Box instance, and a license is registered/"billed" to company.
1 vote -
Add "additional_details" to events endpoint for MOVE, COPY, RENAME events
Presently, security & events reports run from the admin console include "change details" for these events - essentially, what the prior state was before the event occurred. The events endpoint does not include these details.
Request to add this to the additional_details of an event as it's reported through the admin events stream for the MOVE, COPY, and RENAME events.
If RENAME, show previous name of the folder
If MOVE/COPY, show previous parent of the folder10 votes -
Receive notification when transfer of content is completed
When deleting and transferring content to another user and an error is thrown, it is not clear to the user when all the content has successfully been moved due to the error message thrown.
We would like to know when all the content has finally completed so we can delete the user without any concerns.
5 votes -
Set an expiration date on collaborations in a folder
Similar to how shared links can expire.
12 votes -
Option to Show Full Folder Hierarchy when Added Only to Subfolder
Right now, when collaborators are added to a folder, they are not able to see the folder hierarchy that is above the level at which they were added. This is great in many situations.
However, there are various scenarios where customers would like users to have the 'full view' of the folder hierarchy above.
13 votes -
51 votes
- Don't see your idea?