How CGS built a company wiki that field, sales, and admin teams use everyday
CGS had valuable company knowledge, but it was spread across scattered documents and people’s heads. Field techs, sales, and admin each needed different information, and there was no easy way to find the right answer quickly. I built a structured Notion knowledge base with role-based portals, clear navigation, and permissions designed around how each team works.
CGS
·
Commercial Systems Integration
·
Knowledge Base & Wiki
·
Under 4 weeks
Notion
Slack
Published
·
updated
THE PROBLEM
The company did not lack knowledge. It lacked a usable home for that knowledge. Field technicians needed quick access to practical information. Sales needed a reliable place for client-facing knowledge. Support and admin needed internal processes organized clearly. Without a shared structure, answers were easy to lose and hard to trust. CGS needed a wiki that people would use everyday, not another folder system that slowly becomes outdated.
THE SOLUTION
I designed a Notion knowledge base as the company’s single source of truth. The workspace includes a clear hierarchy, intuitive navigation, and three dedicated portals: field tech, sales, and support/admin. Each portal surfaces the information that role needs most, while permissions make sure people see the right content without clutter. The design was also intentionally inviting, because adoption depends on more than structure. The system had to feel easy to enter and simple to maintain.
THE PROCESS
We agreed on the structure and hierarchy first, then built the workspace portal by portal. I created templates, permissions, navigation, and links to core tools. The process focused on making the wiki practical for daily use, not just organized on paper.
THE RESULT
CGS now has one company-wide knowledge base serving three teams. In two weeks, scattered know-how became a structured AI-powered Notion wiki. The team now has a central place to document processes, find answers, and reduce dependency on individual memory.
