Posting on behalf of a customer who was looking for a similar feature.
Use-case: they have confidential clients and do not want users from accessing articles meant for that client's users, was looking for a way to set up a seperate KB for those users.
We would also like to vote for this idea! Not only do we have confidential information that would be great not to share with all our clients and the public in general, but we also have clients all over the world meaning that being able to have a seperate KB for each language would be ideal.
We have various clients that require specific instructions that are tailored to their business and how our software integrates in their ecosystem.
We also need a platform to maintain our internal support SOPs etc.
Being able to have multiple sub-domains on the knowledge base would be ideal, and to be able to make articles visible in multiple knowledge bases, so we only have to write articles once and can appear in multiple directories.
Hey There - I am bumped to see how long this thread has been going with regular contribution yet no viable solution. For both multiple products and languages, this is an absolute must have.
Sincerely hoping this can happen in the near future!
We would love an internal Knowledge-base, we want to add to the Hubspot training all the internal processes of using Hubspot and others - this has my vote using an external tool is annoying as we want to get our colleagues to use Hubspot as much as possible
@JWharton since August, the product team contacted a few of us to get some feedbacks about the wireframes and navigation flows they designed so, hopefully, it should be live soon
This would be an extremly useful feature for us. We have different product offerings, and therefore having different independent knowledge bases would be ideal!
This feature would also be very useful for us. We work with both suppliers and independent retailers and we would like to have separate knowledge bases and different root domains for each. We would also like the option to be able to independently set each knowledge base to be private or not
The recent addition of signing in to see some articles has satisfied our Immediate Need. We now "hide" some articles for our Internal Staff to access if they are logged in. The rest are available to the public as our Gizmo Guides™ - http://kb.gizmocaresinc.com
I do wish we could have a root domain for our Knowledge Base Articles. We'd prefer http://gizmosguides.com as a root for all of our public articles.
Você deve ser um usuário registrado para adicionar um comentário aqui. Se você já estiver registrado, faça logon. Se você ainda não estiver registrado, registre-se e faça logon.