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.
176 results found
-
Retention Policies as Deletion Policies
Files in a folder (or globally) would be purged after a certain period of time, but if a user wants to remove the content before that time, they would be able to do so.
24 votesCurrently not planned; may be considered for future roadmap
-
Collaboration Whitelisting - Add Ability to Whitelist Specific External Users
The Collaboration Whitelist feature is currently scoped to whitelist entire domains
REQUEST: Take this current domain whitelisting a level deeper by only allowing certain users from a given domain to collaborate with ones own EID, aka introduce user-level external collaboration whitelisting controls to where a company can say "block all collaboration with all @acme.com users except for X @acme.com users"
19 votesNo plans at this time to make this more granular – while we’re interested in this one, to make this feature work well there is a decent amount of UI complexity to sort through on both the admin and end-user side.
-
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!
-
Launch workflow at end of retention policy
There should be an option to launch a workflow process when a retention policy expires. This would allow for use cases such as moving the file to an archive, destruction approval, etc.
16 votes -
Unified/Global 'All Trash' View
In larger companies, Content Manager's organization of trash (by Owner) and searching through Usage Logs are both overly cumbersome when looking for a file that a user has 'lost' (aka that's been deleted).
To ease this pain, please build a unified/consolidated/global 'All Trash' view added somewhere in the Admin Console -- likely in Content Manager.
From that view, an admin would be able to see:
1. File/folder name
2. Date deleted
3. Owner
4. Deleted by (user)
5. Option to permanently delete or restore15 votesThis is not planned at this time.
-
Retention policy details in the Trash UI
The Bin/Trash UI displays Retention policy details the first time you trash an item until you navigate away.
Ability to have this info visible at all times in Trash UI would be helpful to end users and admin rather than running reports to check status of a single file.13 votes -
Smart Archive
Ability to report on content that hasn't been accessed, modified etc after a certain period of time and ideally take action e.g. delete or move to archive.
13 votes -
Restrict the move to the trash in Retention and Legal Holds
Currently, Retention and Legal Holds prevent contents from deleting them permanently, but it's more helpful to let contents not to move to the trash. We would like to choose from either option. ion.
11 votesThis is an understandable request, but if fulfilled, would create a situation where users had no way of removing files from view.
-
Collaboration Domain Whitelisting at Folder Level
We want to whitelist other domains at the folder level so that collaboration can be open with certain clients on external folders while also being completely blocking collaboration with any other domains.
11 votes -
Moved to trash report
We would like to run a report for a user and understand who deleted their content. Currently you will need to run this for the whole enterprise with the option moved to trash, and the results will only show who deleted the content and not who owns that content.
The only work around at moment is to pivot table with files and folders report of the owner they are looking to run the report on.
11 votes -
Allow users to easily set retention on an individual file or folder
End users need to have the ability to easily apply retention policies to individual documents. They should be able to click an apply policy button, choose the policy and click OK
Policies should be able to be configured so that users only see policies that apply to them or they have access to.10 votesPlease help us understand the use case more, as the ability to apply retention is typically not extended to end users.
-
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 -
Manage Quarantine Programmatically (via API)
There is no way to manage the quarantine process programmatically. As a result, we must individually release / delete quarantined files via the UI.
Given that the policies have a tendency to generate false positives, this process becomes very time consuming and difficult to manage and requires valuable IT time to click buttons (often for hours).
At our scale, and since we opt to use DLP policies, it's impossible to manage.
10 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.).
-
Apply retention policy to all existing content
Currently with Governance, you have the ability to apply a retention policy to all new content. This policy does not touch any of the existing content within the domain. This is a large issue for an enterprise that wants to apply a single retention policy to the entire domain.
9 votes -
9 votes
-
Ability to customize download policy thresholds
Currently the policy thresholds are automatically set by our algorithms, and the policy is triggered on a per minute rate basis and one hour time window. This has caused alert fatigue for the customer because so many notifications are generated every few minutes based on these thresholds that they aren't able to update or customize.
9 votesWe will be looking at how to reduce the noise but it might not be through enabling customization.
-
When retention policy expires, have option to archive rather than delete
At the end of a set retention policy, add an option where the content is automatically moved into a designated archive folder.
8 votes -
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 -
Identify "retention policy" as the deleter of content
When an item is deleted by a retention policy, it just reads that "someone" deleted the item.
We would like the ability for the deleter to be named as something more explanatory like "retention policy" so it is more easily identifiable during an audit.
7 votes
- Don't see your idea?