As we tested the public portal experience, one of the things that turned out to be tricky was getting a knowledge base to show up as public. I didn't save the links, but there are a good number of community posts out there on this topic and we probably looked at all of them. Thanks to a HI ticket we were able to get the permissions to the KB adjusted and the articles tested. Here are the details.
Initially, we set up a new Knowledge Base called "Public KB" and added the public role via the user criteria for Can Read. Then we added and published a test article to the Knowledge Base.
Moving onto testing this. When accessing the Knowledge article from an Incognito window, we saw log entries show up in the transaction log where the guest user was trying to gain access to the pages within Knowledge.
However, the article itself still wasn't visible publicly and brought back this insufficient privileges message to a user accessing the page.
After many rounds of unsuccessful testing through tweaking Criteria and ACLs, we hit up HI support. Within the Knowledge Base form, there are two related lists not on the form by default for Cannot Read and Cannot Contribute. By default, both of these are set to exclude the Guest User.
Once we cleared out the Guest values in the list, the Knowledge Base was available for users accessing the system unauthenticated. We turned off everything associated to comments and reviews in the Knowledge Base to only show the article itself.
