General security options

Use secure links (SSL/HTTPS )

You can choose to Force SSL links so that your knowledge base will load using "https" rather than "http". SSL links ensure that all data passed between the visitor and the site is encrypted.

To use this setting, check the box next to Force SSL under Settings > Basic > Domain Setting > Knowledge Base Protocol and save.

Force SSL option under Settings > Basic

If someone tries to go to a non-secure link, they will be redirected to the secure version of the link.

All KnowledgeOwl subdomains can use SSL links and have the option to Force SSL (http links will redirect to https).

However, if you have a private domain, you will need to add your site SSL certification, chain, and key to make SSL links works. Learn more about setting up a private domain in our Private Domain guide.

We recommend everyone choose Force SSL links. It is the default for all new knowledge bases, and most major browsers (including Google Chrome, Firefox, and Edge) began marking all HTTP websites as "not secure" in 2018.

Create a public knowledge base

To make your knowledge base public and available to anyone with the link, go to Settings > Security and choose None for Access Security. If your site is public, it can show up in Google and other search engines.

Learn more about search engine optimization in our SEO guide.

Create a public knowledge base with some private content

To make some content private on your public knowledge base, you can create a reader group (or groups), restrict content to the appropriate group, and require readers to log in to get access to the reader group restricted content.

To log in readers to your site to access the restricted content, you can add a reader login/logout button to your website or use one of the other authentication methods like single sign-on or remote authentication to automatically authenticate certain readers.

Create a private knowledge base

To make your knowledge base private, go to Settings > Security and choose one of our available security options:

  • Restrict by reader logins
    Readers will be required to log in with a username and password. Users with full account admin access can set up readers, reader groups, and reader settings under Your Account > Readers (or Account > Readers for users with admin access to readers). Learn more in our Reader Management guide.
  • Restrict by IP or shared password
    Readers will need to be coming from a specified IP address or enter a shared password to access the site. You can also choose to require both an approved IP address and a password to log in.
  • Remote authentication
    Readers will be required to log in through a 3rd party site, such as your own website or application. You can use this option to automatically log in readers from your software.
  • SAML SSO (single sign-on)
    Readers will be required to log in through your specified identity provider, such as ADFS, Okta, or G Suites (Google Apps for Work). 
  • Salesforce SSO (single sign-on)
    Readers will only be able to log in through your Salesforce account. Learn how to set it up in our Salesforce SSO Configuration guide.

Create a private knowledge base with different content for different readers

To restrict content access in a private knowledge base, create reader groups for the different segment of your audience and restrict your content to the appropriate reader groups. When you create readers in KnowledgeOwl or log them in using single sign-on (SSO) or remote authentication, assign the readers to the appropriate groups.

To learn more about readers, read our Reader Management guide.

Security Setting

The security settings under the Settings tab are mostly centered around the needs of private or internal knowledge bases. By default, your knowledge base will be visible to the public which means anyone can peruse your content. However, under Settings > Security, you have quite a few options.

When would I use the different types of security?

IP-based Restriction —

This setting is great for internal office knowledge bases. If you can track down the IP addresses that your office uses, you can paste the comma separated list into the box and ensure that no one trying to access your knowledge base from outside of your office can get in.

Shared Password —

This one is great if you need to restrict access to your knowledge base but you aren't sure of your office's IP addresses or if your readers are going to be spread out. Creating a single password that you can give to everyone will allow you to control who gets in but will allow for more flexibility.

IP-based Restriction OR Shared Password—

You can also use this setting in combination with the IP protection setting for even more flexibility. What this means is that while someone is in your office they won't have to worry about logging in because they are accessing the knowledge base from an approved IP address. If they work from home one day though, they will be asked for the shared password to log in.

IP-based Restriction AND Shared Password —

Need more security? You can select to use IP-based restriction as well as a shared password for two-factor authentication.

Approved Readers —

Readers offer the most power in terms of authentication to your knowledge base. Essentially a reader is an individual login for each person or group whom you want to give access to your knowledge base. With this setting turned on, a person trying to access your knowledge base will be asked for a username and a password which we can then use to identify who they are. Once they log in, they will remain authenticated for 2 hours and can browse normally. If you select this option, you will need to set up readers under Your Account > Readers.

Restrict Content to Logged In Readers

Even in public knowledge bases, you can restrict some content so that it is only visible to specific readers. To do so, create a reader group or groups and then restrict the category or individual articles to that group.

How does restricted content work?

Readers must be logged in to see content that is restricted. When content is restricted:

  • Only readers who belong to the restricted group(s) will be able to see the content in the Table of Contents
  • Only readers who belong to the restricted group(s) will see the content in Search Results
  • Readers who do not belong to the restricted group will get a "You don't have access to view this" page if they enter the direct URL for the content

Restrictions can be set:

  • At the category level: restrictions set here will automatically cascade to all articles or sub-categories as long as those sub-categories and articles have "None / Inherit" selected.
  • At the article level: restrictions set here apply only to the individual article and don't impact other articles or categories in any way 

Restrict access based on Reader Groups

  1. If you do not have your reader groups set up, you will need to set them up by following these instructions
  2. Create a new category or article (or edit an existing one by clicking on the wrench icon to the right of any content) inside Knowledge Base > Articles.
  3. In the edit view for the category or article, select the Reader Groups should be able to view this content under Restrict to Groups in the right-hand column:
  4. Click Save.

If more than one group is selected, does a reader need to belong to all or only one of the groups?

This depends on your knowledge base's settings. Two Reader Group Logic options are supported:

  • Inclusive:
    • Example: An article is restricted to groups "Apples" and "Bananas". The article can be viewed by any reader in groups "Apples" OR "Bananas".
  • Exclusive:
    • Example: An article is restricted to groups "Apples" and "Bananas". The article can only be viewed by a reader in groups "Apples" AND "Bananas".

By default, all knowledge bases are set to Inclusive Reader Group Logic. You can check or update this by going to Settings > Security and checking the Reader Options section:

Requiring login to view files/images

The Security Settings for your knowledge base (Settings > Security ) determine the general security requirements for readers to access your knowledge base.

The files you upload to your knowledge base--PDFs, Excel sheets, screenshots, Word documents, etc.--do not automatically use this same security.

By default, even if your knowledge base requires login, the files you've uploaded do not require login. This is by design so that you can give customers the link to specific documents and they can easily download the file by clicking on that link or URL without having to log in to your knowledge base.

However, you can adjust your security settings so that readers have to be logged in to access files and images stored within your knowledge base.  If you make this change, the URLs you'll see will change slightly to a different cloudfront URL.

If you would like to require that someone must log into your knowledge base before accessing these:

  1. Go to Settings > Security.
  2. In the Reader Options section, check the Image / File Resources box next to "Require authentication to view any image or file from your file library."
    Check the box here to require login to view all files and images
  3. You'll receive a warning asking you if you're sure you want to do this. Click Cancel to keep files unauthenticated; click Proceed anyway to continue with requiring login to view files.
    File authentication "are you sure" screen 
  4. Be sure to Save your changes.

Some customers who require file authentication have noticed some issues with their upper left logos not loading properly on initial page load. If you make this change and notice issues with your logo, please contact us and let us know you're having issues. We can move your logo file to unrestricted storage so it will load faster.3