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
-
Group Admins should be able to invite co-admins to groups
A group admins tried to add a user to the group as a member, but received the error message 'User does not have permission to edit users of this group'. The user he was trying to add was a Co-Admin for Box.
With this, if the Co-Admin has the administrative privilege to "Manage Groups" attributed to her, then she can go in and add herself to the group.
If not, the main Admin of the enterprise would have to add that Co-Admin to the group. This complicates the process of adding users to a group.
2 votesThis suggestion is not under consideration for the current or future roadmap because there has not been enough demand from customers.
-
Include Enterprise Events for access changes to shared links triggered by enterprise-wide settings updates
If an admin updates the enterprise-wide shared link settings from open to restrictive (for example, removes "People with the link" as an option), the access level on any existing open links is changed. This change is not included in Enterprise Events/Usage Log reports.
2 votes -
User-Level Sharing Controls: Control sharing permissions at the User level
This request is specific to controlling external sharing permissions and defaults at the user level. For example, an admin should be able to permit whether a user can generate Open Shared Links (e.g., disable open links per user), invite external collaborators, and the default shared link permission that is generated by that user, even if those users are within a folder that has external sharing enabled.
30 votesWe are currently focused on building groups for access to 1st and 3rd party apps and specific enterprise settings in Box rather than focusing on groups or individual users for sharing controls. Uservoice request here: pulse.box.com/admin/v3/suggestions/36670615
To achieve granular sharing controls, you can explore using Box Shield to classify sensitive content and set access policies to that content.
-
6 votes
Not planned for now but will keep on our radar for the future.
-
Add a warning when an admin tries to change their subdomain in the admin console
It will break all existing shared links unless admins have the "spoofing" setting enabled. By association, embedded content will stop working too.
The request is to add sufficient warning.
1 vote -
Ability to set external password requirements
We would like to be able to set the requirements for the password required to log in to FTP and WebDAV
1 voteThank you for your submission. However, this does not have enough demand in order to be prioritized.
-
The Ability to Search for Users by Secondary Email Address
In the Admin Console, there is currently no way to search for users by their secondary email address.
When the Admin goes to create a new user with an email address that is already in use by an existing account, they have no way of seeing who is using the email address without checking their users' account details individually.
4 votesThis suggestion is not under consideration for the current or future roadmap. We are currently focusing on improving the current experience to manage users in the Admin Console before we add enhancements to search.
-
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.
-
Disable/enable feature announcement notifications on an enterprise level for all users
This would be added to the enterprise settings for default email notifications. The users are receiving many notification and sending out instructions to all of them to change on a user level seems to be out of the question.
4 votesThis is not a priority at the moment given our roadmap commitments. We will reconsider with additional demand.
-
Make a setting for enterprises to have granular control over if a user gets to change their name
Similar to the unable to change primary email.
2 votes -
Web App Integration - Group Application Controls
We would like to be able to apply an integrated web application to groups of users as opposed to individual users.
3 votesNot planned for now but will keep on our radar.
-
1 vote
This suggestion is not under consideration for the current or future roadmap because there is not enough demand from customers to sort members by access level.
-
Security Report: Include Changes to Any Setting from Enterprise Settings
Currently, the Security Report doesn't appear to capture quite a few settings changes that happen in Enterprise Settings in the Admin console, which is bad.
For example, if an admin is wanting to know who changed the 'save files to device' setting on the Admin Console -> Enterprise Settings -> Mobile tab, there's no in-product way currently to identify that. Also,
--All Notifications tab settings except for the Compliance Email Archive settings are missing
--ALL settings from the Apps tab are missing, meaning there are no filters/logs exposed currently for any changes to make apps available/disabled, disabling all published apps,…28 votes -
Role based permissions or more granular permissions on groups
Ideal is a role based permission where you can select individual folders, people, and files that users have access to as well as admin permissions.
Other option is to add more granular permissions for groups.
6 votesWe do not plan to add more permissions / roles at this time.
-
Admin determines fixed tags for accuracy
Give the admin the ability to create a "template" of tags to use so that end users have to follow a set model.
3 votesI think metadata will end up being the mechanism for this.
-
Inactive State: Do Not Hide Owned Folders for Managed User Collaborators (still hide for External Collaborators)
Currently the 'Inactive' User Status not only prevents the user from accessing their account, it also hides ALL owned folders for all collaborators.
Meaning if John Smith is changed to 'Inactive', all of the collaborators that are in his owned folders will no longer see those folders in their accounts.
REQUEST: Change this status to only prevent the user from accessing their account, while keeping their owned content visible for Managed User collaborators (keeping today's behavior of hiding for External Collaborators).
18 votesWe are currently re-designing our managed users page for performance and usability updates which will be released at the end of this year. We will revisit newer features to user management after we release our new UI. In the meantime, please add your use cases in the comments so we can have this feedback when we decide to pick this up.
-
Ability to output a list of all collaborators via API
Currently you are not able to export external users as a list. You can only validate if a certain user is external or not.
5 votes -
1 vote
-
Group-Level Sharing Controls: Control sharing permissions at the Group level
This request is specific to controlling external sharing permissions and defaults by Group. For example, an admin should be able to permit whether a Group can generate Open Shared Links, invite external collaborators, and the default shared link permission that is generated, even if users in that Group are within a folder that has external sharing enabled.
19 votesFor now, we are focussed on solving bulk management issues with Shared Links.
Box Shield is an additional option for enforcing granular controls on content.
-
Add ability to trigger email confirmation when adding an email alias from blacklisted domain
Example: gmail.com is a blacklisted domain. If an admin tries to add a gmail.com alias for a managed user via the API, the call will fail with a 400 response.
2 votesThis request is not on our short-term roadmap. We will update you if anything changes.
- Don't see your idea?