We have been receiving spam from chatters on our site that includes all sorts of attachments, from documents to pictures, that are completely irrelevant. I'd like to suggest an option to disable the file attachment feature of the chatbot.
This sort of activity can be dangerous, on top of being obnoxious. We don't want anyone on our Hubspot team to click on a potentially dangerous file. In addition, disabling it would clean up much of our chat conversations.
If we have no need for attachments in our chat, we should not have to have them enabled.
Hi all- Thanks @GeoComb for posting that. We are working on getting this documentation in our API docs right now, but this is available for beta and fully supported as posted above!
I will resolve this idea as soon as we get this posted in our tech docs.
We have had teh same problem with inappropriate pictures through chat. It is silly that we cannot turn off this option. There is no reason our client's ever need to send a file through chat.
We have a client who is an attorney and it could be bad for a lead to upload something like legal documents to chat. It creates a nasty, complicated situation. Think of the financial firms and other consultant type businesses that don't want chat to be used this way.
Thanks so much for your patience while I was digging into this for you. I spoke with one of the product managers from our engineering team, and am happy to report that not only are we getting ready to roll out a beta for this feature, but I actually have a workaround that you can implement right now to disable the file upload feature in your chat widget.
You will just need to add the following script to the head HTML of any page with your chat widget on it. Seeing as your chatflow looks to be targeting all website pages, I'd recommend adding the script at the domain-level if possible. Here is that script:
Hi all- Thanks @GeoComb for posting that. We are working on getting this documentation in our API docs right now, but this is available for beta and fully supported as posted above!
I will resolve this idea as soon as we get this posted in our tech docs.
Is there not an option inside of HubSpot to disable attachments? Ideally, this would be implemented instead of requiring users to upload a code snippet to the site. Would make this easier to manage downstream.
There is not going to be an option within the UI to implement this. I thought they had done that when I posted my glowing comment, but all they actually did was to post the existing snippet. They do not intend to make a config option in the UI at this time. It would be easy to make a switch at the chat inbox to enable/disable it with simple visibility rules on the fly with JS but it isn't a priority...yet.
This really should be added as a feature. As a cybersecurity company, there are real concerns about threat actors uploading malicious documents to our site/hubspot. Hubspot, please consider adding this as a new feature!
Tried looking for documentation on disabling attachments to live chat. Surprised there was no option to disable it and a Google search lead me here.
Please consider this feature to provide an option to disable files being uploaded with chat. We've received strange images and files and worry if any of them are ever malicious.
I'm not a developer, I'm a marketing person. I'm seriously disappointed that HubSpot has not activated a simple toggle on each conversation that would allow/disable attachments. Expecting me to add code to my website on every page that a conversation appears on is ridiculous.
Important issue for legal reasons to limit communications via uploads
Important issue for security: We had chat enabled for all of a day before team members flagged it for allowing executable uploads. Where is documentation for how uploads are handled?
@cdewey22 Head section code fix per above comments appears to be ineffective. Attachment functionality is initally disabled, but reappears after first message submit from the front end. Newer docs seem to show same code. Can you shed some light? >> UPDATE: A caching plugin was interfering with normal operation; removed the script from delayed execution and the HS fix worked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.