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.
9062 results found
-
Granular permissions per user for sharing public links/classified documents
The administrator should be able to set the default classification for all new documents (e.g. For Official Use).
Each user should be able to set their own default classification (which will override the system setting (e.g. Classified).
Each user should be able to change the classification for any new or existing document where she has sufficient rights. For existing documents, she should also be able to select multiple documents, and then change the classification for all those documents in one go.
1 voteDefault classification label is not planned because it could be misleading to end users. However, to address the concern of content being leaked before it is classified, you can create an access policy applying to “All content without a classification label” in Box Shield.
-
Would like ability for posting/hosting HTML pages via Box
Our creative teams often need to show campaign materials & mock-ups via HTML rendering online. Would like for this to be supported by Box via Edit or an Render button.
Globally - we have approx. 40-50 users working ~7 campaigns per week - so this would be a high use, high value use case.
Teams use Adobe Creative Cloud to create html banners / sites. To render them, a series of documents (with links requiring subfolders) need to be viewed on a browser. When sharing with internal users without Adobe licenses or with external parties/customers, the files are zipped with…
2 votes -
Folder-Level Sync Controls: Restrict Managed Users from syncing a folder (even if they're an Editor / Co-Owner)
Be able to disable sync at the folder level regardless of co-owner or editor collaboration level. Users need to be added at these collaboration levels but they should not have the ability to sync certain folders to their machine (e.g., heavily collaborated content).
19 votesWe currently do not have this planned on our roadmap. Please keep the feedback & use cases coming to help us prioritize this in the future!
Box Shield may be a potential workaround for users interested in restricting syncing of specific content by classifying it. Though this will also prevent any downloads of the content as well.
-
Change Co-Admin Permission to Only Require 'View & Edit Policies'
Right now, in order for a co-admin to be able to view and edit Legal Hold policies (matters), they need a weird mix of unintuitive co-admin permissions (including 'view users content').
2 votesThank you for the suggestion! At the moment there is no plan for this feature. We may look into this in the future.
-
A Way to See Containing Folder From Search Results
We are searching for a file and there is no easy way to see the folders in which the resulting files are contained.
5 votesWe are not currently planning to implement this feature within search. Containing folder information will continue to be available through file previews and in the browse view.
-
More native DocuSign features enabled in native integration
We want to be able to specify sender settings and add custom fields as we do on docusign.com
4 votes -
Invite Collaborators Pop-Up: Add Optional 'Automatically Remove Collaborator on X Date' Field
Right now, auto-expiration for collaborators is only provided as an option from within the Admin Console.
REQUEST: Add a 'automatically remove this/these collaborator(s) on X date' checkbox to the Invite Collabs Pop-Up, with the default being to have it unchecked, of course.
We have API endpoints already to add an expiration to an individual collaboration (https://docs.box.com/v2.0/reference#edit-a-collaboration), meaning admins can do this on our own via API. We would like the same type of option/functionality natively in the webapp UI as well.
3 votesThank you for the detailed explanation! This is not planned for the short-term roadmap. We will reconsider with additional customer demand.
-
Usage Logs and Admin Events don't report version reversion
ITEMMAKECURRENT_VERSION is a Standard User Event in the API but doesn't show up in Usage Logs or Admin Events.
When a previous version of a file is promoted as the latest version, we do not receive an enterprise notification for that.
If we quarantine a file (create tombstone as say version 2) and the user makes the v1 version as latest (v3), then the event received is of type user event and not an enterprise event, which makes us not be able to process such a change.
1 vote -
Tables - Ability to Copy a Row and Paste into a Table in A Different Box Note
Requesting ability to copy a Box Note row and paste into another Box Note table (preserving formatting and links). Currently, you can paste into a new table this way, not an existing table in our testing.
Rationale: Ease of use, consistent ability to cut and paste
21 votesWe understand this use case, however it is not a current priority for the team. We will let you know if anything changes.
-
1 vote
This is a non-trivial change to our architecture and user-experience. We will consider this as we review our organizational structure for content within Box.
-
Please expand user name character field limit from 50 to 100 words.
Global companies need local characters such as Japanese and English for name field and 50 is short for some names
1 voteThis suggestion is not under consideration for the current or future roadmap. Once we see more traction from customers who want are requesting this functionality, we can revisit our decision.
-
21 votes
Microsoft API’s dont allow co-authoring and MSFT doesn’t plan to support it for Box. Please provide feedback to MSFT reps to enable co-authoring for partners such as Box
-
Usage Logs - Include WebDAV Login Actions
We currently don't see WebDAV login activities in the Usage Report. We want to see the log for WebDAV failure logins for security reasons.
2 votesThis is a resource-intensive request which is not on our short-term roadmap. We will update you if anything changes.
-
If a managed user triggers IP CAPTCHA, send an email notification to the enterprise's admin.
If a user triggers CAPTCHA on an IP address, it could potentially impact many users if our account is NATing our IPs to one external IP.
Typically this is caused by an end user saving a bad set of credentials into some kind of client (FTP or WebDAV) that is constantly trying to reconnect.
2 votesThis request makes sense, but this is not something that is planned for the foreseeable future.
I will keep monitoring similar cases and prioritize once this becomes a high value request.
-
Bulk Edit - Add 'Status' column to Bulk Edit spreadsheet
There is no way in the Admin Console to update 'status' (active, inactive, etc.) for 2 or more users at once (aka in bulk).
22 votesEnhancements to the Bulk Add/Edit feature are not currently on the roadmap, but will keep track of this request and consider prioritizing if many customers are requesting it. User status can be edited via API or SAML
-
11 votes
This is not something that we would consider as part of the basic virus-scan for all files today. Customers requiring advanced features such as quarantining malicious files can benefit from a CASB product with Box integration
-
Change Unique Identifier to Something other than Email Address
This is the grouping for the common request for Box to use a unique identifier other than email address for managed users.
Key pain point with the fact that Box uses email address as the unique identifier: Email addresses change often in large companies, thus requiring these companies to use custom API scripting to keep emails in Box updated based on changes in AD.
This unique identifier (whether a mapped value from the customer's user store, aka AD, or the Box unique user ID) should also be the identifier used when users authenticate to Box using SSO (via SAML).
20 votesThis feature request isn’t currently planned on the roadmap, but we are considering the notion of user attributes that can be placed on a user and then used for better context while sharing / collaborating and searching in the Admin Console.
Please provide more use cases in the comments to help us understand the problem better.
-
Improve event information on shared link changes
When running Reports > Usage Logs > select all for "File Sharing" in the Admin Console, you currently only see that a user modified a Shared Link access level. This new feature would allow admins to see what access level the Shared Link was prior to and after the change.
This is important if an admin wants to know how accessible the content was when the Shared Link was initially created and shared.
9 votesNot currently planned at this time.
-
Shared Links - Ability to Have Multiple Shared Links per Item (Folder/File)
Currently, Box's shared link system is a 1:1 ratio between items (files/folders) and shared links, meaning there's 1 shared link per item.
However, there are various scenarios where users would like to have the ability to create multiple shared links per item, each link with different permissions, etc.
Example Use Case: For File A...
--I want one 'people with the link' link with a password added and an auto-expiration set for 10 days from today so that I can share this link to time-sensitive content externally
--I also want a persistent 'people in your company' link that my internal colleagues…3 votes -
Extend Time for Required Password Resets
Extend Password requirements to 180 days
4 votesThis is not planned at this time.
- Don't see your idea?