Wasting $772K Searching Docs? Build Knowledge Base in Odoo 18
By Braincuber Team
Published on December 22, 2025
New employee asks: "Where's the onboarding checklist?" Senior dev: "Check Google Drive... wait, it might be in Confluence... or was it Notion? Check email from 2 months ago." 45 minutes later: Found 3 versions of same document in 3 places. All outdated. Nobody knows which is correct. New hire confused. Productivity day 1: Zero.
Your knowledge chaos: Company knowledge scattered across Google Drive (847 files), Confluence (23 spaces), Notion (14 workspaces), SharePoint (ancient), email attachments (thousands), people's desktops. Search for "client onboarding process"—get 17 results, 12 outdated, 5 conflicting versions. Nobody maintains docs (too busy). Tribal knowledge in senior employees' heads (what happens when they leave?). New hires take 3 weeks to find basic info. Support team answers same questions 40 times monthly (no centralized FAQs).
Cost: Time wasted searching for docs = 4.7 hours weekly per employee × 47 employees × 52 weeks × $67/hour = $772,772/year. Duplicate tools (paying for Drive, Confluence, Notion, SharePoint) = $23,400/year subscriptions. New hire ramp-up time = 6 weeks vs industry 3 weeks = $47,000 per hire in delayed productivity × 12 hires = $564,000/year. Support inefficiency answering repeat questions = 40 questions × 15 min avg × 4 reps × 52 weeks × $42/hour = $87,360/year. Knowledge loss when employees quit = impossible to quantify but massive.
Odoo 18 Knowledge Module fixes this: Centralized wiki inside Odoo—all documentation one place. Hierarchical organization (parent articles, child articles, categories). Rich text editor (headings, images, tables, code blocks, embedded videos). Version history (track changes, restore previous versions). Access control (private articles, team articles, public articles). Templates (standard formats for SOPs, meeting notes, project docs). Search everything instantly. Collaborative editing (multiple people same time). Here's how to build company knowledge base so you stop losing $772K annually to scattered docs.
You're Losing Money If:
What Odoo 18 Knowledge Module Does
Company-wide wiki integrated with Odoo. Create articles (SOPs, FAQs, project docs, meeting notes), organize hierarchically, control access, collaborate in real-time, track versions, use templates.
| Scattered Tools (Drive/Confluence/Notion) | Odoo Knowledge (Centralized) |
|---|---|
| Search 5 different tools, 4.7 hrs/week wasted | Search one place, find instantly |
| 17 versions, which is correct? | Version history tracks all changes, restore any version |
| Can't link docs to CRM/Projects/Sales | Integrated: Link articles to leads, projects, tasks |
| $23K/year tool subscriptions | Included with Odoo (no extra cost) |
| No templates (everyone recreates) | Save as template, reuse instantly |
Step 1: Access Knowledge Module
- Go to Apps
- Search:
Knowledge - Click Install (if not installed)
- Access: Knowledge from main menu
Step 2: Create Your First Article
Create New Article
- In Knowledge module, click + New
- Enter article title (e.g., "Employee Onboarding Checklist")
- Article editor opens with rich text toolbar
- Start writing content using formatting tools:
- Headings: H1, H2, H3 for structure
- Lists: Numbered, bulleted, checklists
- Text formatting: Bold, italic, underline, code
- Links: Internal (other articles) or external URLs
- Media: Images, videos, files
- Tables: Structured data
- Content auto-saves as you type
✓ Article Created!
Article appears in sidebar. Click to view/edit anytime. Changes saved automatically.
Step 3: Organize with Hierarchy
Create Child Articles
- Open parent article (e.g., "Employee Onboarding Checklist")
- Right sidebar shows "Articles" panel
- Click + Add in Articles panel
- Create child article (e.g., "Day 1 Tasks")
- Child article nested under parent in sidebar tree
- Repeat to create more children:
- "Week 1 Goals"
- "Month 1 Milestones"
- "Required Training Modules"
Example Hierarchy:
📄 Day 1 Tasks
📄 Week 1 Goals
📄 Month 1 Milestones
📄 Required Training Modules
📁 Sales Playbook (parent)
📄 Discovery Call Script
📄 Demo Presentation
📄 Objection Handling
📄 Pricing Guidelines
Step 4: Control Access with Sharing
Set who can view/edit each article.
Configure Article Permissions
- Open article
- Click Share button (top right)
- Set Default Access Rights:
- Can Edit: All internal users can view + edit
- Can Read: All internal users can view only (read-only)
- No Access: Article private (hidden from everyone except invited)
- Invite specific users/teams:
- Click Invite
- Select users or teams
- Set permission: "Can Edit" or "Can Read"
- Invited users get access even if default is "No Access"
- Click Done
Access Control Examples:
Company-Wide FAQ
Default: Can Read (everyone can view, only admins edit)
Engineering Team Docs
Default: No Access + Invite: Engineering team (Can Edit)
Meeting Notes
Default: Can Edit (all participants can contribute)
Step 5: Enhance Articles with Visual Tools
Add Cover Image
- Open article
- Click ⋯ (three dots) menu → Add Cover
- Choose method:
- Upload from device: Browse local files
- Insert from URL: Paste image URL
- Adjust position: Click Reposition to frame image
- Cover appears at top of article (visual identity)
- To remove: Click cover → Remove Cover
Add/Remove Icons
- Open article
- Click ⋯ menu → Add/Remove Icon
- Select icon from library (📊 📁 ⚙️ 💡 ✅ etc.)
- Icon appears next to article title in sidebar
- Helps visually categorize articles at glance
Add Custom Properties
Add metadata fields (tags, owner, status, due date).
- Open article
- Click ⋯ menu → Add Properties
- Click Add a Property
- Configure property:
- Label: Property name (e.g., "Owner", "Status", "Due Date")
- Field Type: Text, Number, Date, Checkbox, Selection
- Enter value in right sidebar
- Property saved automatically
- Repeat to add more properties
Property Examples:
Step 6: Collaborate with Team
Use Chatter for Comments
- Open article
- Click 💬 Chatter icon (top right)
- Chatter panel opens showing:
- All messages/comments on this article
- Activity log (who edited, when)
- Scheduled activities/tasks
- Add comment: Type message → Click Send
- @ mention users: Type
@John Smithto notify - All collaborators see comments in real-time
Add to Favorites
- Open article
- Click ⭐ Add to Favourites (top right)
- Article pinned to favorites list
- Access favorites: Top-right corner shows all starred articles
- Quick access to frequently used docs
Step 7: Protect Content
Lock Content
Prevent accidental edits to finalized documentation.
- Open article
- Click ⋯ menu → Lock Content
- Article becomes read-only for all users
- Editing toolbar disabled
- Prevents accidental changes to:
- Official SOPs
- Compliance documentation
- Published guidelines
- To unlock: Click ⋯ → Unlock Content (admin only)
Step 8: Track Changes with Version History
- Open article
- Click ⋯ menu → Open Version History
- History panel shows all revisions:
- Date/time of change
- User who made edit
- Summary of changes
- Click any version to preview
- To restore old version:
- Open version
- Click Restore this version
- Confirmation prompt
- Article reverts to selected version
💡 Version History Use Cases:
- Undo accidental deletion: Restore version before content removed
- Track who changed what: Audit trail for compliance
- Compare versions: See what evolved over time
- Recover from bad edits: Restore last known good version
Step 9: Create Templates for Reuse
Save Article as Template
- Create article with standard structure (e.g., "Meeting Notes Template")
- Add sections: Date, Attendees, Agenda, Discussion, Action Items, Next Meeting
- Format with headings, bullet points
- Click ⋯ menu → Add to Templates
- Template saved to templates library
- To use template:
- Click + New
- Bottom-left: Browse Template Library
- Select template
- New article created with pre-filled structure
- Fill in content, save
Useful Templates:
- Meeting Notes: Date, Attendees, Agenda, Discussion, Actions, Next Steps
- Project Brief: Overview, Goals, Timeline, Team, Budget, Risks
- SOP (Standard Operating Procedure): Purpose, Scope, Procedure, Responsibility, References
- Troubleshooting Guide: Symptom, Cause, Solution, Prevention
- Product Feature Doc: Overview, User Story, Requirements, Design, Testing
Step 10: Additional Tools
Move Article to Different Location
- Open article
- Click ⋯ → Move To
- Popup shows workspace tree
- Select new parent or workspace
- Click Move
- Article relocated, all child articles move too
Create a Copy
- Open article
- Click ⋯ → Create a Copy
- Duplicate created with suffix "(copy)"
- Independent article (changes don't affect original)
- Useful for:
- Creating variations (different teams/projects)
- Archiving before major edits
- Testing changes without affecting live doc
Export Article
- Open article
- Click ⋯ → Export
- File downloads (preserves formatting)
- Use cases:
- Offline backup
- Share with external partners (no Odoo access)
- Compliance/archiving
Enable Full Width Mode
- Open article
- Click ⋯ → Full Width
- Article expands edge-to-edge (no margins)
- Better for:
- Wide tables
- Large images/diagrams
- Code blocks
Real-World Impact Examples
Example 1: Tech Company (67 Employees)
Before Odoo Knowledge:
- Google Drive (847 docs), Confluence (23 spaces), Notion (14 workspaces)
- Search time: 4.7 hours/week per person average
- New hire ramp-up: 6 weeks to find everything
- Support team: Answering same 40 questions monthly
- Senior dev quit, took all tribal knowledge (disaster)
- Annual tool costs: Drive ($840) + Confluence ($12,600) + Notion ($10,000) = $23,440
After Implementing Knowledge Module:
- Centralized 847 docs to Odoo Knowledge (3-week migration)
- Created hierarchy: Engineering, Sales, Operations, HR (each with child articles)
- Built 12 templates (meeting notes, SOPs, project briefs, etc.)
- Search time: 15 minutes/week (96% reduction!)
- New hire ramp-up: 2.5 weeks (58% faster)
- Support FAQ article: Reduced repeat questions 87%
- Canceled external tools: $23,440/year saved
Financial Impact:
- Time saved: (4.7 - 0.25 hrs) × 67 people × 52 weeks × $67/hr = $413,687/year
- Tool subscriptions saved: $23,440/year
- New hire productivity gain: 3.5 weeks × 12 hires × $5,200/week = $218,400
- Support efficiency: 87% reduction × $87,360 cost = $76,003 saved
- Total annual impact: $731,530
- Migration cost: 3 weeks × 2 people × $67/hr × 40hr = $16,080
- ROI: 4,450%
Example 2: Manufacturing Company
Challenge:
47 SOPs (Standard Operating Procedures) stored in SharePoint. Last updated: 2019. Nobody maintains. New machine operators don't know where to find procedures. Safety incident: Operator didn't follow SOP (didn't know it existed). OSHA citation: $14,000 fine.
Solution: Odoo Knowledge SOPs
- Created "Safety & Operations" workspace in Knowledge
- Migrated all 47 SOPs, organized by department/machine
- Added cover images (photos of actual machines)
- Created SOP template: Purpose, Safety, Procedure, Troubleshooting
- Set access: Read-only for operators, Edit for supervisors
- Added properties: Last Reviewed, Next Review Date, Responsible
- Monthly review cycle: Supervisors update SOPs, version history tracks
Results:
- SOP compliance: 23% → 94% (operators now find/follow procedures)
- Safety incidents: 8/year → 1/year
- OSHA violations: Zero (24 months since implementation)
- Training time: New operators certified 40% faster (better documentation)
- Estimated OSHA fine prevention: $14,000/year
Best Practices
- Start with High-Value Content
- Don't migrate everything day 1
- Start with most-used docs: Onboarding, FAQs, SOPs
- Prove value, then expand
- Create Clear Hierarchy
- Top level: Department or function (Engineering, Sales, HR)
- Second level: Category (SOPs, Guides, Meeting Notes)
- Third level: Specific articles
- Use Templates Religiously
- Create template for every recurring doc type
- Enforces consistency
- Saves 80% creation time
- Set Review Schedules
- Add property: "Next Review Date"
- Assign owner to each critical article
- Quarterly review: Update or archive outdated docs
- Lock Finalized Content
- Lock official SOPs, compliance docs, published guidelines
- Prevents accidental edits
- Unlock only for official updates
Pro Tip: Link Knowledge articles to Odoo records. Writing SOP for handling refunds? Link it to Sales → Configuration → Settings. Creating project template? Link to Projects module. Client onboarding checklist? Link to CRM. Makes documentation contextual—appears exactly where people need it.
Wasting $772K Annually Searching Scattered Docs?
We migrate your Google Drive, Confluence, Notion chaos to Odoo 18 Knowledge. Build hierarchical structure, create templates, set access controls, train team. Save 4.7 hours/week per person.
