The ability to require users to have a login to access private knowledge base articles is extremely useful when you want to provide support to your end users with information that you don't want on the open internet.
It would be extremely helpful for the end user if the login they use to access those private knowledge base support articles could be the same login that they use for our own product and website.
I think this would cause users to use the support articles a lot more, but also allows us to directly link to, and closer integrate the support articles directly into our product so that relevant articles are right there where and when end users might need them, and with a single click they can then access that information, without having to go through another login first. Overall this should be a significant improvement on the experience for the end user and provide them much better support.
I would just offer, the pain point is the lift it would require to onboard customers on logging in to a separate site. We already put enough attention into the onboarding of our actual services, so adding this layer is more complex.
I agree as well. It is not very friendly to have the user create and remember two separate log ins. Totally not realistic here. That means that we also have to maintain an updated list of approved users. Also not scalable.
I heard from a source that Hubspot is thinking of only releasing this upcoming functionality to Service Enterprise customers, not Service Professional. As a Service Pro customer this will continue to render the knowledgebase absolutely worthless to us, as only paying customers should have access to our KB, and we really cannot ask them to have one set of credentials for our application and another set for accessing our KB.
Same situation here as @finn - we are a Service Pro customer and without the ability to use SSO for private resources, it's pretty useless for us. We use SSO for all our other customer platforms, even some free/open-source solutions so when it's available we'd expect to be able to use it on Pro level.
I definitely want to upvote this issue with two thumbs and two big toes.
An alternative in which a call in to a HS API can return a one-time authenticated, tamper-proof URL linking to a specific piece of content is worth considering, perhaps?
@goconnor, been nearly 5 months since you announced you were working on this feature. Couldn't agree more that this is a pretty critical improvement and for a company that's focused on customer experience, I would have thought it would be something you're looking to offer ASAP?