Q: how do you define a user?
if we are a software company looking to use this for publishing support articles, would a user be our editors, would our customers end users just be the audience of the public KBs or do they need to sign in to interact and be considered a user?
AustinKerr_Trainwel
Feb 11, 2025A: Great question!
So users are internal employees with access to the system. There's the private knowledgebase which stores all information they can also be assigned courses made out of knowledgebase info. Life if you wanted to onboard a support staff. This also includes those with edit access.
For public kbs anyone can view and access the information who can access that public kb. We don't count these viewers at all.
So if you have a software team with 5 staff some who want to document some basic fundamentals about your stack and some on customer service or exec roles. You'd likely want to make those users so the 5 user plan would fit your needs. Then you can make public kbs for each software you put out and each of those you can decide which internal articles are pushed to each of those.
Hopefully that clears things up
ConComSysGreat quesiton and reply. To add ... When you say "Then you can make public kbs for EACH sotfware you put out ..." Does that infer that we can have more than 1 Knowledge base (with separate assigned permisisons & or tiered roles etc) and also put them each onto our CNAME? Thank you.
Verified purchaser
So there is one master internal kb and courses, then you can assign articles to an unlimited number of public kbs which have no features for assigning or courses. I'm considering making public courses possible but there wouldn't be the same assigning or tracking features for public courses and none exist for knwielegebase