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.
179 results found
-
Compliance & Retention of File Activity Comments
We are using the Activity section on each file to keep a running list of processing notes for each documents - ie invoice approvals, marketing and advertising review, etc. More granular control of comment governance would be very helpful.
For instance, including comments in permission settings to prevent a user from deleting comments, or include in Governance Admin Panel an option to disable comment editing. Comments should also be subject to the same retention requirements imposed on the file itself - ie if the file has a 5 year retention period.
Also, while there is a User Activity report that…
10 votes -
Reset Governance settings
JFE Steel like to reset Governance setting when Box turned on Governance setting again. JFE Steel set up upload policy when they had POC. Then they did not purchase Governance. When they purchased the Governance later, the setting the customer configured before became effective again. This confused customer. So, Governance setting should be reset when Box turned on the feature.
1 voteThank you for the suggestion! At the moment there is no plan to reset Governance settings. We may look into this in the future.
-
Custom Terms of Service - Archive of Previous ToS Text
Currently, when changes are made to the text in an existing custom ToS, Box does not save the original text that was signed off by previous users. Only the most up to date version of the text will be available in Box. I would like to request that, for compliance reasons, there's an archive of previous ToS available so it is clear which specific language each user has signed off on.
1 voteWe don’t have immediate plans to address TOS. We’ll want to see other feedback related TOS before determining if it makes sense to revisit.
-
1 vote
-
Support EU-specific patterns for upload policies
We would like to see options in upload policies for "If a document contains:" that are not just US-centric, ex: European Identification #‘s
2 votesThank you for the suggestion! At the moment there is no plan for this feature. We may look into this in the future.
-
Restrict Classification edits to Governance menu
A admin can access the Classification template in the Metadata page and delete values of classification. That makes errors. Classification should be only accessible via the Governance menu and not via the Metadata menu.
3 votesThank you for the feedback. This specific use-case isn’t planned at the moment.
-
Additional approval for large delete actions
We'd like the ability to add an optional multi factor authentication or admin approval while deleting files or folders above some specific amount data e.g 50 GB.
4 votesThank you for the suggestion! At the moment there is no plan for this feature. We may look into this in the future.
-
Apply policies to duplicate files
Identify duplicate files in Box, and apply any policies in place onto all duplicates
9 votesWill need to understand the use case more (e.g., examples of duplicates to understand customer’s definition of a duplicate, how a duplicate can be created, etc.).
-
Define version limits by user, folder or file
We like the ability to set the number of file versions per user, folder or file
6 votesHi, this is an interesting idea, however, we would be worried about the configuration complexity of adding differing version limits below the enterprise level.
-
Include all file names in expiration notices of retention policies
Retention notifications to include the name of each file (instead of just names of folders containing the files) that will expire in 14 days
18 votesWe are targeting a solution to be released in the calendar year 2024. Please reach out to learn more!
-
Warning when changing metadata associated with retention policy
Warn or prevent the user if they are changing a metadata value associated with a retention policy from a value with a longer ret policy to one with a shorter ret policy
4 votesThank you for the suggestion! At the moment there is no plan for this feature. We may look into this in the future.
-
Warning when moving files into folders with different retention policies
Warn or prevent the user if they are moving a file from a folder with longer retention policy to a shorter retention policy that the longer retention will still hold
8 votes -
Indefinite retention for top level, Finite retention for sub-folders
Ability to have an Indefinite retention policy as a top level folder and Finite retention policies on sub-folders. Sub folders should by default inherit from the parent, but if listed in another policy then the sub folder should be able to override the default
a. This would prevent having to have separate folder trees for Indefinite and Finite policies
b. The parent could be ‘Work in Progress’ and then just move to a sub folder…keeps the documents more logically organized by department
5 votes -
Use Box as governance layer for content outside Box
Ability for Box to function as federated content viewer (governance) - as some content will remain outside Box. Use Box as governance layer but not storage element.
4 votesWe do not plan to enable Box Governance as the federated policy layer across multiple systems at this time. However, it is possible to use the Governance APIs to enact this if you have another federating system.
-
Allow upload policy to move to folder instead of quarantine
instead of flagging/quarantine custom words/numbers with a policy – also would like the option to put those items in a folder.
- Use Case: work with government agencies and are uploading content to box with SSN and other secure documents so would like those to automatically go to a specific file if item is flagged2 votesThis specific use-case isn’t planned at this time, however, we are investigating if we could apply a classification policy instead.
-
3 votes
We do not plan to make custom terms of service more granular at this time, as the admin / user complexity of configuring and maintaining n number of ToS policies would be very high.
-
2 votes
-
Compliance email archive for external collaborator actions on enterprise owned content
Compliance email is only being sent if managed user makes an action. We would like complaince emails to be sent based on enterprise owned content so that would included external collaborator actions.
3 votes -
Different Custom Terms of Service for Specific External Collaborators
Looking for a way to use different custom terms of service for different external domains since currently you can only use one set of terms for all external users
4 votesThere is a significant amount of admin UI complexity that this feature would introduce. At this time, we don’t plan to add this.
-
1 vote
- Don't see your idea?