Part 1 of this series gave your workers a Knowledgebase where they can create new articles, edit existing ones, or search the KB for information when responding to customers. At this point you can use the KB, as is, for your internal use or you could expand its audience by opening it up to the public. To do this you need to set up a Community Tool where your users can explore and search the KB through a public-facing web site. To create a KB community tool, click ‘helpdesk setup’, the ‘Community Tools’ tab and add a new ‘Public Knowledgebase’.

Note the Support Center also has a KB module, however the ‘Public Knowledgebase’ tool is strictly for the KB and the KB only, so I’m going to focus just on that. Access the configuration page by clicking ‘Public Knowledgebase’ in the left “Communities” column.

There are only a few options you need to worry about, the ‘URL’ and the “Public Topics”, the rest you can leave as default if you wish. Community Tools are independent of the Helpdesk interface and should be installed in a unique directory on your web server. It could really be anywhere, in its own sub-directory or on a separate web server — as long as it’s publicly accessible that’s all that matters. So for example if your Helpdesk is installed at /localhost/cerb4/ then you could install it at /localhost/cerb4/kb . The file path you choose gives the KB its own unique URL that you’ll want to include in the ‘URL’ field.

The “Public Topics” correspond to which top-level KB categories are exposed to your users. So any articles in this category and its sub-categories will be available to the public at large.

After you save your changes, the last step is to actually install the KB on your web server. Copy and paste the contents of ‘index.php’ into a index.php file on your web server, e.g. /localhost/cerb4/kb/index.php , and you’re done with setup. The KB community tool is now ready for your users.

To check out what your users will see, visit the Knowledgebase URL in your web browser. You can drill down into the public categories, search for articles, print out any information you need, and subscribe to the most “recent changes” feed.

Unless you want to expose more categories to the public, you never need to mess with the KB configuration again. If you do, simply add more topics from the ‘Community Tools’ tab and save changes, the index.php file will update automatically so you don’t have to re-copy and paste. Just keep adding new articles to the KB through the internal Helpdesk interface (see part 1), and you continue to extend your informational resources out to both your workers and your users.

-joegeck@wgm

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]


3 Comments to “Using the Knowledgebase to share resources the way you want [Part 2]”

  1. Cerberus Helpdesk Blog » Blog Archive » Using the Knowledgebase to share resources the way you want [Part 1] | December 17th, 2008 at 10:58 am

    [...] As you can see, when used in conjunction with replies the KB works very similar to F&R — workers can refer to it whenever they need to look up any information. The next major application of the KB is letting your users explore categories of your choosing, outside of the Helpdesk. We’ll cover that in part 2. [...]

  2. Kandarp Patel | March 23rd, 2009 at 10:20 am

    Before installing cerb4 I had read that the Community facing Knowledgebase would allow edits by the public (user login required). I can’t seem to find mention of this anymore. Does this feature exist/is it in the works/is it not going to happen?

    Thanks,
    Kandarp

  3. Joe Geck | March 25th, 2009 at 3:07 pm

    @Kandarp

    Hmmm, as far as I know public editing of the KB was never an option and is still not being considered at this time. I’ll apologize on behalf of WGM if we accidentally gave you this false impression, it surely was not intentional. If you happen to ever find where we mentioned this, please let us know so we can clear it up.

    I think our current stance on public editing of any resource, is that it should be limited to a wiki and be outside of Cerb4’s immediate scope.

Leave a Comment