Currently, we can manually set auto-deletion of a folder via folder settings. We want auto-deletion be set automatically for all newly created folders and files that are under a given folder (in a similar way as how folder-based retention policy auto-delete file versions under the folder.). Unlike retention policy which only admins can configure via admin console, we want this feature to be configurable by end users.

At the end of a set retention policy, add an option where the content is automatically moved into a designated archive folder.

Allow to freeze file and folders, which will not allow any collaborators including the owner to perform any changes to files and folders. Example: prevent creating new versions of the files, prevent moving content to trash, prevent change of metadata etc. Basically complete lock, which can only be unlocked at the end of a retention period. The purpose is to manage enterprise records. May be some sort of retention policy that lets us do the above. The current lock feature does not provide the level of freeze we are looking for.

We already have an event for removing the legal hold assignment, but that doesn’t tell us if each of the files under that hold is released from the hold or not.

I hope to be able to delete a policy that is retired and no files are applied

Retention notifications to include the name of each file (instead of just names of folders containing the files) that will expire in 14 days

Would like to set multiple email accounts for t “To a specific email address” of Compliance Email Archive.

A piece of UI feedback on legal holds: the buttons “release” and “report” are quite close to each other, but do drastically different things. While there is a secondary confirmation screen, it still might be useful to create more physical separation between the two to prevent mistakes.

Identify duplicate files in Box, and apply any policies in place onto all duplicates

When [Contents Security] catches a policy violation, Box tells the name of policy only.   So Box users need to find the violation data though the file.   If Box can explain a detail point of violation, it will help users to understand and find the cause of violation quickly and easily. 

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

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.

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.

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.

We like the ability to set the number of file versions per user, folder or file

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

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.