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.
388 results found
-
bulk manage Shared Links
Provide a way for all shared links in an account to have their permission levels / access levels / expiry dates modified in bulk, rather than having to change each one individually which is extremely time consuming for large doc sets.
179 votes -
Open Shared Link Controls: Default Password Requirements for Open Shared Links
REQUEST: Admin would like the ability to set a global control whereby all public/open ('people with the link') links must have a password.
Our current controls on shared links impact all 3 Shared Link permissions causing additional impact on the user experience.
149 votesInstead of “require password” security control, we intend to support “Require OTP” requirement for public links (via SMS, Email, or TOTP). I wanted to share where we are headed. We do not plan on delivering this ask as is, but we do intend to solve the security use case behind it.
Please comment if you disagree.
-
Collaborator Expiration - Include Co-Owner(s) in the Email Notification
Current Behavior:
--Email Notification - Sent to 'affected users' (defined as Folder Owner and the original Inviter, aka the person who invited in the collaborator who is about to expire)
--Ability to Extend Expiration Date - Folder Owner & Co-OwnersREQUEST: Add Co-Owner(s) to the email notification distribution so that they can take the burden off the folder owner (since co-owners already have the ability to extend the expiration date).
82 votesNot currently planned at this time.
-
Send a "here's how your items are shared" report to each user periodically
One of the most common sources of security breaches is due to a user inadvertently sharing an item more broadly or for longer than they intended.
A simple way to help limit those sorts of security breaches would be for Box to email every user a report periodically (configurable by the admin, but roughly monthly) that said "Here's how everything you own is shared with other people, and here's a link to the KB article that'll tell you how to fix it if it's not what you want", then showed a report of their folders, files, and shared links, with…
80 votes -
Support AD Conditional Access with Microsoft Azure
Please support AD Conditional Access with Microsoft Azure. It meets security requirements so easily.
And it is compatible for third-party apps by configuring SAML settings.I think that is not easy to develop Azure cooperation feature, but I require that.
63 votesWe're actively working on this request at the moment. We expect to support it in the upcoming quarters.
-
Shared Link Password Policy
Much like the default link expiry policy we would also like one specific to forcing passwords for shared links and preferably being able to define that policy with minimum characters and complexity.
Bonus would be passwords that are auto-generated and viewable by the creator of the shared links to minimize the need for external tools.
60 votes -
50 votes
-
49 votes
-
Add hardware token security for 2FA
Yubikeys and similar devices allow for hardware token security and are highly recommended. We want to implement it across devices (ipad, iphone, android, MacOS, Windows) and this must include Box
SMS 2 factor is considered very hackable and has been hacked many times.
How can we use Yubikeys with Box.com ? What are your plans on this?46 votesWe now have the ability to use TOTP for 2FA. In addition, admins can enforce TOTP for managed/external users.
We do want to support FIDO standards for 2FA in the future and will update this idea with more details once we have a concrete plan. -
Custom Watermarking based on metadata or manually.
Opportunity where main requirement was to distribute content to various locations, but add custom watermarking as they are published out. Typically with the location name content is publisehd to.
46 votes -
Allow the use of Linux devices as approved devices.
We had Linux based user using Box web console and as of the July update, they are no longer able to access Box. I would like to see Linx OS be added to the approved Operating Systems list in the Admin Console for enterprise settings.
45 votes -
SSO exception
Ability to have exceptions for SSO for specific amdin accounts/test users. Use case: there's a series of admin accounts we use that own folders/content in Box but aren't actual users. Now when we want to turn on SSO - we now have to have OKTA accounts for those accounts and test users, when we'd prefer to just do Box 2FA for those vs. SSO enabled for all
30 votesUnfortunately this is not on the near-term roadmap, that being said this is a very interesting request which we may consider in the mid-long term.
-
'Email Shared Link' - Add Reporting for the Recipient (Who the shared links were sent to)
When sending shared link emails (via the Shared Link modal -> Email Shared Link option) we do not report on who we sent the email to.
REQUEST: In the UI and Excel exports, add information on who the shared link email was sent to.
27 votesNot currently planned at this time.
-
Add granularity to shared link controls
Based on organizational requirements and the variance, there should be additional controls such as limiting the capability to create shared links (open Links) to Admins or designated personnel as an option. This would allow for greater granularity as some divisions within an organization may have a need to share publicly, while also securing sensitive information
23 votesFor now, we are focussed on solving bulk management issues with Shared Links.
Box Shield is an additional option for enforcing granular controls on content.
-
Natively generate QR Code for shared links
The ability to convert Box's shared link to QR code natively, instead of using unsecured free QR generating services
22 votes -
22 votes
Not currently planned at this time.
-
FIDO2 Phising Resistant MFA
Box only supports MFA and TOTOP options for 2FA external users. There is a need for FIDO2 (phising-resistant) requirements as an option for external sharing.
This process is not only secure but also user-friendly. There's no need for users to remember extra passwords or carry around additional hardware tokens. There is no need to install additional software; all the major browser support this out of the box. The device and browser do all the heavy lifting.
Per the updated guidelines from the National Institute of Standards and Technology (NIST), the requirement is that internal users must use phishing-resistant MFA, while…
21 votes -
Enforce parent folder collaboration restrictions on moved folders
Make sure that folder settings apply to all the subfolders. Currently, even if you restrict collaboration to within your company through folder settings, a folder that is already collaborated to external users can be moved into that folder. Right now, we don’t have the mechanism to check if a folder that is about to be moved is collaborated to external user.
21 votes -
Watermark is "too intrusive"
Coming from WatchDox, this watermark style is way too intrusive. It makes the file content hard to read. Ultimately, we'd like the ability to customize the style and content of the watermark.
21 votes -
Expose folder settings via API like "Restrict Collaboration" and "Hide Collaborators"
As far as I know new APIs are managed by platform team.
21 votesNot currently planned at this time.
- Don't see your idea?