Hi @robertw you can find the instructions for setup here: Set up single sign-on (SSO) to access private content
@VictoriaGumaer - thanks. But this does not say how to protect the knowledge base AND integrate it into our existing product/authorization where our users reside.
Our customers / end-users are registered/authenticated in our system and we want to direct them to the knowledge base - potentially hosted in Hubspot in the future.
1) SSO (only available in Enterprise Edition and not even sure if this can be used for this scenario and limit it to Knowledge Base).
2) List with where an additional registration is needed. We don’t want our users to register to yet another system
Please advise.
It says that this has been delievered, but I do not see that as an accurate depiction. If I am understanding correctly we are looking to have our customers (non-hubspot users) to access/SSO into our KB through the credentials they use for our private apps without having to setup a new username/password just to access the KB (which creates a bad experience). The SSO capability that Hubspot offers now is limiting in that it only applies to internal Hubspot users accessing private KB articles, which although useful it does not give the customer a great experience and leaves our KB articles open/public if we decide we do not want to burden them with another set of credentials.
@goconnor Do you have any updates on this, it is getting increasingly more difficult to stay with Hubspots Help Center when we are constantly balancing what our customers need and what we can/cannot afford to put into a public domain. Having users have 2 separate credentials is just not an option
This one should not be closed as of now “It’s not currently possible to require SSO for an entire knowledge base.”
Doing article by article is just non sense.
Is there an update on this? Why can you not move the authentication up a level?
Does anyone have a workaround? I don’t want to have to authenticate by going to a dummy article.