> ## Documentation Index
> Fetch the complete documentation index at: https://docs.buildbetter.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Knowledge Overview
> Create, share, review, and manage team knowledge, reusable skillsets, groups, and institutional context
Knowledge is BuildBetter's workspace for team context. It includes collaborative knowledge pages, reusable Skillsets, groups, sharing controls, revision history, activity tracking, and review workflows so teams can maintain the context that powers chat, projects, personas, and agent work.
## What Is Knowledge?
Knowledge pages are collaborative documents and reusable context objects organized for teams. Unlike AI-generated Documents, Knowledge content is maintained by your workspace and can be shared, reviewed, revised, and reused across workflows.
Organize pages, groups, and reusable context in structures your team can browse
Full-featured editor with formatting, tables, links, and markdown support
Share Knowledge with the right people and manage group-level access from Settings
Track revisions, activity, and review state so important context stays current
## When to Use Knowledge
### Internal Documentation
* **Process documentation**: Standard operating procedures, workflows, and how-to guides
* **Onboarding materials**: New team member resources and training content
* **Best practices**: Team playbooks, templates, and guidelines
* **Reference guides**: Technical documentation, API notes, and system overviews
### Team Collaboration
* **Meeting notes repository**: Centralized location for recurring meeting notes
* **Project documentation**: Project-specific information and context
* **Decision logs**: Record important decisions and their rationale
* **FAQ pages**: Common questions and answers for your team
* **Skillsets**: Reusable skills, prompts, and operating context that can be managed from the Build app
### Institutional Memory
* **Customer insights**: Synthesized learnings from customer interactions
* **Competitive intelligence**: Information about competitors and market
* **Product context**: Feature explanations, roadmap notes, and priorities
* **Historical documentation**: Archive of important past initiatives
## Knowledge vs Documents
Understanding when to use Knowledge pages versus BuildBetter Documents:
| Feature | Knowledge Pages | Documents |
| ---------------- | ------------------------------ | --------------------------------- |
| **Creation** | Manually authored | AI-generated from data |
| **Purpose** | Reference materials, processes | Insights, summaries, reports |
| **Organization** | Hierarchical tree structure | Flat list with permissions |
| **Content** | Static documentation | Dynamic, data-driven content |
| **Best for** | Playbooks, SOPs, guides | PRDs, meeting summaries, analysis |
Use Knowledge pages for content you write and maintain yourself. Use Documents when you want AI to generate content from your calls, signals, and data.
## Core Features
### Groups, Sharing, and Reviews
Knowledge now supports team-oriented controls beyond a simple page tree:
* **Groups** let you organize access around teams, functions, or projects.
* **Flexible sharing** controls who can view, edit, or review important content.
* **Revision history** helps you inspect how a page or skillset changed over time.
* **Activity tracking** shows recent edits and review movement.
* **Review flows** help keep high-value Knowledge current before teams rely on it.
Older Skillsets links redirect into the current Knowledge experience. Existing Skillsets remain available, but the management surface now lives under Knowledge.
### Skillsets Catalog
Skillsets are reusable bundles of skills, prompts, and team context. Use them when you want repeatable behavior from BuildBetter or coding-agent workflows.
* Browse organization-wide Skillsets from Knowledge
* Create, edit, delete, and reorder skillsets and skills
* Review summaries before opening full details
* Copy content to the clipboard
* Use source links and metadata to understand where a skill came from
### Page Hierarchy
Organize your knowledge base with nested pages:
* Create root-level pages for major categories
* Add subpages to build out detailed sections
* Drag and drop to reorganize your structure
* Expand and collapse sections for easy navigation
* Move pages safely with invalid nesting blocked before it can break the tree
### Rich Text Editor
The Knowledge editor supports:
* **Text formatting**: Bold, italic, underline, and links
* **Structure**: Headings, bullet lists, and numbered lists
* **Tables**: Create and resize tables for structured content
* **Markdown**: Write in markdown for faster editing
### Organization & Navigation
Keep your knowledge base organized:
* **Search with Highlights**: Find pages by title or content instantly, with matching text highlighted in results
* **Pagination**: Browse large knowledge bases with paginated results for faster loading
* **Tree navigation**: Browse the hierarchical structure in the sidebar
* **Orphan Detection**: Pages without a parent are flagged so you can reorganize or clean them up
* **Delete Confirmation**: Deleting a page prompts for confirmation and shows affected child pages to prevent accidental data loss
* **Page icons**: Add emojis to visually identify pages
* **Drag-and-drop**: Reorganize pages by dragging them to new locations
* **Hierarchy Safeguards**: Legacy cyclic relationships are cleaned up automatically, and nested pages stay visible even when older page ID formats differ
## Getting Started
Navigate to the Knowledge section in the left sidebar
Click the "+" button to create a new root-level page
Click into the editor and start writing. Your content auto-saves as you type.
Create subpages to build out your documentation hierarchy
Add emoji icons to pages for visual organization
## Common Use Cases
* **Product playbooks**: Launch processes, release checklists
* **Feature specifications**: Detailed feature context and requirements
* **Research summaries**: Synthesized insights from user research
* **Competitive landscape**: Competitor analysis and positioning
* **Sales playbooks**: Objection handling, discovery frameworks
* **Customer profiles**: Key account information and history
* **Implementation guides**: Onboarding processes for customers
* **Success metrics**: KPIs and tracking methodologies
* **Strategic plans**: Company and team objectives
* **Decision frameworks**: How major decisions are made
* **Org context**: Team structures, responsibilities, processes
* **Board materials**: Templates and historical presentations
* **SOPs**: Standard operating procedures
* **Training materials**: Onboarding and upskilling content
* **Tool documentation**: How-to guides for internal tools
* **Policy documents**: HR, security, and compliance policies
## Chat Prompts for Knowledge Pages
Use the BuildBetter chat assistant to help create, refine, and leverage your knowledge pages. Here are practical prompts to get started:
### Writing & Communication Templates
**Create email templates:**
* "Help me write a follow-up email template for after discovery calls"
* "Create an email template for introducing our product to new prospects"
* "Write a renewal reminder email template for customer success"
* "Draft an internal announcement template for new feature releases"
**Refine existing emails:**
* "Make this email more concise and action-oriented"
* "Rewrite this email to sound more professional but friendly"
* "Add a clear call-to-action to this customer email"
**Discovery call frameworks:**
* "Create a discovery call script with qualifying questions for enterprise prospects"
* "Write a QBR agenda template with talking points for customer success"
* "Draft a demo script outline for our main product features"
**Meeting preparation:**
* "Create a pre-call research checklist for sales calls"
* "Write a meeting follow-up template with action items section"
* "Draft an agenda template for weekly team syncs"
**Support responses:**
* "Write a response template for common billing questions"
* "Create a troubleshooting guide template for support tickets"
* "Draft escalation communication templates for urgent issues"
**Success outreach:**
* "Create a check-in email sequence for new customers"
* "Write a template for sharing product updates with customers"
* "Draft a customer feedback request template"
### Process & Playbook Creation
* "Create an objection handling guide for pricing concerns"
* "Write a competitive battlecard template for \[competitor name]"
* "Draft a qualification checklist using MEDDIC framework"
* "Create a negotiation playbook for enterprise deals"
* "Write a handoff process from sales to customer success"
* "Create an onboarding checklist for new customers"
* "Write a health score criteria guide with red/yellow/green definitions"
* "Draft a renewal playbook with timeline and touchpoints"
* "Create an escalation process for at-risk accounts"
* "Write a customer expansion playbook for upsell opportunities"
* "Create a feature request intake process"
* "Write a bug triage guide with severity definitions"
* "Draft a release checklist for product launches"
* "Create a user research interview guide template"
* "Write an incident response playbook"
### Documentation & Reference
* "Create a glossary of terms our team uses"
* "Write an FAQ page for new team members"
* "Draft a tool stack overview with links and owners"
* "Create a decision log template with context and rationale sections"
* "Write a team charter template with roles and responsibilities"
* "Create a product FAQ based on common customer questions"
* "Write a getting started guide outline for new users"
* "Draft a best practices guide for \[feature/workflow]"
* "Create a troubleshooting guide for common issues"
* "Write a use case guide showing different ways to use our product"
* "Create a training curriculum outline for new sales reps"
* "Write a certification checklist for customer success managers"
* "Draft a shadowing guide for onboarding new team members"
* "Create a skills assessment template for team development"
* "Write a coaching framework for managers"
### Using Chat with Your Knowledge Pages
Once you've created knowledge pages, you can reference them in chat:
* "Based on our sales playbook, how should I handle this pricing objection?"
* "Using our onboarding checklist, what steps are we missing for this customer?"
* "Compare this customer's situation to the criteria in our health score guide"
* "Help me customize our email template for this specific prospect"
* "What does our process documentation say about handling escalations?"
Create knowledge pages for your most common workflows first, then use chat to help you apply those templates to specific situations. This combination of documented processes + AI assistance is powerful for consistency and speed.
## Best Practices
### Page Organization
* **Use clear naming**: Make page titles descriptive and searchable
* **Limit nesting depth**: Keep hierarchy to 3-4 levels maximum
* **Group related content**: Use parent pages to organize categories
* **Add context**: Include emoji icons to help with visual scanning
### Content Quality
* **Keep pages focused**: One topic per page for easier maintenance
* **Include examples**: Add concrete examples to illustrate concepts
* **Link between pages**: Reference related pages to build connections
* **Update regularly**: Schedule periodic reviews to keep content fresh
Knowledge pages are workspace-scoped, meaning all members of your workspace can view and edit them. Use the tree structure to create clear ownership and organization.