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
- Single File
- Multiple Files
- Click “Upload Document”
- Choose your file (max 50MB)
- Add title and tags
- 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 commandAgent Commands
Agent Examples
- Alex - Cloud Engineer
- Oliver - Security
- Tony - Database
Knowledge Types:
- AWS documentation and guides
- Cost optimization playbooks
- Infrastructure procedures
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
Example 2: Technical Documentation
Example 3: Security Policies
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
#kbcommands - 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
Agents can't find information
Agents can't find information
Solutions:
- Check if agent has access to the knowledge base
- Verify knowledge base is set to “Always Available” or use
#kbcommand - Improve document titles and add more keywords
- Test search with different terms
Documents won't upload
Documents won't upload
Solutions:
- Check file size (max 50MB per file)
- Ensure file type is supported
- Verify document isn’t password-protected
- Try uploading one file at a time
Web crawling not working
Web crawling not working
Solutions:
- Verify the website URL is accessible
- Check if website blocks crawlers (robots.txt)
- Start with smaller page limits
- Try crawling a single page first
Next Steps
🚀 Create Knowledge Base
Get Started NowCreate your first knowledge base and start uploading content
🤖 Configure Agents
Setup AI AgentsConfigure your agents to use your knowledge bases effectively
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
#kbcommand syntax