Knowledge Management System in Notion – Introducing Vaults (Life OS)
Based on August Bradley's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Knowledge management is separated into vaults (Book Vault, Media Vault, Training/Academy Vault) so extracted insights can be reused without re-consuming sources.
Briefing
A knowledge management system built inside Notion is designed to turn scattered inputs—books, articles, courses, podcasts, and personal reflections—into “vaults” that steadily grow into reusable, context-ready insight. The core idea is that knowledge shouldn’t sit in isolated databases. Instead, it should flow into a central Knowledge Lab where the best material gets synthesized by topic, and where related notes resurface automatically when someone needs them for a decision, conversation, or deliverable.
The vault layer sits at the heart of a broader “Life OS” structure. Earlier work focused on projects and tasks, but knowledge management lives entirely in vaults—independent resources meant to capture information, process it into actionable understanding, and then feed pipelines like goals, projects, and tasks. Over time, each vault becomes more valuable as it aggregates and synthesizes inputs into a living resource—described as a “gold mine” of thoughts, ideas, and best thinking.
The system starts with a Mind Expansion dashboard that acts like an intake hub. Three input streams feed the Knowledge Lab: (1) Notes and Ideas for personal thoughts, reflections, and team member thinking; (2) Knowledge Sources for books and other media; and (3) the Academy for courses and formal training. Each stream is organized as its own Notion vault (Book Vault, Media Vault, Training/Academy Vault), and the Knowledge Lab is presented as the culmination where the most useful pieces from those sources are pulled together.
Inside the Book Vault, the emphasis is on extraction and prioritization. Books are tracked by reading status (actively reading, queued, to-read, finished), and notes come from either hierarchical highlighting or writing summaries in one’s own words. Hierarchical highlighting uses more than two emphasis levels to capture nuance, while summarizing in personal language is framed as more effective for retention—at the cost of time. The system also supports audio books and different formats, with Kindle favored for easier highlighting and note-taking.
The Media Vault mirrors the same principle for articles, videos, podcasts, and embedded media. Finished items are treated as “gold mines” because extracted highlights and notes can be revisited quickly without re-consuming the entire source. The Training/Academy Vault focuses on course learning: instead of lightweight notes, it builds course dashboards using Notion database fields, subpages, and toggle pages so expensive training can be mined later.
Personal or team thinking lands in a Notes and Ideas database. Entries are easy to capture and then linked to either a Knowledge Lab topic or a dashboard category (for teams: departments like sales, marketing, HR; for individuals: life domains like fitness or family). Each note includes relational links to its source (book or media) and to the Knowledge Lab topic it supports, plus status and sorting (often by last edited) to make retrieval fast.
The Knowledge Lab is where synthesis happens. Each topic entry collects the best extracted material from books, media, and courses, then pulls in linked notes and ideas through a self-referencing filter. A Notion “slash toc” table of contents feature helps navigate deeper outlines within each topic. Crucially, notes resurface contextually: instead of relying on arbitrary time-based reminders, the system brings relevant notes into view when someone enters a topic area—so the information is timely because it’s tied to the moment of use.
Overall, the system aims to create a continuously improving knowledge base: quick capture at the edges, structured extraction from sources, synthesis by topic in the Knowledge Lab, and retrieval that feels “automatic” because it appears in the right context when work demands it.
Cornell Notes
The vault-based Notion system is built to convert raw inputs—personal notes, books, media, and courses—into topic-specific “Knowledge Lab” pages that grow more valuable over time. Each vault (Book Vault, Media Vault, Training/Academy Vault) emphasizes extraction: hierarchical highlighting and/or summaries for books, and structured notes for articles, videos, and podcasts. Notes and Ideas are captured quickly, then linked to either Knowledge Lab topics or dashboard categories so they can resurface later. Retrieval is designed to be context-driven: when someone opens a topic in the Knowledge Lab, linked notes appear automatically, sorted by last edited, making the knowledge timely without relying on arbitrary review timers.
Why are “vaults” treated as independent resources rather than just another database?
What’s the difference between hierarchical highlighting and writing notes in one’s own words?
How does the system make course learning retrievable later?
How do Notes and Ideas become useful instead of clutter?
What makes retrieval “contextual” in the Knowledge Lab?
How does the Knowledge Lab synthesize information from multiple vaults?
Review Questions
- How do hierarchical highlighting and personal-word summaries each contribute to knowledge extraction, and when would you choose one over the other?
- Describe the flow from a raw input (like an article or a spontaneous idea) to its eventual appearance inside a specific Knowledge Lab topic.
- What mechanisms in the Notes and Ideas database and Knowledge Lab entry design help ensure notes resurface at the right time and place?
Key Points
- 1
Knowledge management is separated into vaults (Book Vault, Media Vault, Training/Academy Vault) so extracted insights can be reused without re-consuming sources.
- 2
The Knowledge Lab is the synthesis layer: it aggregates the best material by topic and connects related topics through internal links.
- 3
Notes and Ideas must be easy to capture, but also linked to either Knowledge Lab topics or dashboard categories so they can resurface in context.
- 4
Hierarchical highlighting uses multiple emphasis levels to preserve nuance, while summarizing in one’s own words improves retention at the cost of time.
- 5
Course learning is stored as structured dashboards (subpages/toggles) so expensive training can be mined quickly later.
- 6
Retrieval is designed to be contextual rather than time-based: opening a Knowledge Lab topic automatically filters and displays the relevant linked notes.
- 7
Team use is supported through department-based dashboards and filtered views so shared knowledge streams stay organized and actionable.