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.
9665 results found
-
The ability to access Box to certain documents only if the user is logged into MFA or VPN
The ability to access Box for all moderate data then only allow access to certain documents (classified docs) only if the user is logged into MFA or VPN
1 voteNot currently planned at this time.
-
2 votes
-
Adapt Annotations to achieve Accessibility guidelines
Box View does not conformance with W3C Web Content Accessibility Guidelines, version 2.0 (WCAG 2.0) at conformance levels A and AA - specifically, annotations can only be viewed around mouseover. This is a blocker for us as we work with public universities who have to meet those guidelines.
1 voteThank you for the feedback. It’s on our backlog and we’ll do our best to get to it as soon as we can.
-
Sync from parent of View Path Collab
Currently cannot sync a folder from the parent of a View Path Collab. We want to use the API to add collaborations and keep the context but also let our users Sync.
1 vote -
Modify file extension
Requesting the option to modify the file extension, perhaps under More Actions in the Web App.
9 votes -
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 -
1 vote
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.
-
2 votes
-
Restrict content creation at the user or group level
Request: Root content creation to be set at user or group level instead of the tenant so that the majority wouldn't have to sacrifice a open folder structure for a small subset of users with constraints. Ultimately looking for a hybrid solution.
13 votes -
2 votes
Recent changes should have made the start-up process quicker for returning users and for new users.
-
If a user locks the file, it should be only unlockable by that user and an administrator, not other Editors
Other users unlocking defeats the purpose of locking in the first place.
30 votesThanks for the suggestion! This is not currently planned, but we will keep it in mind for future enhancements of the product.
-
0 votes
-
0 votes
-
0 votes
-
Block login to Box Sync if BFD is already installed (and vice versa)
Prevent access to Box Drive if Sync is already installed on users machine (and vice versa)
0 votes -
0 votes
-
Change email in deletion notification to users.
We would like to include a different email in the deletion notifications to users than the default of including the admin email.
0 votesThank you for your submission. However, this does not have enough demand in order to be prioritized.
We will reconsider with additional use cases.
-
Ability to disable "user added another user to your folder as a collaborator" email notifications.
We've built an app that centers around adding users to folders owned by a service account. We had over 150k notifications in a single day, accounting for 80% of their email traffic to a single inbox for a brief period. We've have added a rule to block these incoming emails, but we are not satisfied with this solution and urgently request the ability to turn these off.
3 votes -
0 votes
We do not planning on making changes to the basic permission structure at this point.
-
Trashed items: include details about the deleter
When a user makes a GET call for all trashed items, the response does not include details (name/user ID) of the user who trashed each item. This is inconsistent with the Web App view of a user's trash. The Web App view includes the name of the item deleter.
5 votes
- Don't see your idea?