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.
999 results found
-
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.
-
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 -
5 votes
-
0 votes
New Admin Insights allow admins to filter out shared links by status, and download a corresponding report directly from the Shared Links chart.
-
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.
-
Allow admins to report on activity of external collaborators.
We want to report on external collaborator usage of our specific content for a number of reasons:
1) to be able to access if their external collaborators are no longer using our data and should be removed
2) to help us understand how their internal users are working with people outside of the enterprise.
Right now, the reporting is limited to showing when people have accepted folders, or users can go to access stats - neither of these options is sufficient.
Ability to see activity of external Collaborators.
a. Downloads, uploads, previews, edits, etc.
b. We can see my managed…115 votes -
Folder Level Custom Terms of Service (TOS)
Currently, terms of service is enterprise-wide. This presents a conundrum for large enterprises who have several departments, some of which do want the TOS feature but some of which do not.
0 votesWe do not plan to implement this at this time given its narrow use case.
-
0 votes
-
0 votes
This is not planned for our current roadmap. We will let you know if anything changes.
-
Folder specific usage reports
A number of our teams need the ability to run usage reports based on the folder in contrast to the typical usage report which is based on the user/group.
We want to store highly sensitive documents in Box but need visibility into this kind of activity. This would also function as a very scalable way of measuring content adoption for the Team Leads.
4 votes -
0 votes
User activity report currently allows moving between pages. To see the data in bulk, exporting would be the best option.
-
0 votes
-
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.
-
Adding "auto_sync_email_aliases" as name of service when an SSO provider passes a new primary or secondary email.
Currently admin reports show the events as taken by the user. This is very misleading to an admin reading the logs, especially when the enterprise disallows users to update their primary email.
0 votes -
0 votes
-
Transfer content to manager when deleting via Okta
Integrate with AD such that admins can automatically transfer a user's content to their manager.
0 votesWe have APIs available to select which user to transfer content to. We do not hold any hierarchical data to determine which user is managed by which other user.
-
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.
-
Add "Box Web App" as the service name associated with webapp upload events
Currently, User Activity reports (and Enterprise Events) for uploads triggered via the web app do not explicitly mention that the uploads were completed via the web app. Other actions, such as previews and downloads, include "Box Web App" as the service name within the event details.
0 votes -
Update user endpoint to allow admins to retrieve a list of all unconfirmed users
Currently, admins cannot retrieve a list of all users whose primary email addresses are not confirmed. Admins may get confused if they try to edit a user whose primary address is not yet confirmed, as this currently triggers a permissions/403 error.
0 votes -
1 vote
- Don't see your idea?