Organize with Libraries
Libraries are the primary way to organize documents in Lore DB. A well-organized library structure makes search more relevant and sharing easier.
When to create a new library
Create a library when you have a group of documents that:
- Are related by topic, team, or project
- Should be shared with the same set of people
- You might want to toggle on/off together for search
Naming conventions
Use clear, descriptive names that tell members what to expect:
- Engineering — Backend Services (team + topic)
- Project Phoenix (project name)
- Customer Support Playbooks (function + type)
Avoid generic names like “Docs” or “Stuff” — they make it hard to decide which library a document belongs in.
Structuring your libraries
A common pattern for teams:
| Library | Purpose | Who gets access |
|---|---|---|
| Core Playbooks | Canonical, verified procedures | Everyone: Viewer. Champions: Editor |
| Team: [Name] | Team-specific documentation | Team: Editor. Others: Viewer |
| Pending Insights | AI-captured, unreviewed content | Knowledge champions: Editor |
| Personal | Private scratch space | Auto-created, private |
Documents in multiple libraries
A document can belong to multiple libraries without duplication. This is useful when a document is relevant to multiple teams. For example, an “API Rate Limiting” doc might be in both the Backend and Frontend libraries.
Library toggles
Toggle libraries on/off to control what appears in your search results. This is per-user and affects both the web UI and MCP-connected tools. Toggling a library off doesn’t remove your membership — you can toggle it back on anytime.
Start with fewer, broader libraries and split them as your collection grows. It’s easier to split a library than to merge two.