Great minds think alike

Some contacts have a hard time receiving emails from HubSPot even after allowlisting domains and IP addresses. It would be very helpful if as a super admin I was able to create temporary passwords for those users so they can log in without the need for an email they cannot receive. ...read more

When knowledge base articles are created, we have a process for others to check those articles for accuracy. Once they are edited, there is only a filter on the backend that shows us who last updated the article but does not account for the original author. We need a way to be able to see the original author not just who last updated the article. ...read more

Language versions should be translated by AI ...read more

The new Knowledge base doesn't have an option to adjust the hamburger CSS for mobile. This includes: Hamburger svg icon - ideally colour Hamburger dropdown - background colour   This causes issues if the menu text is in white (hides the text) and the hamburger menu icon is off-brand. ...read more

Currently, when a user registers for private content, there are a few options. Password-less authentication, Social sign-on, and Single-sign on.   We have a use-case where, due to some info-security certifications we maintain, we require sign-on to any cloud platform to be challenged. Or in other words, sign-on cannot just be a simple username and password combo.   Unfortunately, this doesn't seem possible for private content with the current settings.   SSO sounds like it would work, except it requires that you have the accounts using SSO registered in the identity provider that you set up to use SSO. This is not the case for us. We want to be giving access to customers or prospects who are not affiliated with us, and so not registered in any single identity provider.   Password-less and social sign-on would meet the requirement, except that they are not enforced. Enabling them gives the users the option to use them, it does not require them to use them. So there is still nothing preventing a user from using a basic username and password.   Another common approach is MFA/2FA, sending an email, SMS or authenticator app challenge that needs to be met before access is granted, but this does not seem to be an option for Private Content.   My idea would be to have a toggle option on the Private Content settings page to require the available registration options, not just allow them.    The end user experience would then be, when registering for Private Content, they would only be able to use the selected required options, preventing them from signing up with a simple username and password.   Currently we are unable to make use of Private Content as it would go against our security certifications. We would very much like to use it though, as it's a great way to host content that we want to have more control over who is able to access it! ...read more

Looking to have additional language options added to knowledge base articles. My use case: Our products and service that we sell differ between countries served. For one example, managing returns. In the United States, our customers can simply place their returns in any USPS mailbox after attaching the prepaid return label. We have a help center document that outlines this, but in Canada, the process would be different. Since the USPS does not exist up in Canada, we'd have to direct them to go to their nearest FedEx dropoff location to ship back their returns. The complication here is that there's only one "English" option for knowledge base translation. Ideally, we could have an "English - United States" option as well as an "English - Canada" option, where we could display the appropriate knowledge base article. Depending on the customer's browser location, it would display the outline of the correct return process. ...read more

Hello, Community! I would like to suggest an improvement to HubSpot's Knowledge Base functionality, especially aimed at companies that deal with multiple teams and different areas. Currently, all team members have unrestricted access to all articles in the internal Knowledge Base. In practice, this means that articles specific to a department (such as Support, HR or Finance) are visible to the entire company — which can lead to confusion, excess irrelevant information and even unnecessary exposure of internal data. My suggestion: Implement the possibility of creating access groups or permissions by department, allowing only members of each area to view the articles that concern them. For example: The Support team would only have access to the Support knowledge base; The Finance team would only see articles related to Finance; And so on. This segmentation would help make the experience more organized, relevant and secure, in addition to making it easier for each responsible area to maintain the content. ...read more

Internal KB articles set to private access, are able to be inserted into help desk messages and links directly to said KB Article. This links a customer to a KB article they dont have access to, which muddy's the customer experience. Additionally, in help desk, private access content like KBs can be inserted into help desk conversations as a link rather than sharing information from said KB in the response. Also, you cannot leverage the right-hand side card in help desk to find private access content in the knowledge sources card. It would be great if my team didn't have to leave the help desk to view a knowledge source. We're trying to use these as internal guides for the team executing the triage themselves.  ...read more

It would be helpful if there was an option to create another subcategory within a subcategory. At the moment it is only possible to create one category + 1 subcategory. This is not enough to organize the articles in a clear and structured way. ...read more