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.
- or
No existing idea results
- ~ No ideas found ~
8176 results found
-
Folder specific usage reports
A number of our teams need the ability to run usage reports based on the folder in contrast to the typical usage report which is based on the user/group.
We want to store highly sensitive documents in Box but need visibility into this kind of activity. This would also function as a very scalable way of measuring content adoption for the Team Leads.
4 votes -
2 votes
-
Reduce Box Drive log file size on admin device
Box Drive logs take up over 35GB in four days. If possible, it would be great to either purge old logs or compress them so they don't take up as much space on the local HD.
1 vote -
Introduce a combination of version labels and version dependent permissions.
Compared to legacy ECM systems, versioning in box is limited to data states over time. There is no notion of a document lifecycle attached to a certain version (WIP, draft, published).
The mandatory check in/out of legacy ECM makes the system very user unfriendly. However, it would be nice if we could somehow label certain versions. The list of labels could either be fixed, or user definable.
If we combine this feature with a new permission: "view documents with status published", we could now have one directory where people work on their documents, but external people would only see the ones they have published.
Such a setup would allow for an easier way of working, since documents won't have to be copied anymore to shared folders. One could work in the shared folder but within it, only certain documents would be shared.
Compared to legacy ECM systems, versioning in box is limited to data states over time. There is no notion of a document lifecycle attached to a certain version (WIP, draft, published).
The mandatory check in/out of legacy ECM makes the system very user unfriendly. However, it would be nice if we could somehow label certain versions. The list of labels could either be fixed, or user definable.
If we combine this feature with a new permission: "view documents with status published", we could now have one directory where people work on their documents, but external people would only see the…
1 vote -
1 vote
-
Canvas LMS integration
Useful for universities.
5 votesThis is not planned from the Box side. If Canvas wants to build the integration, that would be the best path.
-
Support for popular eBook file formats in Box Preview (ePUB, AZW, MOBI, etc...)
Book publishers use these formats for delivering to eBook stores, editors, agencies, etc.
2 votes -
Ability to Archive Old Box Notes
Or at least add different view categories so that all the notes don't just appear under Recents
2 votes -
11 votes
-
Bulk assign metadata attributes to multiple folders/files at one time
We were a previous heavy user of tags and our users enjoyed the ability to assign tags to multiple files at once in the old UI.
Because they have tens of thousands of users deployed, they often have the same attribute needed to be assigned to many files.
6 votesWhile we recognize the importance of this feature, it is not something we plan to introduce in the near term. We will certainly keep this in mind for future roadmap inclusion and we will keep the status of this request updated to accurately reflect our current position.
-
3 votes
Interesting feature request! However, we’re not able to prioritize it at this time due to competing priorities.
-
Ability to create Box reports by API
To import snapshot data (folders and files, collaborations etc.) to SIEM like Splunk, it's convenient that Box reports data can be created by API.
23 votesCustomers can utilize the existing events infrastructure to gather this data, so we do not have any plans to provide snapshots in fewer API calls in the short term.
-
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.
-
Allow End users to email shared links to groups
Users would like to be able to send notifications to groups. When selecting to send shared link as emails, you cannot select groups.
4 votes -
Allow users to password protect shared links created via iOS app
Currently the iOS Box app does not allow users to password protect open shared links.
19 votes -
Add support for Canon, Nikon, Sony images
Supported by Google Drive.
Canon = .cr2
Nikon = .nef
Sony = .arw4 votesThank you for the submission! This is not planned.
We don’t see enough customer demand for this yet, and supporting every additional content type takes a significant amount of engineering time and effort.
We suggest using the Open With Preview framework which should give third-parties (the company in this case) the ability to integrate a viewer for these file types as part of Preview.
-
1 vote
-
1 vote
-
1 vote
-
Collaborators Page - Add 'Common Folders' Column Back to Page
In Legacy, the Collaborators page had a column called "Common Folders" that told me (as a user) which folders I was collaborating in with the given user.
In Amsterdam, this column was removed, meaning the page only tells me WHO I'm collaborating with, but not WHERE I'm collaborating with them (aka in which folders)...which makes the page FAR less useful.
REQUEST: Add the 'Common Folders' (or something similar) column back to the Collaborators page so that the page can tell me both
1. Who I'm collaborating with across my entire account
AND
2. Where I'm collaborating with each user (aka in which folders)In Legacy, the Collaborators page had a column called "Common Folders" that told me (as a user) which folders I was collaborating in with the given user.
In Amsterdam, this column was removed, meaning the page only tells me WHO I'm collaborating with, but not WHERE I'm collaborating with them (aka in which folders)...which makes the page FAR less useful.
REQUEST: Add the 'Common Folders' (or something similar) column back to the Collaborators page so that the page can tell me both
1. Who I'm collaborating with across my entire account
AND
2. Where I'm collaborating with each user (aka…7 votesInteresting feature request! However, we’re not able to prioritize it at this time due to competing priorities.
- Don't see your idea?