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.
189 results found
-
Ability to exclude specific folders or files from policies
Ability for admin to select folders or files for which subsequent uploads will not be requarantined.
1 vote -
Have a download policy similar to the upload policy
When someone is downloading content with social security numbers, EINs, tax numbers, etc. then someone is notified
1 vote -
Add ability to query if a user is under Legal Hold via API
Currently, Legal Hold objects have assignments, and if you get information about the assignments via the API you could see if a user was assigned to them.
However, we want to access it from the user perspective - something like an islegalheld field on the user object.
2 votes -
Include link to folder/file shared in admin email notification for sharing policies
Currently, the email notification for a sharing policy only shows who sent the collaboration invite and to whom rather than showing the content that was shared. This requires an admin to pull a collaboration report each time to verify what was shared.
1 vote -
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 -
File Version treats each version as a separate file.
Within the policies area box is restoring the file but every time a new version is created the same file will be flagged again.
1 vote -
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.
10 votes -
1 vote
-
3 votes
-
Legal Holds based on Metadata
Allow the ability to put content on Legal Holds based on metadata attached to the document. Customers may utilize metadata moreso than custodian or date to identify content to be placed on Legal Hold
7 votesAs metadata usage is currently quite low, and because this is possible via the API, this is not currently planned for support within the Governance UI. We may reconsider with more customer feedback or higher usage of metadata.
-
The ability to limit the options for extending the retention period
We only want content to live in Box for a set period of time and want to limit the ability for content owners to extend retention after period is up.
1 voteThis is currently not on the roadmap as we have not heard this request from many other customers. We will consider it in the future if there is increased customer demand.
-
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.
-
Apply disposition action based on "Move" date
We would like to move active projects to a completed projects folder that deletes content after 30 days.
The disposition action should occur 30 days after the project is closed and the folder is moved, rather than when the files were initially uploaded or last edited.
We cannot apply a policy to the active folder because we need to be able to delete files.
4 votes -
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.
-
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.
14 votes -
3 votes
-
Option to delete the folder alongside Permanently delete content policy
We auto-delete completed projects after 30 days and would like to automate this process with retention policies.
Currently, a Permanently delete content policy only deletes the content within a folder, however, we need the folder itself deleted because it contains the confidential name of the project.
2 votesThis is currently not on the roadmap as we have not heard this request from many other customers. We will consider it in the future if there is increased customer demand.
-
1 vote
-
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
-
Upload Policy Type for folder locations
'Upload' Policy Type does not provide the option to apply at a folder level. It would be ideal if all policy types had the option to apply it to specific folders.
3 votesWould love to understand the use-case more on this one.
- Don't see your idea?