Hi [First name],
Every knowledge base has an audience and an authentication method, even if that audience is "everyone on the internet" and the authentication method is "none."
Different authentication options can open up your knowledge base to do more for you than you had perviously thought possible.
Many knowledge bases start out with a single use case and audience and then, as time goes by, need to adapt to handle new audiences and use cases.
We thought this could be a really helpful topic for our customers, as the options are many, and the different contexts feel near infinite. Let us show you what is possible!
What we'll cover:
Three common knowledge base authentication patterns (public, private, and mixed) and the considerations and settings to focus on in each setup, including:
Using a public knowledge base open to the public and which settings to explore to maximize your SEO/GEO
Having all employees on a shared VPN access a knowledge base without entering passwords
Using a single shared password for an entire knowledge base (most common for testing setups or when you're providing one knowledge base to each client)
Setting up a private knowledge base and creating and managing individual reader accounts within KnowledgeOwl
Setting up a private knowledge base using Single Sign-On
Setting up a knowledge base with some public content and some content requiring login (what we call a "mixed" authentication strategy)
Who should attend:
You're a KnowledgeOwl author or admin.
You want to understand what the authentication options within KnowledgeOwl are and when to use them.
You already feel like you need to change your authentication strategy (or suspect you may need to in the future).
You're fielding questions from your leadership about whether KnowledgeOwl supports xx people accessing the knowledge base in yy way.