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
-
Display Collaboration Invite as account Creator in Daily User Account Creation Summary Email.
Admin for enterprise is requesting to add Collaboration Invite as an account creator in Daily User Account Summary Email and Report's display results online.
Admin received Daily User Account Summary email and it did not display the creator of some accounts within the email. It was represented by "--" in the field.
The Admin ran a report and the results were the same when displayed within the window.
Only when the user exported the report were they able to see that the accounts were created through a collaboration invite.
0 votesThank you for the suggestion! We are not reviewing this at the moment, but will consider with additional customer demand.
-
0 votes
Not planned for now. I’m interested in additional information. Do you plan to notify users directly about this?
-
Ability to report on what types of files users have
The ability to drill down at the user level to show what kinds of files a user has. E.g. 50% .docx, 10% jpg etc. without looking at the content itself.
0 votesThank you for the suggestion! We are not reviewing this at the moment, but will consider with additional customer demand.
-
0 votes
We don’t show email addresses for any non-box users for collaborations. This is consistent with the /collaborations endpoint as well since the person in question has not agreed to our TOS
-
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.
-
0 votes
-
0 votes
-
0 votes
-
0 votes
We will need more customer feedback on this suggestions before further consideration.
-
Restrict content creation feature to enable/disable co-admins from creating root level folder
We would like an additional control that enables/disables co-admins from creating root level folders. They should be able to perform all other folder actions, copy, move, delete, but not allowed to create. This enhancement would not apply to the Main Admin.
This would help ensure that locked down folder structure are maintained, minimizing user error and guaranteeing compliance and oversight. This would also facilitate making sure that Governance policies are in place for all content without admin monitoring required for newly created folders/content uploaded to 'unauthorized locations'
0 votes -
Ability to send Confirmation Link to managed user
Admin would like the ability back to send a confirmation link to managed users. Not reset password like this feature was changed to.
It is inconvenient to have to contact User Services in order to have this email sent to users.
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.
-
Group collaborations: include information in Enterprise Events about the folder that was added/removed
When a group is given access to a folder (or folder access is removed from a group), Enterprise Events for GROUPADDITEM / GROUPREMOVEITEM should include information about the item that was added or removed, as well as the collaborator level.
0 votesThis suggestion is not under consideration for the current or future roadmap. We are currently focusing on improving the experience to manage users in the Users & Groups tab.
-
Allow admins to select multiple folders within Content Manager and bulk change permissions/ownership
Our admins have had a large influx of personal accounts migrated to their managed service. In some cases people set up shared accounts that do not have a corresponding individual attached. They are trying to scoop up those folders and put them all into a subfolder that can be shared by the group.
0 votes -
Archive a User's Data and Admin Deletes Managed User.
We liked the (now changed) feature of Delete & Transfer to an inactive account. Since the recipient (the new owner) was inactive, no one could collaborate on files that they owned. This was our "archiving" system. Any way to fix this? Workarounds for now = admin makes recipient temporarily active for transfer, then makes them inactive after.
0 votes -
0 votes
-
Add Boolean Attribute to User object to Indicate Unlimited Quota status
Currently, when querying the User object endpoint there is no way to identify whether the quota for the user has been set to Unlimited, even though Box permits sending a "-1" parameter to set the space_amount.
When the object is returned, the space_amount for an Unlimited quota will vary depending on the total space allocation for our company.
The request is to add a new Boolean attribute, such as "isquotaunlimited" to return this information.
0 votesWe are not currently planning on adding this new field to the users endpoint in the next few quarters, although we will revisit this feature request in Q3.
-
Different Support contact information for sub set of user population
We would like certain user accounts to see a different support number than all of the others users.
0 votesWe have not heard many requests regarding this feature. We will reconsider with additional demand.
-
Create Setting to be able to 'Hide' user from Shared Contacts
This pertains to companies who would like to be FERPA compliant.
0 votesWe have not heard much about this use case. For now, it is not prioritized. We will reconsider with additional updates.
-
Request to expose "ip_address" parameter through User Events endpoint as with Admin Events
ip_address parameter is exposed for events reported by the admin events endpoint. Please expose the same info for user events.
0 votesThis type of information should ideally be getting pulled from the enterprise events API. The User Events API is analogous to the updates feed in the Web App.
More detailed logging about how users are accessing content (e.g. IP address or service) is meant to be pulled from the Enterprise Events API as that’s a centralized location across the enterprise for auditing.
- Don't see your idea?