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.
- or
161 results found
-
Improve management of pending invitations via API
As we continue to build and customize the collaboration mechanism we found it difficult to manage pending invitations. When calling your API api.box.com/2.0/folders<folder_id>/collaborations it returns approved collaborators in the “accessibleby” object but when it return PENDING collaborators the “accessibleby” object is null, but there’s status “pending” on this collaborator. We would imagine it would capture the email address of that pending collaborator. Seeing this is capable in your public domain to show the pending collaborator with an email address would be very useful to create modules to manage pending collaborators (e.g. resending the invitation, update…
7 votes -
Event stream missing a share_level or similar attribute
By pulling the events with the API and comparing them, it appears both are missing a share_level or similar attribute. This attribute is also they can detect when users share files outside the company.
3 votes -
Request for a web page that better captures domains AND IP ranges for Box, including an XML feed to subscribe, changelog, etc
Can Box emulate Microsoft and create a web page like this. Originally (about 3 years back) this page was bare bones and just contained services, urls and IP ranges. Network admins had to scrape the page to grab the IP ranges they needed and use IFTTT. They have since added an XML feed and a way to subscribe to changes. They post updates once a month or so before they go into effect. Every bit of info on this page (including placement of links) has evolved based on user/admin feedback. https://support.office.com/en-us/article/office-365-urls-and-ip-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2
1 vote -
2 votes
This is not currently on the near-term roadmap.
-
Email to Box
Box to email is a powerful feature when combined with email services. If you would like to automatically forward emails when using Gmail, its either all or nothing (all the emails would have to be sent, or none).
This is due to the fact that Gmail requires a verification code to be entered when creating an email rule to addresses off the Gmail account domain.
If there would be a way to read the body of the message for the verification code, this could reduce issues with forwarding and the volume of messages forwarded to Box.
1 vote -
1 vote
-
0 votes
-
Request for an Content Folder API call to support passing to it a folder path and return the unique folder ID
We would like to be able to retrieve folder ID directly via API call by passing in the folder path as a variable.
So for example if the custom program knows the folder virtual path (/folder A/folder 123/folder X) the API call would return the correct folder ID for "folder X".
0 votesFolder path is pretty fragile as names change frequently, so I don’t think this is something we’d want to do.
-
Folder Under Retention Should Not Be Purged From Trash
When a folder is deleted from trash that contains files under retention policy it causes issues because the files are no longer visible to the customer to recover them. This happens if the trash admin setting is set to purge all trash in a certain time period.
2 votes -
BOX should give us more options to work with subfolder access
When you give the Viewer access to a group of people in the root of a structure, you could work with subfolders by 1) removing some people from access specific subfolders or 2) changing the type of access specific person would have. For example,
1) I have specific content that should be restricted but need to manage it in a single place. If I try to remove a person from a subfolder, it will remove this person from the whole structure.
2) I can create a root folder called "Teams" and give everyone the viewer access to it (since the…3 votes -
Shared link default permission at the folder level
An option to have newly-created folders and documents inherit the folder sharing permissions of its parent folder.
5 votes -
Password Mail
When we share the open link with password, currently we need to create the new email and send the password separately.
If we have the Email Icon to send password, we can work this on only Box.
We would like to create the new Email icon to send email from Box web console.2 votes -
The support for large contents migration Snowball(AWS) type of migration should be supported by Box.
Snowball(AWS) type of migration should be supported by Box. Especially the customers who have tons of files/folders as TB/PB level has a hard time for content to move from Windows servers to Cloud systems like Box.
1 vote -
0 votes
-
Prevent copy/move actions during upgrade
When upgrading, current files should be maintained so there is no loss of workflow and access to files other than for making change.s. There should be a freeze on all changes to the folders so that folders are inadvertently moved and duplicated and manipulated by those that have access. Currently those without anything but viewing permissions can go in during the upgrade and copy and move files and change permissions so they have access. That should not be. Files should be frozen.
1 vote -
Separate folder move and copy function
As far as i understand, the move and copy folder function in Box Web is combined from a role perspective. That means a user must have Co-Owner rights to move a folder but also to copy a folder. I agree that moving a folder means deleting the folder on the source location which may need elevated role. But copying a folder only needs read access on the source folder. So it would be great to separate these two functions and make the copy function available to users who have editor role on the target folder and have at least previewer…
1 vote -
0 votes
-
FTPS access for collaborators to a subfolder rather than through root level credentials
Use Case: Research studies using radiology images that come in large image sets from tools like MRI scanners which can have hundreds to thousands of images which make it impossible or impractical to use the web interface.
However, they are still external collaborators who should have the ability to send files.
2 votes -
Error message to transfer ownership when only admins are allowed to create or delete level 1 folders
With the option to restrict folder creation at level 1 to admin, if the admin give the ownership to a user and then this user try to give the ownership to another user, she can perform the actions and finally get the message "There was a problem making xxx the owner of the item. Please try again or refresh the page."
The message should be revamped or the user should not be able to start giving ownership.
0 votes -
Editor Only Permissions Access
We are looking for a way to limit a user so she can not add new documents to a folder but is able to edit documents already in the folder.
The granular nature of your platform is so fantastic, and this nuance would make it even better. After all, just because I share a folder populated with documents that I want edited by other people doesn't not mean I want those same editors to bloat my folders with extraneous files.
There is strong use-case for this. Call it the Edit Only privilege.
0 votesThank you for the request! I believe this would add to the complexity of the product without providing wide enough benefit. I’m happy to review further use cases and demand in the comments.
- Don't see your idea?