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.
378 results found
-
Add option to require classification before saving
Add option for enterprises to require users to classify a document before saving it into Box
1 voteThis is not currently planned at this time.
-
2 votes
-
Allow security classifications to hide content if the viewer is an external collaborator
In addition to the classification level impacting sharing permissions, include the option to hide/block files from external collaborators in the folder
5 votesNot currently planned at this time.
-
Expire individual collaborator access from folder after x days
More granular than unsharing the entire folder
2 votes -
Reduce considerable increase in file size when watermarking content
Expected behavior that watermarking files will convert files to pdf upon download (if the user is not a collaborator) and greatly increase the file size.
1 voteThis is not currently planned at this time.
-
1 vote
This is not currently planned at this time.
-
49 votes
-
Refresh Tokens coordinating with IdP Requirements
We would like our Box refresh tokens to align with our IdP requirements.
We use Azure (https://docs.microsoft.com/en-us/azure/active-directory/active-directory-configurable-token-lifetimes).
Azure supports configurable refresh tokens. Can/Will Box configurable refresh tokens eventually respect these IdP refresh tokens?
2 votes -
Configurable minimum TLS level for communicating with our tenant
We want a means to force TLS 1.2 in our environment for both internal and external users. We can control our managed users, but it does leave some external users potentially using a lower TLS connection.
1 vote -
1 vote
This use-case is covered by using IP whitelisting on the API. Let me know if I’m missing something.
-
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).
78 votesNot currently planned at this time.
-
Watermark on Download when user has View Upload rights
We need users who have Viewer Uploader rights to always have a document watermarked on DL. According to the ACL, Viewer Uploaders download without the Watermark.
3 votes -
KeySafe HSM Support in Azure
We would like to also leverage the same Azure relationship for key management.
2 votesWe do not have plans in the near term to add support for Azure KeyVault.
-
1 vote
-
Device Trust separate desktop and 3rd party apps
We're trying to limit Box to managed devices. We enable DT on webapp, deploy Box for EMM, but when we try to open/edit a file in iOS Office, DT considers it a 3rd party app and blocks it.
Decoupling the two would leave the desired state of blocking webapp on unmanaged devices, controlling mobile through EMM, but also allowing editing in apps as desired on that managed device.
0 votesNot currently planned at this time.
-
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.
136 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.
-
Require 2FA for certain content only (not globally)
Force 2-factor / MFA based on the type of content, folder, user. etc. - natively in Box or support this functionality through IdP
11 votes -
Allow admin to disable external password
Instead of being able to only "reset" the external passwords, we want to block the ability for users to use/access their external passwords.
4 votes -
Suppress Notifications - Expand Scope to Suppress In-App Entries in the Updates Feed & Access Stats (for DLP & CASB Integrations)
Services (like DLP and CASB partners such as Netskope and Skyhigh) that use the Content API to scan Box content have the ability to suppress email notifications that would normally be generated for various activity (such as downloads, etc.). This is great as the activity from these services should be transparent and not exposed to the end user.
However, the Suppress Notifications header currently only applies to suppressing email notifications -- these entries for activity from these API-based services still are exposed in-app to end users on the Updates feed and in other locations such as Access Stats.
REQUEST: Expand…
10 votesNot currently planned at this time.
-
Restrict downloads from IE Browser
Right now, any user can from IE browser right-click and download an image/video, even when the shared link or collaboration level through which they are previewing is restricting downloads
1 vote
- Don't see your idea?