Skip to main content

Public Knowledgebase

Core Web App

Would be nice to have a completely public knowledgebase that's not tied to a portal. When sensitive docs need viewed a user could enter a unique password or signed into an allowed domain.
Just to give an idea of the size… We have about 4000 users on multiple domains and a public audience of unknown people too.

1 comment

Log in to comment and vote

Comments1

  • Plum Burrito

    •

    Feb 3, 2022

    Upvoting this one, but here are my thoughts.
    The key is to keep ALL knowledgebase information within the single documentation platform.
    A public KB would allow us to create product documentation, troubleshooting articles, and FAQ. If we do this via portal we need to add every single person in a company, which is not functionality that exists in the API. Also, it would prevent us from sharing more sensitive information with key stakeholders, something I'm okay setting up the portal for currently.
    Functionality to be considered:

    • Public KB not tied to specific customer.
    • Would exist entirely to be accessed by all users, and contain no company specific information. (thinking the specific addresses and whatnot can be shared through the portal and distributed from there, or with a PDF alongside the KB URL information)
    • Wouldn't cry about the ability to grant login to public KB based on domain name only, simply due to us not wanting the KB to be completely public information.