What Is Knowledge?
Knowledge pages are collaborative documents organized in a hierarchical tree structure. Unlike AI-generated Documents, Knowledge pages are manually authored content that you create and maintain—perfect for internal documentation, processes, and reference materials.Hierarchical Organization
Organize pages in a parent-child tree structure for intuitive navigation
Rich Text Editing
Full-featured editor with formatting, tables, links, and markdown support
Real-Time Auto-Save
Changes save automatically as you type—never lose your work
Search & Discovery
Full-text search across all pages to find information quickly
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
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 |
Core Features
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
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: Find pages by title or content instantly
- Tree navigation: Browse the hierarchical structure in the sidebar
- Page icons: Add emojis to visually identify pages
- Drag-and-drop: Reorganize pages by dragging them to new locations
Getting Started
1
Access Knowledge
Navigate to the Knowledge section in the left sidebar
2
Create Your First Page
Click the ”+” button to create a new root-level page
3
Add Content
Click into the editor and start writing. Your content auto-saves as you type.
4
Organize with Subpages
Create subpages to build out your documentation hierarchy
5
Customize with Icons
Add emoji icons to pages for visual organization
Common Use Cases
- Product Teams
- Sales & Success
- Leadership
- Operations
- 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
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
Email Templates
Email 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”
- “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”
Meeting & Call Guides
Meeting & Call Guides
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”
- “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”
Customer Communication
Customer Communication
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”
- “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
Sales Playbooks
Sales Playbooks
- “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”
Customer Success Playbooks
Customer Success Playbooks
- “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”
Product & Operations
Product & Operations
- “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
Internal Documentation
Internal Documentation
- “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”
Customer-Facing Content
Customer-Facing Content
- “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”
Training Materials
Training Materials
- “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?”
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.