Today, internal KBs can only be accessed by users logged in to Front. External KBs can be accessed by anyone with the link. We do not support custom authentication for readers to access either of these KBs.
Many organizations, including our own, will have a mixture of Front and non-Front users. Making internal knowledge bases ONLY accessible to Front users is a Deal Breaker.It would be better for an organization like ours to invest in a 3rd-party knowledge base platform, and make it available via a side panel, than try to make a hobbled, low-feature Front knowledge base work, and still need to use separate knowledge base solution to fill in the gaps.
can see that you have only 2 options :
Internal to our users
ideas: It would be great to have another option:
Kind of a auth api, that we could authenticate our users, so they can get access to the knowledge center. I can understand that this could be complicated to setup.
Or maybe much simpler, like youtube does with videos - The video is not "public" so we cannot search for it, BUT we can embed it. So we could embed the knowledge center inside our SaaS application - with maybe a domain restriction.
This would be really useful because it would broaden the uses of Knowledge Base!