Great minds think alike

Use the Service Hub portal to securely share documents with customers (think things like contracts and other legal documents that are unique to each customer). It seems like a portal is primarily for tickets, but it would be great if it could be extended in this way. ...read more

In regards to attachments related to a company, there does not appear to be a standard "view" option to see how many attachments a company has associated from the main companies page. In fact, attachments is not even available as an idea category below. I am new to Hubspot, and we are importing our pdf files customers have signed to their account and our partner is importing them to the attachments section.  It would also be helpful to be able to resize the "show all attachments view" as we have some long file names that cannot be seen without hovering. Overall, I am concerned there is not an "important agreements" place to place contracts within Hubspot that will not also accumulate other types of files like attachments to emails.   ...read more

We upload thousands of customer product images. The only way we can search for them now is to put every image element into the file name. For instance, patio-plants-pergola-water-feature-17. While that's great for getting a somewhat good SEO-optimized image, it's a bit of a pain. It would be great to have image tags in the file manager so we can create custom tags and then make the search experience better.  ...read more

We really need the ability to completely disable the file manager via permission sets. Please make this a feature! ...read more

We currently use Google sheets to create and send invoices. We plan to start using Hubspot. It would be great if there was a functionality to bulk import old invoices into the invoice object that we can then connect to deals, so we have all historical and present invoicing data in one place. ...read more

Hello product team,   For HubSpot admins, one of the biggest challenges is keeping a portal organized, cleaned up and prevent overall chaos. Especially in Enterprise portals with sometimes hundreds of users, it's almost impossible to get users to follow a naming convention for email names, landing page names, workflow names. Quickly this becomes a cat and mouse game where HubSpot have to constantly chase and remind users to name their assets correctly.   Why is this currently a bad user experience for users?   Naming conventions are usually documented outside of HubSpot, in a wiki, stored as a Google Doc or something similar along the same lines. Forcing them to interrupt what they're currently doing, look up a naming convention and then come back means that they're losing time. They also have to leave HubSpot momentarily. Even then, they might misunderstand the naming convention and type in an incorrect name.   Why is this currently a bad user experience for admins?   Incorrect naming means that list or workflow filters for Recent conversion might not work. It can also mean that reports become a mess, if these reports are pulling in asset names.   If admins have to look into this on a permanent basis, in portals where there are new assets every day, this takes time away from developing the HubSpot portal and generating more value for all users.   Here's what a solution could look like   To solve this, it would be great if there were tools to enforce a naming convention. Ideally, admins would specify what constitutes a correctly named asset and similar to the forms editor, arrange fields to their liking.   Here's a quick mockup of what this could look like when creating a new page.     The user could select from dropdowns which team they belong to, the language of the assets, the asset type, include a title and date. The system would then generate a title from this that cannot be further edited.   Admins should be able to specify the options for each dropdown, separators, order and field validation (e.g. max length for a title).   (In case this is eventually introduced, please consider to make this a feature that is at least included in all Professional and Enterprise subscriptions.)   I would love to see this for all assets in HubSpot: emails, workflows, lists, campaigns, imports, properties, files etc.   Thanks in advance for reviewing! ...read more

hi there,   HS is storing every attachment of an e-mail. our company is using links, logos, pictures as part of the signature. all these are stored, with extensive e-mail exchange these are adding up to hundreds of stored attachments. Making it impossible to find relevant attachments. Would it be possible, to either: - avoid auto-storage below a certain size of an attachment - allow search of attachments - allow bulk-deletion of attachments by name, size or similar thanks for having a look Best regards ...read more

Currently, all major browsers support the WebP format. Which is a great format performance-wise. Now I know that HubSpot converts other formats to WebP serverside, but we should expect users to upload the WebP format as well. One of the most powerful HubL functions is the 'resize_image_url' function, which allows you to resize the served image without having the client resize the image themselves (which is great, because clients never do this 😜). HubSpot also offers the option to clone, crop and resize images, which is a great feature of the file manager. The problem: The WebP format does not work with the 'resize_image_url', also, passing the name, width and height in the image URL does not seem to resize the image at all. So this is a major issue performance-wise. Furthermore, it currently is not possible to clone and resize a WebP image from the file manager. The solution: Make sure that the 'resize_image_url' and the file manager functionalities also work with the WebP format. ...read more

Import of a CSV file to a blog lets you automatically map columns based on column headers.  Why not support the same feature for HubDB tables.  If a column header in the imported CSV file matches a column label or column title in teh HubDB table, it should be mapped accordingly by default.   Related to this idea, it would be nice to have previous mappings remembered in successive imports, even if the CSV column headers did not match the exiting table. ...read more