A workspace knowledge base holds the approved material an organization teaches from: policies, standard operating procedures, manuals, product documentation, codebooks. It supports learning, publishing, and approved AI assistance from the same sources.
Parallel training
Use the same approved material for learning and AI assistance:
- People learn it as structured courses, with progress, assessment and certificates.
- Agents answer from it on Slack, Microsoft Teams, iMessage and your own website. See Agents.
- Your own AI tools reach it over MCP, so Claude, Cursor and internal bots work from the same current material.
Connected sources refresh the Knowledge Base on their supported schedules. Check sync status before relying on a recent source change. Authors review and apply course revisions separately.
What it holds
Documents and folders with tags, versioning and full revision history, plus images that are searchable alongside text. Documents can be shared to the whole workspace, to groups, to named users, or through public links. Roles run from viewer through editor and maintainer to admin.
Screen recordings can be imported and turned into structured visual walkthroughs.
Feeding courses
Knowledge Base documents attached as course materials are snapshots of a particular version. The course materials panel checks the current Knowledge Base version and can show Source doc updated with Refresh from KB. Refresh replaces the attached material snapshot; it does not rewrite existing readings, questions, or other authored activities. Review and revise those activities, then publish through the course's delivery workflow.
Use the source version and material preview to review changes before updating the learner experience.
Readings can include inline citations back to their Knowledge Base sources, with visibility configured per course. Ask the editor assistant to cite the attached source, then open the citations during review. See the learner experience.
Integrations and MCP
Content can be imported from supported files, URLs, YouTube, GitHub Documentation, and connected document systems. Native source sync is separate from an assistant using external MCP tools such as Linear or HubSpot. A chat-tool connection does not automatically create a synced Knowledge Base folder.
Honen also exposes its own MCP interface, so an organization's existing AI tooling can read and write permitted knowledge, read and edit permitted courses, and perform authorized workspace operations. Personal sign-in uses the user's permissions; scoped Connectors add their own capability and resource limits.
Connected sources and document versions
Native source connections include Google Drive, OneDrive, SharePoint, Notion, Confluence, Document360, GitHub Documentation, and Granola. Website crawling and YouTube transcripts also bring material into the Knowledge Base. Sync scope and supported content depend on the source.
GitHub Documentation sync imports selected repository folders containing Markdown or HTML and referenced images. Referenced repository images are copied into Honen storage. The connection reads GitHub and does not write changes back to the repository. Document history preserves versions and lets authors compare changes. Updated source material can inform course revisions; authors review and apply those revisions in the course editor.
Publishing documentation
Publish Knowledge Base folders on a Site alongside courses and curricula. Choose public or restricted access, edit pages and navigation with AI, and review a live preview before publishing.
Templates and recurring maintenance
Templates can reference Knowledge Base folders so creators begin with relevant sources. They do not grant access: the creator must already be able to use the selected folders and Skills. Readings and lecture slides can reuse original source screenshots alongside cited source text.
Agents can use approved knowledge to identify outdated courses and, with proposal permission, prepare changes for human review. Schedule those tasks through Automations. Source sync alone does not approve or publish a course update.
Start with Import files and web links, Organize and use source material, or GitHub sync. Integrations and MCP explains refresh timing and connection types.
Import your team's existing content
Choose the walkthrough for the system that holds your source:
- Files, web pages, YouTube, and recordings.
- Google Drive, OneDrive, and SharePoint.
- Notion pages and Confluence spaces.
- Document360 product articles.
- Granola meeting notes and transcripts.
- GitHub Markdown, HTML, and screenshots.
Each workflow takes you from selecting the source to attaching it to a course, writing the brief, and reviewing the generated learning. Use Turn documents and recordings into a course for file-format choices and Build and maintain source-backed learning for future revisions.