Erich Zirnhelt
ServiceNow Employee

KB_Icon_484x252px.jpegx

In an effort to get you the information you need before you need it, we've started promoting high-impact content from our various sources (product documentation, this community, knowledge base) through a variety of channels (blog posts, Twitter, LinkedIn, Google Plus).

 

Sharing KB articles has been warmly received, except that we were only allowing signed in HI users to see them. Last week we changed that. (If you want to take your knowledge base public, this page is a great place to start.)

 

In order to enable unauthenticated access to our articles, we needed to take several steps:

  1. Create a new Audience: Public
    • We had already customized our access control so the authors simply have to pick the intended audience from a list of values: Internal, Partner, Customer. To this list we added Public.
  2. Update the user interface for users when they are not logged in
    • We did not want our users to arrive on an article and have no path out of it, so we added a Login button.   HI users can then log in and access the other HI functionality. (You may have also noticed that the search box we show at the top of every KB article is missing - we will be bring that in for unauthenticated users soon.)
  3. Manually switch selected articles to Audience = Public
    • Our content team has been focusing their efforts to make the majority of our customer-visible articles public in the coming weeks.
  4. Update our documentation

 

(There were other steps taken to enable web crawling, but I'll share those in a later post.)

 

We've already noticed an increase in article views, so this is proving to be a welcome change.   As much as possible, our future sharing efforts will refer to publicly accessible articles.

 

 

Also see..

Comments
ServiceNow Employee
ServiceNow Employee

Thanks Erich!   I can't wait to see how this changes content usage.   Really appreciate the effort.


Kilo Contributor

This will be a great way to easily search the needed knowledge at one stop shop


Tera Contributor

Hi Erich, this looks great!   We are getting ready to upgrade to Fuji.   However we are unable to make the new knowledge portal public.   Could you provide some pointers on how we can accomplish what was done on Hi to make the portal publicly accessible?   I'm referring to what is seen at this url ServiceNow Customer Service System.


It appears that this is using a custom ui page is this correct?   Any insight you can provide would be greatly appreciated.


ServiceNow Employee
ServiceNow Employee

Hi Brian,



I won't be able to answer the question completely (and I apologize for the delay - vacation ) but yes, in order to enable a public KB with Fuji's V3 of KM we had to create a custom variant of the default landing page, and a custom variant of the KB article view. The latter was most critical as that's the content that gets indexed by Google and other engines.



I check with the dev team to see if they can provide more details for you.



Thanks,
Erich


Giga Contributor

I am wondering if anyone has thoughts on the percentage of Knowledge that should be visible to 'the masses' vs. that visible to ITIL users.   For instance, at this point, 10% of our published knowledge (about 2,000 KBs) is available to those without the ITIL role.



If we desire to 'push left' by encouraging self-service and reduce calls to the Service Desk, I would think this % would need to grow to 20-33%.   Does anyone have a feel for their desired metric in this area?   What % of published KBs do you think should be available to 'the masses' in order to consider your KM successful from that perspective?



Thanks!


ServiceNow Employee
ServiceNow Employee

Hi Katherine,



though I suspect the answers will be varied, I think the KM Special Interest Group would be happy to share their thoughts!



Thanks,
Erich