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
-
Allow for creation of custom permission levels (roles).
We want to share files to an external collaborator, but want to restrict the download and allow editing.
Request: Add new custom roles and assign them preview, link, edit, and they would have to use our Office 365 to modify within Box?
11 votes -
0 votes
-
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.
-
0 votes
-
0 votes
-
1 vote
-
Support Gov Cloud on Azure
This is in addition to AWS
1 voteWould love more detail on this request.
-
Box for Azure Stack
Architecture support for Box deployments within Azure Stack
0 votes -
Error message to transfer ownership when only admins are allowed to create or delete level 1 folders
With the option to restrict folder creation at level 1 to admin, if the admin give the ownership to a user and then this user try to give the ownership to another user, she can perform the actions and finally get the message "There was a problem making xxx the owner of the item. Please try again or refresh the page."
The message should be revamped or the user should not be able to start giving ownership.
0 votes -
0 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 -
Disable Single File Collaboration on Enterprise setting
Just like Box Notes, Single File Collaboration should On or Off in Enterprise settings.
0 votes -
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 -
Rsync-like upload of file differences
Sync differentials, not the entire file. This is similar to Rsync functionality.
0 votes -
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 -
remove image files from people's HTML email signature
The ability to have small image files removed from people's HTML email signature. It would be nice to have a way to filter these out or add a workflow that deletes these.
0 votes -
0 votes
-
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.
-
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
- Don't see your idea?