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.
396 results found
-
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 -
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.
-
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.
-
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
-
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.
-
Ability to export reports in CSV format
CSV is more useful than Excel when they export logs because some our internal system can import only CSV format (not Excel). It's more convenient to give an option to choose CSV or Excel as export type.
4 votesBecause the admin can save the Excel file as a CSV and we do not want to overpopulate the user interface with too many choices, it is unlikely that we will address this request.
-
Add setting in "Group settings" that would allow users to remove themselves from a group
Users could be presented with the option to remove themselves from a group when they try to remove themselves from a folder that they inherit through a group. This should only be available if the group settings allow this behaviour.
It would be beneficial to have a warning message which shares what other folders will have access revoked.
1 voteThis suggestion is not under consideration for the current or future roadmap. We will revisit this feature request as we see more demand from customers.
-
Renaming and moving files/folders: include old and new names and locations in Enterprise Events call
If renaming or moving a file or folder, Usage Log reports include both the new and old names, and new and old locations. The old location and old name are missing from Enterprise Events via the Content API.
4 votesThank you for this request! We do not plan on prioritizing this at the moment. We’ll continue to monitor demand.
-
Add folder/file path to usage log reports
Currently, the usage log report only shows the most recent folder that it lives within, and not the entire path.
17 votes -
Access Stats: Ability to get Access Stats programmatically per-file
Provide an a file API endpoint to obtain Access stats similar to the functionality in the Webapp.
Right now, we have to collect all the relevant events and do the math every time to get an accurate count. This complicates the application logic. Would be much easier to obtain the stats without having to calculate them on your own just like the UI does.
For example having the ability to pass a field and get summary figures in the response. Having to create an event parser to do this is a high barrier to entry to get this type of…
10 votes -
Bulk Edit - Add Ability to Change Primary Email Addresses
Bulk Edit currently allows admins to change various settings for users, but it does not allow the admin to 'bulk edit' the primary email addresses for their users. This functionality would be handy in various scenarios, including when a company goes through an email domain change.
Right now, customers must come to Box (Customer Success) to have us run scripts in Internal Admin to do bulk email changes as we do not have this feature natively in Bulk Edit within the Admin Console.
4 votes -
See login activity reports
We would like to see each users login activity, including those who have never logged into Box.
3 votes -
Print log
Print log can't be extracted currently, so it should be done.
6 votesNeed more information on this
-
Personal Folder Auto-Creation
Similar to the Okta feature (https://support.okta.com/help/articles/Knowledge_Article/36802318-Configuring-Box-to-Create-a-Personal-Shared-Folder), this request is for a native option in Box to automatically provision a 'personal folder' for each user upon provisioning (whether provisioned manually, via Bulk Add, or via auto-provisioning).
Key Requests for this feature:
--Ability to customize the name of the folder that's created (such as choosing the user's name + 'Personal Folder' or other custom strings of text)
--The user's personal folder will be created in their own account and they'll be the owner of it, with no other users in it (even if restrict content creation is turned on)14 votes -
Additional MFA for Admin Console
When logged in as a user, we would like to be prompted for MFA for Admin Console access in case the admin's Box credentials are compromised
4 votesNot currently planned at this time.
-
Allow users to have over 100 group associations.
Many of our users are a part of over 100 groups in their AD, but Box won't add these users to these groups because Box has a group membership limit of 100 groups per user.
2 votesWe would recommend you consider using an API-based integration to import Groups into Box rather than the SAML approach for a better user experience.
-
Admin Rights/User Management (Admin Console)
Ability to grant a certain set of co-admin rights to a group versus on the individual level (helpdesk as an example)
7 votes -
11 votes
-
Control External Collaboration at User Level (not folder level)
Currently, users can have a restriction placed on them that folders owned by that user cannot be collaborated outside of the organization. However, if that user is invited into a folder that allows for external collaboration, that user can invite external collaborators.
We want flexibility to control this at a user by user basis. For example, User A should not be able to invite external collaborators, regardless of folder that they're invited into. However, User B should have the ability to do so (but only within folders that User B owns or within another folder that is set to allow…
4 votesThank you for this request! I’d like to see additional customers with use cases for user-level collaboration restrictions.
Collaboration is a setting that is tied to content rather than users, and I’m not sure that we have evidence yet to make changes to that model.
-
Deleted accounts: Retrieve and restore any previous collaboration relationships
Allow for a Point in Time recovery.
We inadvertently de-provisioned a group of users and then re-provisioned them. Upon re-provisioning, we want Box to be able to restore the user collaboration points to how they existed prior.
6 votesThis is not currently planned as it is an edge case. We will reconsider with additional demand.
- Don't see your idea?