Guides

How to Build a Company Knowledge Base in Google Drive

What goes in, how to organize it, who owns each part and how people find it: the four decisions behind a knowledge base your team actually uses.

Eric Dunaway
Eric Dunaway
Spaceli
8 min read

A company knowledge base in Google Drive comes down to four decisions: what goes in, how it's organized, who owns each part and how people find it. Get those right and Drive, which your team already uses, can hold everything from the employee handbook to engineering runbooks to a help center for customers. This guide covers each decision, gives you a structure to start from, and lists the mistakes that quietly kill most knowledge bases.

Why build it in Drive at all? Because that's where your documents already are. People write in Google Docs every day, access is managed by your Google Workspace admin, and nobody has to learn a new editor or migrate years of content. The hard part isn't storing knowledge. It's turning a shared drive into a place where anyone can find an answer in a minute.

What belongs in a company knowledge base

A knowledge base holds the answers people would otherwise ask a colleague for. Most companies need six kinds of content, each with an obvious owner.

What goes in a company knowledge base and who owns it
ContentTypical pagesOwner
Company basicsMission and values, who's who, holidays, office and remote setupPeople or HR
OnboardingFirst-day checklist, first 30 days, tools and accountsPeople or HR, with each team lead
PoliciesExpenses, travel, security, time off, code of conductPeople, Finance, IT
How we workMeeting rules, planning process, decision log, writing guidelinesLeadership or operations
Team knowledgeEngineering runbooks, product specs, sales playbooks, support macrosEach team
Customer-facing docsGetting started, how-tos, billing questions, troubleshootingSupport or product

Customer-facing docs are often kept apart from the rest. They don't have to be: write them in the same Drive, keep them in their own folder and share that one part publicly. Here's how to build a public help center from Google Docs.

What doesn't belong: drafts in progress, meeting notes nobody will reread, and files that only make sense to their author. They belong in Drive, just not in the knowledge base.

How to build it, step by step

1. Decide who it's for

Write down the audiences before you create a single folder: the whole company, specific teams, new hires, contractors, customers. Each audience needs different access, so it usually gets its own top-level area. Mixing internal and public content in one folder is how confidential pages end up shared by accident.

2. Create shared drives, not personal folders

Use a shared drive for each area so files belong to the company, not to whoever created them. A common setup is one shared drive for company-wide knowledge, one per large team and one for customer docs. Smaller companies can start with a single shared drive and one folder per area. If you're starting with a team wiki, our guide to creating a wiki in Google Docs walks through the same setup.

3. Start from the questions people actually ask

Don't start by writing everything. Collect the 20 to 30 questions new hires and colleagues ask most often, from chat history, onboarding notes and support tickets. Each question becomes a page. That first set covers most of what people look for, and it shows the team the knowledge base is useful from day one.

4. Make a template for each page type

Give policies, how-tos and runbooks a fixed shape: a one-line summary, the owner, the last review date, then the content. Store the templates in a "Templates" folder. Pages that look alike are faster to read and easier to keep up to date. For step-by-step procedures, start from our SOP template for Google Docs.

5. Assign an owner to every area

Every top-level folder needs a named person who answers for it. They review their pages on a schedule, every quarter for most content and right away when a process changes. A knowledge base without owners decays within months.

6. Set permissions by area

Give the whole company view access to company-wide content and edit access to the owners. Keep team spaces open to the company unless there's a reason not to; hidden knowledge gets duplicated. Share customer docs publicly only from their own folder, and invite contractors to just the areas they need. Here's a permission setup for a team wiki you can copy.

7. Launch it where people already work

Announce it with the first set of pages, link it from the onboarding checklist and pin it in your main chat channels. The habit that makes it stick: when someone asks a question that's already answered, reply with a link to the page instead of retyping the answer.

8. Keep it alive

Once a quarter, ask each owner to review their pages, archive what's outdated and add the questions that came up since. Track the questions people still ask in chat: each one is either a missing page or a page nobody can find. Here's a 30-minute quarterly review to run.

Three ways to structure it

There's no single right structure, but there is a right one for your size. Pick one main axis for the top level and stick to it.

Three ways to structure a company knowledge base
StructureTop-level foldersWorks best forWatch out for
By topicCompany, Onboarding, Policies, How we workTeams under 50 peopleTeam knowledge gets squeezed into generic folders
By teamPeople, Engineering, Product, Sales, SupportCompanies with clear departmentsCompany-wide answers get scattered across teams
By audienceEveryone, Engineering, Leadership, CustomersCompanies with internal and public docsOverlap between audiences needs links, not copies

Most companies end up with a mix: topics for company-wide knowledge, a folder per team for team knowledge, and a separate area for customers. That's fine, as long as each piece of content has exactly one home.

Keep every tree two or three levels deep. If a page sits five folders down, nobody will browse to it. For ready-made layouts, see our Google Drive folder structure templates.

Mistakes that kill a knowledge base

  • Writing everything before launch. Months of preparation produce a big, outdated knowledge base nobody asked for. Launch with the top questions and grow from there.
  • Copies instead of links. The same policy in three folders means three versions, and two of them are wrong. Keep one page and link to it.
  • No owners. "Everyone maintains it" means nobody does.
  • Personal folders. Knowledge kept in someone's My Drive leaves with them.
  • Hard to find. If people have to search all of Drive and guess which file is current, they'll ask in chat instead. More on why nobody can find anything in Google Drive.
  • Looks like a pile of files. A folder list with no navigation, no table of contents and inconsistent formatting feels unfinished, and people stop trusting it.

The last two are the hardest to fix with Google Drive alone. Drive is built for storing files, not for browsing and reading them as one knowledge base.

Turn your Drive into a real knowledge base with Spaceli

Spaceli adds the missing layer on top of Google Drive: navigation, search and a clean reading experience. Your docs stay in Drive, you can edit right inside Spaceli, and every change syncs both ways.

One space per area. Each space is built from one Drive folder, existing or new, shared drives included. Create as many as you need: a company handbook, an engineering wiki, an onboarding space and a help center for customers. Admins pick a default space, so everyone in the company lands on the right one.

Built-in navigation. Folders become a sidebar you can reorder with drag and drop, without touching Drive. Every doc gets a table of contents that highlights where you are, and every heading gets its own shareable link. Pin up to three quick links in the space header, like your roadmap or team calendar.

Search that finds answers. Press Cmd+K to search one space: titles show up instantly, then matches in the full text of your docs, grouped into pages, folders and quick links.

Pages that look finished. Every doc gets the same clean typography, in light and dark mode and in one of five color themes. Write callouts (Note, Tip, Warning, Danger, Success) and code blocks with syntax highlighting right in Google Docs.

All your knowledge, not just Docs. Sheets, Slides, Forms, PDFs and videos open inside the space. Figma designs, Miro boards, Loom videos and other embeds sit next to your docs.

Access that matches Drive. Colleagues on your company domain can join automatically or request access. When you connect a folder, Spaceli offers to invite everyone who already has access to it, with their roles carried over. Invite contractors and clients to specific spaces only, or make a space public so customers can read it without an account.

Your data stays yours. Spaceli only works with the folders you connect and the files you create or choose. It keeps no permanent copies of your documents. Stop using it, and everything is still in your Drive.

FAQ

Can Google Drive be used as a knowledge base?

Yes. With shared drives, a clear folder structure, page templates and named owners, Google Drive can hold a company's knowledge. What it lacks is navigation, focused search and a reading view, which a tool like Spaceli adds on top. Our guide to creating a wiki in Google Docs covers the same setup for a team wiki.

Should we use one shared drive or several?

Start with one if you're a small team. Split into several when areas need different access: for example, company-wide knowledge, team spaces and customer docs.

How do we keep the knowledge base up to date?

Give every area an owner, review pages once a quarter and archive what's outdated instead of deleting it. When people keep asking the same question in chat, that's a page to write or a page to make easier to find.

Can one knowledge base serve both employees and customers?

Yes, as long as they're separate areas. In Spaceli, that means separate spaces: internal ones for your team and a public one for customers, all written in the same Google Drive.

What's the difference between a knowledge base and a wiki?

They overlap. A wiki usually means pages that the whole team edits and links together. A knowledge base is the broader collection of answers, policies and guides, sometimes including docs for customers. In Google Drive, you build both the same way. More in knowledge base vs wiki vs intranet.

Eric Dunaway
Written by Eric Dunaway

Writes about wikis, documentation and how teams keep their knowledge easy to find.

Share

Your knowledge base is already in Google Drive.

Give your team a better way to organize, find, and share knowledge. Keep your documents right where they are.

Start for Free

Free during the beta. Get started in about a minute.

Spaceli only accesses the folders you choose.