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.
8694 results found
-
Add QoS ability with Sync
Throttle incoming and outgoing traffic in Sync 4.
0 votesThank you for the suggestion! This is not currently planned. We will let you know if anything changes.
-
Add "Cancel" Button to dialog window when removing a folder from Box Sync
When deleting a folder through Box Sync, a confirm deletion window pops up and warns the user that deleting the folder will remove it from all collaborator accounts but unsyncing will remove the folder from their computer only.
It then only gives the option to click the buttons "unsync" or "delete". User thinks there should be an option to cancel to better account for user errors.
0 votesThank you for the suggestion! This is not currently planned. We will let you know if anything changes.
-
Disable install of Box Sync on a server
We have Box Sync installed on a server (Windows Server 2008 R2) which is not supported.
0 votes -
0 votes
This is not planned for development.
-
Enterprise site for external collaborators
We'd like the ability to offer external collaborators a specific domain or sub-domain when collaborating in our company's folder.
Intent is to better adoption with agencies that are hesitant to allow our Box account on their networks as it currently means that have to all All-Box on their network (e.g. app.box.com)
0 votes -
Allow Viewer permission when inviting a collaborator through Single File Collab
Right now, editor is the only immediate permission available, but users can be changed to "viewer" after the fact. It's just an extra step.
0 votes -
Disable Single File Collaboration on Enterprise setting
Just like Box Notes, Single File Collaboration should On or Off in Enterprise settings.
0 votes -
Longer Custom/Vanity Names
We need to have Longer Custom Vanity Names do to their folder structure/naming convention that they use.
0 votes -
Separate folders I own from those I am collaborated into
Either through filtering or separate pages on the All Files page
0 votes -
0 votes
-
0 votes
-
Allow content shared via shared link (not just an attachment) to be uploaded when "emailed to folder" in Box
As we transition away from attachments, shared links (from Box or others) are being emailed.
Request: Upload to folder when the user sends it with the "email to folder" address.
0 votes -
Ability to choose default shared link access security level on a per user basis
We have the default shared link permission to people in the folder or file.
We would like to change that default for one user to be "People in your company" for example.
0 votes -
Ask people accessing shared link to put in name and email
Our admin wants to know who is opening the shared links
0 votesThis is not currently planned for development. We will consider this with additional customer demand.
-
Invite Collabs Pop-Up: Add Optional 'Send notification?' Checkbox
Currently in Box, when a user uses the Invite Collaborators pop-up to invite someone to a folder, an invitation email is always generated for the recipient. This is good in some scenarios, but creates a lot of email noise in many other situations where the inviter really doesn't want the recipient to receive an email notification.
Google Drive provides a 'Notify user?' checkbox on their 'invite' pop-up that allows you to 'silently' add the recipient to a folder without sending them an email notification.
Request: Add 'notify users?' checkbox to the invite collabs pop-up
0 votesThis is not currently planned for development. We will consider this with additional customer demand.
-
0 votes
We do not planning on making changes to the basic permission structure at this point.
-
Implement controls to prevent users with free SFDC accounts to link with corporate Box accounts
Our Box tenant allows integration with SFDC, a user can link their free SFDC account. We would like to see better controls which prevent access to Box via non-approved SFDC instances
0 votes -
Provide more flexibility with visibility of SFDC folders in Box
Even if a user is invited to the root folder of the SFDC folder tree in Box, they are unable to view all of the subfolders unless the user has previously accessed via SFDC first.
To make sharing of SFDC content with other non-SFDC users easier, we would like to have this behavior changed.
0 votes -
0 votes
This is not planned for our current roadmap. We will let you know if anything changes.
-
0 votes
This is not planned for our current roadmap. We will let you know if anything changes.
- Don't see your idea?