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
No existing idea results
- ~ No ideas found ~
9722 results found
-
Content Explorer UI File upload limit API option
Need API option in "Content Explorer" UI to increase file upload limit. We have this option available in "Content Uploader" UI. Similarly we need fileLimit option in "Content Explorer" UI too.
Right now we can able to upload only 100 files at a time from "Content Explorer"
1 vote -
Control Outbound Collaboration in Box Shield
Box shield collaboration policies only seem to apply to inbound collaboration (i.e. sharing from one's own tenant to an external account). We need the ability to have fine-grained controls on what invites a managed user can accept from external tenants.
3 votes -
Notification email format
Notifications should include file path or as much of the path the user receiving the notification is authorized for, not just file name and operation (download, upload new verion).
3 votes -
Add a captcha to the File Request module.
Add a captcha to the file request module especially when the module is available from the public. This will prevent file upload from spam.
7 votes -
Metadata Instance Update - Remove when no value should not fail
When Updating a metadata instance to remove a value from a specific instance, currently today the API fails if the field has no value.
I would like to propose that if the field had a value it is removed, and if it doesn't - then just ignore the operation. Similar to what add does if the field already has a value, it just silently replaces it.
As an option, in case others are relying on the failure, maybe add a new operation "forceRemove" so that if there is no value, the code will just ignore it and continue with the other updates.
When Updating a metadata instance to remove a value from a specific instance, currently today the API fails if the field has no value.
I would like to propose that if the field had a value it is removed, and if it doesn't - then just ignore the operation. Similar to what add does if the field already has a value, it just silently replaces it.
As an option, in case others are relying on the failure, maybe add a new operation "forceRemove" so that if there is no value, the code will just ignore it and continue with the…
1 vote -
Fix broken "reverse waterfall" permissions
Fix broken "reverse waterfall" permissions.
When I change subfolder permissions to give someone higher permissions (e.g. Editor to Co-Owner), it changes the parent folder permissions too.
This makes sense that you wouldn't be able to give someone lower permissions in the subfolder than the parent folder, but makes no sense the other way around.
6 votes -
Allow file locking under co-author access
Please allow the ability to lock a file for single-user only access under the Box co-authoring environment
6 votes -
Applying Salesforce Data to a document (file) request that comes back as metadata on the document
It would be great if the Box Salesforce integration has a feature wherein it will allow metadata fields of Box files take on the data of fields from records (e.g. Account/Contact) in Salesforce. When the file is uploaded, it will have the associated metadata that relates back to the account.
Searching the community forums, I could not find any post related to this requirement (the only one that was similar was from 5 yrs back and has no responses .
https://support.box.com/hc/en-us/community/posts/360049148314-Box-and-Salesforce-Integration and this forum has since been deprecated.And this link returns 'You're not authorized to access this page' https://support.box.com/hc/en-us/community/posts/11339147547283-How-can-I-connect-context-rich-information-from-business-applications-to-files-in-Box-Metadata-
I had raised Case #2916584 and was asked to raise the idea in the Pulse forum. Please consider it for the future roadmap.
Cheers
SamIt would be great if the Box Salesforce integration has a feature wherein it will allow metadata fields of Box files take on the data of fields from records (e.g. Account/Contact) in Salesforce. When the file is uploaded, it will have the associated metadata that relates back to the account.
Searching the community forums, I could not find any post related to this requirement (the only one that was similar was from 5 yrs back and has no responses .
https://support.box.com/hc/en-us/community/posts/360049148314-Box-and-Salesforce-Integration and this forum has since been deprecated.And this link returns 'You're not authorized to access this page' https://support.box.com/hc/en-us/community/posts/11339147547283-How-can-I-connect-context-rich-information-from-business-applications-to-…
1 vote -
Allow me to search by Folder ID
Allow me to search by Folder ID
5 votes -
Fix Version History for Co-Authored Files
Now that co-authoring is available on Office files (which is a great feature!) version history is paying the price. On files that are edited often, the version history is growing out of control which leads to two primary issues:
1 - Since only the last 100 versions of a file are available, the significant increase in versions caused by co-authoring means you may only have a few days worth of version history instead of months or years of history. Consider more version history and/or the ability to specify on a file how often an "accessible" version is saved for viewing later (say once a day or once a week for instance).
2 - The version history pane is very slow to load. Some performance optimizations are needed for the large increase in versions.
Now that co-authoring is available on Office files (which is a great feature!) version history is paying the price. On files that are edited often, the version history is growing out of control which leads to two primary issues:
1 - Since only the last 100 versions of a file are available, the significant increase in versions caused by co-authoring means you may only have a few days worth of version history instead of months or years of history. Consider more version history and/or the ability to specify on a file how often an "accessible" version is saved for viewing…
10 votes -
Box Embed - prevent users from navigating outside the assigned folder
If a user is assigned to the following folders e.g. All Files > Cases > Case 1.
Currently, Box Embed Breadcrumbs allow users to navigate all the way up to the All Files.
We want the users to only be able to navigate only within Case 1 folder and not explore outside Case 1. This is useful to prevent users placing content outside Case 1 when embedded inside a case management application e.g. Appian, Salesforce, etc.
1 vote -
Bulk add collaborators
Multi-select files to send collaboration invites to. I currently must do this via the API.
1 vote -
Upload images to Pulse
I submitted a feature request at support.box.com and was told to post the request here on Pulse instead. Unfortunately, I can't include screenshots here as I can in the support portal.
1 vote -
Save Collaboration Invite
I included an email address in my invite message, so the invite was not sent and I got the error, "Collaboration invite was not sent because URLs are not supported in the invite message."
I had dozens of invitees and a fairly long invite message, so it was aggravating when the invite was not saved for me to edit (remove the email in the message) and retry.
1 vote -
Restructure API endpoints to only use one base URL
We're currently pushing documents from a different system through your APIs using an integration platform.
Here we are uploading files and then assigning metadata templates to them for later use in searches and checking for versions, etc.The integration platform vendor is taking pay through every baseline URL we add to the system as a connector and then allowing us to basically have as many connections to the same system as we want using that base URL. This is relevant to our challenge.
When utilizing the Box API, the base URL (based on the documentation I've found) for uploading documents is:
"https://upload.box.com/api/2.0....."While when searching for files or uploading metadata, etc. then the baseline URL is:
"https://api.box.com/2.0/files...."Because of the baseurl difference then this means that we have to pay twice to connect to the same system.
I'm therefore wondering if you have any other endpoints or are planning to move your endpoints so that we only have to either use "https://api.box.com" or "https://upload.box.com" when connecting to Box?We're currently pushing documents from a different system through your APIs using an integration platform.
Here we are uploading files and then assigning metadata templates to them for later use in searches and checking for versions, etc.The integration platform vendor is taking pay through every baseline URL we add to the system as a connector and then allowing us to basically have as many connections to the same system as we want using that base URL. This is relevant to our challenge.
When utilizing the Box API, the base URL (based on the documentation I've found) for uploading documents…
1 vote -
Multiple IDP Support for Login
While Box Supports Multiple IDP connections to a single tenant, it is not possible without the tenant to provide a landing page for login. This is something that multiple other providers already support, and asking the customer to supply their own login page to access Box from multiple IDPs hurts both Box and the customer.
This hurts Box because instead of creating managed and secure users, I now need to juggle 3rd party users and treat them as guests rather than full users. ($)
This hurts customers by not allowing us to administer policies easily for end users as a whole. Larger conglomerate companies do not necessarily always function in the same silo's and if often takes years for them to merge structure if they even merge at all.
While Box Supports Multiple IDP connections to a single tenant, it is not possible without the tenant to provide a landing page for login. This is something that multiple other providers already support, and asking the customer to supply their own login page to access Box from multiple IDPs hurts both Box and the customer.
This hurts Box because instead of creating managed and secure users, I now need to juggle 3rd party users and treat them as guests rather than full users. ($)
This hurts customers by not allowing us to administer policies easily for end users as a…
1 vote -
Ability for Legal Hold to notify user before they drop file in Trash
Ability for Legal Hold to notify user before they drop file in Trash
2 votes -
Box Sign: Knowledge Based Authentication (KBA)
Box Sign: Knowledge Based Authentication (KBA) via integration with LexisNexis for Box Sign.
IRS requires knowledge based authentication to verify the identity of the person who is signing (confirm social security #, etc. )
DocuSign doesn't offer this unless you request it and pay extra. Box Sign could require that customers pay extra for this too.
Mortgage, banking, finance companies require this.
5% of all of my customer's signatures require using KBA.
58 votes -
MS Office @ mentions to sync and notify users
@ mention comments, tags and notifications section in Microsoft Office apps, should also integrate with Box interface and notifications. Great achievement with co-authoring, however, it is highly inconvenient to have to comment on Box preview, and then open the file to work/edit. Ideally users need to be able to @ mention and tag other colleagues/users within the MS application, which should notify other users to take action on the required document. Otherwise it creates duplication of work/inefficiencies in the process.
29 votes -
Hubspot integration same as Salesforce integration
Hubspot integration same as Salesforce integration
6 votes
- Don't see your idea?