Knowledge Base

Give your AI agents access to your organizational knowledge by uploading documents or crawling websites. Your agents can then reference this information to provide better, more contextual responses.

Document Upload

Upload FilesAdd PDFs, Word docs, and text files to create knowledge repositories

Web Crawling

Crawl WebsitesAutomatically index websites, wikis, and documentation sites

Quick Setup

1

Create Knowledge Base

Go to Knowledge in CloudThinker and click “Create Knowledge Base”
2

Choose Type

Select Document Upload or Web Crawler based on your content source
3

Configure Settings

  • Name: Give it a descriptive name
  • Description: Brief overview of the content
  • Access: Choose who can use this knowledge base
4

Add Content

Upload documents or set up web crawling (see sections below)

Document Upload

Supported Files

  • Text: TXT, Markdown, RTF
  • Office: Word (.docx), PowerPoint (.pptx), Excel (.xlsx)
  • PDF: Adobe PDF files
  • Web: HTML, XML, JSON

How to Upload

  1. Click “Upload Document”
  2. Choose your file (max 50MB)
  3. Add title and tags
  4. Click “Upload”

Web Crawling

Basic Setup

1

Enter Website URL

Provide the starting webpage URL to crawl
2

Set Limits

  • Depth: How many clicks deep (1-10)
  • Pages: Maximum pages to crawl (100-10,000)
3

Choose Schedule

  • One-time: Single crawl
  • Daily: Update every 24 hours
  • Weekly: Weekly updates
  • Manual: Only when you trigger it

Common Examples

  • Documentation sites (GitBook, Confluence)
  • Company wikis
  • Help centers and FAQs
  • GitHub repositories

Using Knowledge Bases

Access Modes

Always Available

AutomaticAgents automatically use this knowledge in all conversations

Manual Search

On-DemandAgents only use when you ask with #kb command

Agent Commands

# Search any knowledge base
@alex #kb find AWS cost optimization strategies

# Search specific knowledge base
@tony #kb:database-guide PostgreSQL backup procedures

# Let agents decide when to use knowledge (Always mode)
@oliver analyze this security incident
# Oliver automatically references security procedures

Agent Examples

Knowledge Types:
  • AWS documentation and guides
  • Cost optimization playbooks
  • Infrastructure procedures
Example:
@alex #kb find EC2 cost savings
→ References uploaded cost optimization guide
→ Provides specific recommendations

Best Practices

Content Organization

Document Structure

Make it Searchable
  • Use clear headings (H1, H2, H3)
  • Include table of contents
  • Add relevant keywords
  • Use bullet points and lists

Tagging

Smart Organization
  • Use consistent tag names
  • Include functional tags (security, database, aws)
  • Add priority levels (critical, reference)
  • Include department/team tags

Maintenance Tips

  • Review and update content monthly
  • Remove outdated documents
  • Monitor which content gets used most
  • Test search functionality regularly

Quick Examples

Example 1: Company Procedures

Name: "Operations Procedures"
Type: Document Upload
Content: 
  - Employee handbook (PDF)
  - IT policies (Word docs)
  - Emergency procedures (PDF)
Access: Always Available
Agents: All agents can reference

Example 2: Technical Documentation

Name: "AWS Documentation"
Type: Web Crawler
URL: "https://docs.aws.amazon.com/"
Schedule: Weekly updates
Access: Manual (#kb command)
Agents: Alex (primary), others as needed

Example 3: Security Policies

Name: "Security Compliance"
Type: Document Upload
Content:
  - SOC 2 checklist (PDF)
  - Security policies (Multiple PDFs)
  - Incident templates (Word)
Access: Manual (sensitive content)
Agents: Oliver (full access), others (limited)

Getting Started Checklist

1

Plan Your Knowledge

  • Identify key documents and websites
  • Decide on naming conventions
  • Choose access levels for each knowledge base
2

Create Your First KB

  • Create knowledge base in CloudThinker
  • Upload 3-5 important documents OR set up web crawling
  • Add proper tags and descriptions
  • Test search functionality
3

Configure Agents

  • Set knowledge base access for each agent
  • Test manual search with #kb commands
  • Configure “Always Available” for critical knowledge
  • Train your team on usage commands
4

Monitor & Improve

  • Check which content gets used most
  • Update outdated information
  • Add new knowledge based on team needs
  • Gather feedback and optimize

Troubleshooting


Next Steps


Success Tips:
  • Start small with your most important documents
  • Use clear, descriptive names for everything
  • Test search functionality before going live
  • Train your team on the #kb command syntax