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.
998 results found
-
Change the default message in text Box when inviting new collaborator to a folder
Would like to be able to change the default text in this section to another default text. Currently, you can manually edit this section every time you add a new user to a folder. We want to be able to change what populates this section by default.
1 voteWe are unlikely to build a setting to enable changes to this default. However, if there is a better default message that may work for all of our customers, we are happy to reconsider.
-
Checkbox default values on account deletion and content transfer process
On account deletion and content transfer process, currently, the default value is checked off for "Notify user" checkbox. We would like to be able to toggle the default value to unchecked checkboxes.
1 vote -
New User-Level Field: "User Description" (Free Text)
Other applications (like Slack) have a user-level free text field (similar to a User Description / Information field) where admins or users can enter free text to describe the user.
1 voteThis is not currently planned. We will revisit this with additional use case data and customer requests.
-
Lite Users added to Groups when rolled in as a managed user
When lite users are rolled in, the admins would like to have the ability to add users to groups within the WebApp UI, instead of having to add users to groups 'AFTER' they are rolled in
1 vote -
Role configuration on group sharing
In Enterprise setting -> Content & Sharing -> Collaborating on Content Tab, you can configure which role to enable and the permission those roles gets. This setting only applies to individual collaborator but not Group. You can disable Co-owner in that setting but still see it available when doing folder sharing with group.
We assume that the setting above is a global thing and applies to both individual collaborators and groups, so we find it a little confusing.
Can you put an extra option like "Apply the same role setting to group" in "Collaborating on Content" tab to better demarcate…
1 vote -
Visually denote already shared folders as in Shared Folders interface for Group Admins.
When adding folders to groups in new interface, a list of all folders is shown including folders that have already been added. This is confusing and can cause additional workflow, having to go back and forth to see what has and hasn't been added.
1 voteThis suggestion is not under consideration for the current or future roadmap. We are currently focusing on improving the experience to manage users before we add enhancements to the group management process.
-
Have an enterprise-facing/admin notice that external collaborators have certain single-file upload limits (250 mb, 2 GB, 5 GB, etc.)
Currently, the responsibility lies on the external collaborator (they receive a message to upgrade their account), but admin would like a way to know if external collaborators have these limits
1 vote -
Allow Special characters to be searchable in content manager
The ability to search with the filename and extension within quotes, i.e. workshop.one
Right now, search separates the two and makes it difficult to locate the file, as it would be searching for "workshop one"
1 vote -
Individual Application Controls
Search should return by title first, then body.
1 vote -
Inadvertent Enterprise Setting changes
Today I was perusing various settings and accidently clicked my mouse on a portion of the page and a checkbox was selected (iWork option).
Also upon doing this a toast showed up saying my change was saved. I think this is a bit scary and wish there was some confirmation dialog rather than an automatic save.
1 vote -
1 vote
We are looking at different ways to ease the consolidation of different EIDs. However, this is unlikely to be approached from the perspective of changing branding options by groups.
-
Tracking Codes via SAML
REQUEST: The ability to add tracking codes as part of the SAML assertion. Currently Tracking Codes must be managed manually in the Admin Console or vis API.
1 voteThank you for this suggestion. We will not be prioritizing this in our roadmap. We will review with additional customer demand.
-
Custom messages, settings and language depending on geography.
We need a different trash setting to the global instance due to european law.
We would also like to push different messaging, welcome screens, languages to dependent on regions for adoption purposes.
1 voteThis is not currently planned on the roadmap. The suggested workaround is to manage different users in different EID.
-
Add User Email Address to 'Account Creation Notification' Emails
PROBLEM: Admins in Box have the ability to receive emails when new accounts are created (via the Account Creation Notification setting in Enterprise Settings -> Security). However, this email only includes the NAME of the user, not the user's email address.
REQUEST: Add the email address for the user to the email (next to the name) since names are not unique within a company (but emails typically are).
1 voteThis is a reasonable request. Thank you for filing it! We will reconsider this with additional customer demand.
-
Add admin setting to change default view for user folders to descending.
Create a setting in the admin console to automatically be able to enable descending order filter for all named files for the whole enterprise. This way each user doesn’t have to do this individually.
1 vote -
1 vote
-
Auto Provisioning for Japanese name (lastname->firstname)
When Auto Provisioning option is enabled, the user's name is set "firstname lastname", but we hope to have "lastname firstname".
Currently, Japanese users set firstname information to "lastname" and lastname information to "firstname" in SAML Response.
Firstname and Lastname should be separated like in Salesforce.
1 voteThanks for filling this. Because there is a workaround (though not ideal) to this issue, we are not likely to prioritize this request.
-
"Failed logins" on Enterprise Settings should clear the number of failed login when a user logins successfully
Currently, the number of failed login piles up even after a user logins successfully. It's strange, so it should be cleared when a user logins successfully.
1 voteThis is a reasonable request, however we do not have enough user demand to prioritize this feature.
-
Ability to create a custom group name that will be displayed on the collaborator list without affecting the SSO integration
Currently, groups only have names unlike user accounts that have names and aliases. However, since we have SSO groups enabled, we have found that is impossible to rename groups without causing issues.
Because of SSO groups, we had to have a specific naming convention for our groups so we can know which groups to send to Box. All our group names begin with COMPANYBOXPD and then the corresponding team name. Since these groups are shown as collaborators, it will be nice to be able to edit the group to display a user friendly group rather than the technical…
1 voteThank you for the submission! This is a reasonable request. However, we will need to hear from additional customers before prioritizing this request.
-
1 vote
Thank you for your submission. However, this does not have enough demand in order to be prioritized.
We will reconsider with additional use cases.
- Don't see your idea?