Internal Wiki and Public Docs from One Google Drive
Keep your internal wiki and your customer docs in one Google Drive: how to split folders and access, and publish both without a second tool.

You don't need one tool for your internal wiki and another for customer-facing docs. If your team already writes in Google Docs, keep both in Google Drive: one folder for internal knowledge, another for public docs, each with its own access. The writing stays in one place, and only the public folder is open to customers.
Why teams end up with two tools
It usually happens by accident. The team writes internal docs in Google Docs. Then customers need a help center, so someone signs up for a help desk tool with its own editor. A year later:
- The same knowledge lives twice. The internal setup guide and the customer setup guide drift apart.
- Writers switch editors. Support writes drafts in Google Docs, then pastes them into the help desk and fixes the formatting.
- Two bills, two logins, two places to search.
- Fewer people contribute. Engineers and product managers comment in Google Docs, but rarely log in to a help desk editor.
For most small and mid-size teams, the second tool solves a publishing problem, not a writing problem.
How to split internal and public content in Drive
The rule is simple: public content gets its own top-level folder, never a subfolder of the internal wiki. Drive permissions flow down from folders, so a separate tree is the only safe way to keep the two apart. More on that in Google Drive permissions explained.
Knowledge (shared drive)
├── Company wiki → your company, internal
│ ├── Handbook
│ ├── Processes
│ └── Support playbooks
└── Help center → public, read-only
├── Getting started
├── Billing
└── Troubleshooting| Internal wiki | Public docs | |
|---|---|---|
| Readers | Your team | Customers, prospects, partners |
| Access | Company domain only | Anyone with the link |
| Tone | Candid, internal names allowed | Customer language, no internal details |
| Review | Owner updates as needed | Second pair of eyes before publishing |
Two habits keep it safe. Draft public articles in the internal wiki and move them into the public folder once reviewed. And never link from a public article to an internal doc; customers can't open it anyway.
Running both from Drive with Spaceli
Spaceli turns each Drive folder into a space, so the setup above becomes two spaces in one workspace:
- Internal space. Your company wiki, open to everyone on your Google domain, with sidebar, Cmd+K search and a table of contents on every page.
- Public space. Your help center, readable by anyone with the link, with no account needed.
- One writing tool. Everyone writes in Google Docs, or right inside Spaceli, and changes sync with Drive both ways.
- Separate looks. Give each space its own color theme, so readers always know where they are.
- External collaborators. Invite a partner or agency to a specific space without opening anything else.
- Hide drafts. Hide a page from the space while it's in review, without touching the file in Drive.
Public spaces aren't indexed by search engines today, so link to them from your product, site and emails. Custom domains such as help.yourcompany.com are coming soon. For the public side step by step, see how to build a public help center from Google Docs.
FAQ
Is it safe to keep public and internal docs in the same shared drive?
Yes, as long as they're in separate top-level folders and only the public folder is shared by link. Check general access on both folders once a quarter.
Can one article be both internal and public?
Keep one version in the public folder and link to it from the internal wiki. Internal-only notes go in a separate internal doc.
When do we need a dedicated help desk tool?
When you need ticketing, a chat widget or detailed article analytics tied to support. For publishing readable docs, Google Docs and a wiki layer are enough.

Writes about wikis, documentation and how teams keep their knowledge easy to find.
Keep reading
All articles →Engineering Documentation in Google Docs: Runbooks, ADRs and Onboarding
A folder structure and templates for runbooks and architecture decision records in Google Docs, plus how to make Docs work for engineers.
How to Keep Designs, Boards and Docs in One Place
Figma, Miro, Loom, Sheets and Docs scattered across tools? Organize by topic in Google Drive and bring them into one knowledge base.
Internal Wiki for Remote Teams: What to Document First
The first ten pages every remote team wiki needs, how to write for async readers, and how to set it up in Google Drive.
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 FreeFree during the beta. Get started in about a minute.
Spaceli only accesses the folders you choose.