Welcome!
-
-
- Learn Home
- Core Concepts
- Companies and Departments
- Courses
- Course Status and Visibility
- Sections
- Video Activities
- Reading Activities
- Document Activities
- Enrolling People in a Course
- Bulk Enroll With CSV
- Roles in a Course
- How Progress Is Tracked
- Course Reports
- Knowledge Base Overview
- Libraries and Folders
- Uploading Content Items
- Library Visibility
- AI Agent per Library
- My Courses
- Platform People
-
- Project Structure Template
- Table of Contents (TOC)
- Content Folder
- Introduction to Markdown
- Markdown Basics
- Markdown Lists
- Markdown Links
- Markdown Images
- Markdown Code
- Markdown Tables
- Markdown Equations
- Markdown Videos
- Markdown Embedded HTML
- VS Code Snippets
- Introduction to Styles
- Framed Narrations
- Markdown Configuration
- Editor Setup
-
Library Visibility
TL;DR; Libraries don't have a visibility setting of their own. Who can open a library, and whose questions the AI agent answers from it, comes from roles on the knowledge base the library belongs to. Everyone with access to a knowledge base can see every library in it.
This page explains how that works and what it means when you decide where content goes.
Access is set on the knowledge base
Every library belongs to a department's knowledge base, and access is granted on the knowledge base, not on individual libraries:
- KB Member — browses the libraries, opens and downloads content items, and uses the AI agent.
- KB Manager — everything a Member can do, plus creating, editing and archiving libraries, managing folders and files, and re-indexing content. A KB Manager can add other KB Managers and KB Members.
Company Administrators can reach every knowledge base in their company without a separate grant. Being enrolled in a course doesn't give access to a knowledge base. See Who Can Do What for every role and where it's granted.
The AI agent follows the same rule
Anyone who can use the agent on a knowledge base can ask about every library in it that isn't archived. Ask this library keeps answers to one library and Ask the knowledge base draws on all of them, but neither is a permission boundary. There's no way to let some people ask about a library while hiding it from others with access to the same knowledge base.
Archiving a library hides its Ask buttons and leaves its content out of Ask the knowledge base answers.
Deciding where content goes
Because every library in a knowledge base is visible to everyone with access to it, putting material in a separate library doesn't keep it away from anyone. Before you upload drafts, compensation data, or manager-only material, check who holds a role on that knowledge base, and who administers your company. If some of them shouldn't see it, it doesn't belong there.
Use separate libraries for what they're good at: grouping content by topic or audience so it's easy to browse. See Libraries and Folders.
Where to go next
- Knowledge Base Overview — the bigger picture.
- AI Agent per Library — what the agent answers from.
- Who Can Do What — every role and the scope it's granted at.