# Improved security for Quote sharing **URL:** \ **Category:** HubSpot Ideas\ **Tags:** products-line-items\ **Created:** [January 24, 2023, 12:08pm UTC](https://community.hubspot.com/t/improved-security-for-quote-sharing/73593 "2023-01-24T12:08:21Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![CKerns](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ckerns/32/195161_2.png) [@CKerns](https://community.hubspot.com/u/CKerns)\ **Post date:** [January 24, 2023, 12:08pm UTC](https://community.hubspot.com/t/improved-security-for-quote-sharing/73593/1 "2023-01-24T12:08:21Z")
We have recently implemented the use of Quoting to push out from HubSpot all of our order forms to prospective customers, and upon doing so we have noted the major security flaw the URL generation has the potential to cause. The public nature of the quote, post submission/ approval, is a security risk, leaving pricing, customer and contract information available. Although the auto-generated slugs add a level of security in its complexity, there is still potential for public access and user sharing, of which is unacceptable for such a sensitive process in a customer’s journey. A few suggestions to mitigate/ remove the risk here could include; 1. Introducing password protection against quotes sent out/ URL’s generated from the process, shared only via individuals with access to the quote produced. 2. Locking down (unsure as to how) URL access based on the senders/ buyers on the quote being built/ sent out. 3. Making the URL generation ‘optional’, allowing generation of a quote without public URL against it. The first two options above are more favourable, owing to utilising the e-signature platform via linking. ---
**Author:** ![RSanchezGomez](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rsanchezgomez/32/81360_2.png) [@RSanchezGomez](https://community.hubspot.com/u/RSanchezGomez)\ **Post date:** [March 9, 2023, 8:34pm UTC](https://community.hubspot.com/t/improved-security-for-quote-sharing/73593/2 "2023-03-09T20:34:34Z")
For us, working in Cybersecurity, this is a must for us to properly send out quotes. ---
**Author:** ![David-H](https://avatars.discourse-cdn.com/v4/letter/d/e0b2c6/32.png) [@David-H](https://community.hubspot.com/u/David-H)\ **Post date:** [October 15, 2023, 4:08pm UTC](https://community.hubspot.com/t/improved-security-for-quote-sharing/73593/3 "2023-10-15T16:08:47Z")
I’m currently reviewing Hubspot to determine if we can migrate to the platform, and was shocked at how unsecure the process is for sharing a quote - and the near inability to even generate a pdf of a quote without it first being published in a public manner. (unless I’m missing something) I agree that this needs to be addressed as the current implementation probably breaks about every MSA agreement with any large organization. ---
**Author:** ![BenSa](https://avatars.discourse-cdn.com/v4/letter/b/a87d85/32.png) [@BenSa](https://community.hubspot.com/u/BenSa)\ **Post date:** [June 11, 2024, 12:06pm UTC](https://community.hubspot.com/t/improved-security-for-quote-sharing/73593/4 "2024-06-11T12:06:14Z")
The current public quote system is completely unacceptable from a security stand point. ---
**Author:** ![MYamada](https://avatars.discourse-cdn.com/v4/letter/m/f14d63/32.png) [@MYamada](https://community.hubspot.com/u/MYamada)\ **Post date:** [November 12, 2024, 3:57pm UTC](https://community.hubspot.com/t/improved-security-for-quote-sharing/73593/5 "2024-11-12T15:57:16Z")
There’s another forum that’s requesting the same thing: [https://community.hubspot.com/t5/HubSpot-Ideas/Password-Protection-for-Quotes/idi-p/427220#feedback-success](https://community.hubspot.com/t5/HubSpot-Ideas/Password-Protection-for-Quotes/idi-p/427220#feedback-success) Follow and like both and let’s fill this gap! ---
**Author:** ![JIbarra](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jibarra/32/99730_2.png) [@JIbarra](https://community.hubspot.com/u/JIbarra)\ **Post date:** [March 26, 2025, 4:27pm UTC](https://community.hubspot.com/t/improved-security-for-quote-sharing/73593/6 "2025-03-26T16:27:55Z")
I would like to address a concern raised by our customers. It has become apparent that additional security measures for quotes are necessary, as the reasons provided by our customers are both legitimate and important. Thank you Product Team! ---
**Author:** ![philmoreau](https://avatars.discourse-cdn.com/v4/letter/p/e480ec/32.png) [@philmoreau](https://community.hubspot.com/u/philmoreau)\ **Post date:** [November 14, 2025, 4:05pm UTC](https://community.hubspot.com/t/improved-security-for-quote-sharing/73593/7 "2025-11-14T16:05:32Z")
There’s already an email verification feature for signature so if it was used for viewing instead it would solve the issue. If Hubspot took security seriously as they always say they do, this could/should be improved rapidly. ---
**Author:** ![CLeabigIR](https://avatars.discourse-cdn.com/v4/letter/c/59ef9b/32.png) [@CLeabigIR](https://community.hubspot.com/u/CLeabigIR)\ **Post date:** [December 10, 2025, 7:23pm UTC](https://community.hubspot.com/t/improved-security-for-quote-sharing/73593/8 "2025-12-10T19:23:02Z")
Lack of password prohibits our company from utilizing the quotes tool, leaving is with a clunky work around. ---
**Author:** ![NBach](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/nbach/32/78271_2.png) [@NBach](https://community.hubspot.com/u/NBach)\ **Post date:** [January 9, 2026, 8:27pm UTC](https://community.hubspot.com/t/improved-security-for-quote-sharing/73593/9 "2026-01-09T20:27:31Z")
Hi all, I am the product manager for Commerce Hub Quotes and wanted to share that we’re starting work to provide authentication/access management to Quotes. Stay tuned for updates! ---
**Author:** ![philmoreau](https://avatars.discourse-cdn.com/v4/letter/p/e480ec/32.png) [@philmoreau](https://community.hubspot.com/u/philmoreau)\ **Post date:** [February 12, 2026, 8:10pm UTC](https://community.hubspot.com/t/improved-security-for-quote-sharing/73593/10 "2026-02-12T20:10:21Z")
Good to know it’s being developed, but is there an ETA for this?