KnowledgeTree does support linking to web-based content stored in internal wikis and any other firewalled service/repository which requires a user to authenticate, with the following limitations:

  1. Firewalled web content must be added as a URL using the Web Page option in KnowledgeTree Manager.
  2. KnowledgeTree stores and surfaces the link only; we do not store user login credentials.
  3. When KnowledgeTree users click on a link to firewalled content, we open the link in a new tab:
    -- if user has a current session running in their browser, the page/file is rendered immediately.
    -- otherwise, user is prompted to log in to the firewalled site, and is then redirected to the page/file.
  4. Thus, firewalled content can only be accessed from KnowledgeTree by internal users who have login credentials to the source service/repository. It cannot be shared with customers, b/c they would be prompted to authenticate to reach the page/file.

Bottom line:

  • Our clients can leverage KnowledgeTree to recommend and surface firewalled web content for internal consumption only. This is useful for sales enablement tools like call scripts, competitive matrices, coaching/training material, etc. that is not intended for external access.
  • All customer-facing content (datasheets, whitepapers, slide decks, videos, etc.) intended to be publicly shared with prospects must be added to KnowledgeTree using a publicly accessible link, or a supported file sharing service (see "Best practices below"); so that prospects can access, preview, and/or download that content without being prompted to authenticate.

Best practices:

  • Use KnowledgeTree's supported repositories (Box, Dropbox, Google Drive, Salesforce Content, SharePoint), or a public link on your web site (blog, resources center), for all content you intend to share with customers.
  • Use firewalled content sources for internal sales enablement materials only.
  • Use KnowledgeTree's Internal badging feature to prevent users from inadvertently sharing firewalled content with customers.
Did this answer your question?