Welcome!

Knowledge Base Overview

TL;DR; The Knowledge Base is a department-level library of reference content — documents, videos, guides — that learners can browse and that an AI agent can use to answer questions. Each department has its own libraries. It's separate from courses, though the same content can live in both.

Courses are great for structured, sequenced learning. But most of what people want to look up at work isn't a course — it's a specific answer, right now, without sitting through a 30-minute module. That's what the Knowledge Base is for.

What's in a Knowledge Base

A department's Knowledge Base is made up of:

  • Libraries — the top-level containers. A department can have multiple libraries for different topics or audiences.
  • Folders — subdivisions inside a library for keeping related content together.
  • Content items — the actual files or resources (PDFs, Markdown docs, text files, videos).

The full hierarchy is: Department → Library → Folder → Content Item.

How the Knowledge Base compares to Courses

Both live in a department. Both hold files. But they serve different purposes:

  • Courses are sequenced, tracked, and "taken." Learners have progress, completion, and roles.
  • Knowledge Bases are browsable and searchable. There's no progress, no completion, no roles. A learner just opens a library and reads what they need.

You should put content in a course when:

  • The content is structured and needs to be consumed in order.
  • You need to track completion (for compliance, for onboarding, etc.).
  • There's a cohort of learners going through it together.

You should put content in a library when:

  • It's reference material someone would look up on demand.
  • It doesn't have a beginning or an end.
  • You don't need to know who read it.
  • It's shared across multiple courses and you don't want to duplicate it.

A lot of good content ends up in both places. Put the source of truth in the library, and attach the same file as a document activity inside any course that requires it.

The AI agent on libraries

This is the feature that makes Lupo's Knowledge Base distinctive: each library can have a dedicated AI agent that answers questions using the library's content as context.

Learners type a question, and the AI answers based only on what's in that library — not the broader internet. It's essentially a "chat with your knowledge base" experience, scoped to one department's approved content.

The AI agent per library is one of the highest-value features in the LMS. It's almost at production quality today — close enough that you should try it if your plan allows. See AI Agent per Library for more.

When Knowledge Bases are worth building out

A department should invest in its Knowledge Base when:

  • Employees ask the same questions repeatedly. If the same five questions hit your HR or Support team every week, those answers belong in a library with an AI agent on top.
  • Onboarding involves a lot of reference material. Put the policies, the tooling guides, and the "how we do things here" docs in a library that new hires can open whenever they need.
  • You have existing documentation scattered across places. If your team has a Google Drive, a Confluence, and a SharePoint, consolidating the most-used pieces into a Lupo library gives you a single place to look.

Don't build a Knowledge Base for its own sake — build it when you have content that's actively useful and a place for it to go.

Where to go next