Welcome!

Collections and Knowledge Bases

TL;DR; A Collection is what the Knowledge picker calls a department — pick one and you land on that department's Knowledge Base. There's exactly one Knowledge Base per department, and it's created automatically the first time anyone opens it.

Before you start

See Departments — a Knowledge Base always belongs to one department.

Steps

  1. Open Knowledge from the top nav. The Collections picker shows one card per department you have access to — its name, its company, and how many libraries it holds. You can search the cards, switch to a list, and group them by company.

    Knowledge picker showing Collection cards grouped by company, each with a library count

  2. Selecting a Collection (Open Knowledge Base) takes you straight to that department's Libraries list. That list is the Knowledge Base's home — there's no separate landing page beyond it.

  3. There's nothing to explicitly create here: the first time anyone opens a department's Libraries area, Lupo provisions its Knowledge Base for you automatically, named " Knowledge Base."

What this doesn't do

"Collection" doesn't name a separate object you create or configure — it's the picker's label for a department. There's no Collection settings page, and nothing to set up beyond having a department with Learn enabled. When the picker is empty, its Create a knowledge base button simply takes a Company Administrator to Create Department — a new department is what brings a new Knowledge Base with it.

If you can see the picker but hold no role in any department's Knowledge Base, it tells you so: access is granted per department, so someone has to add you to the one your team uses — see Knowledge Base access.

Where to go next