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
-
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.
-
0 votes
This is not planned at this time. Do BCRs help you address this request?
-
0 votes
We will need more customer feedback on this suggestions before further consideration.
-
Total File Count by File Type via Admin Console
We would like to see how many files are in Box at any given time and by file type. This would help drive the seamless use of Box across our org. due to the amount of content we already have stored.
0 votesThis information is available via API or by using overall size of storage as the proxy for number of files if possible
-
Prevent End Users from Updating Email Aliases in Account Settings
Current: Users are able to add any email addresses as aliases to their accounts
Request: Create a setting in the Admin Console that can be enabled to prevent end users from modifying their aliases if it is being managed by Admins via API/SAML. Alternatively, enable a setting that limits users to only be able to add email aliases that match registered domains for the EID.
3 votes -
Add column to the User Activity Report that shows the full file path for any file or folder activity
Currently, it only shows a column called "Contained in Folder" which is not enough for most investigations.
0 votesFor the moment, I think this needs to be accomplished via our APIs.
-
0 votes
-
Security Log should cover features in "Folder Settings".
Specifically, the setting called "Only folder owners and co-owners can send collaborator invites".
0 votesWe don’t currently plan to add this to the logs.
However, it should be noted that there are compensating controls for this, such as restricting the ability to change this setting at the EID level, or not adding users as Editors in folders where there is sensitive material.
-
Allow Group Admins make a GET call for enterprise users
Group Admins are able to use the webapp UI to add managed users to a group. The UI allows them to start typing a username or email address and will return any results that match. If a Group Admin wants to add a member to a group via the API, they need to know a user's user ID. However, GET calls to https://api.box.com/2.0/users?filter_term=email@domain.com by a Group Admin fail with a 403 error. The same call made by a Co-Admin succeeds.
0 votes -
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 -
0 votes
-
Enable restriction of content creation in folders more than one folder deep
i.e. for specific, company-wide folders
0 votesNot planned at this time. I think this can be addressed via existing permissions. Let us know if your problem persists in the comments.
-
0 votes
Thank you for your submission. However, this does not have enough demand in order to be prioritized.
We will reconsider with additional use cases.
-
0 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 -
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.
-
0 votes
Thank you for your submission. However, this does not have enough demand in order to be prioritized.
We will reconsider with additional use cases.
-
0 votes
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?