Google Drive Permissions Explained for Team Wikis
Roles, general access and inheritance: how Google Drive permissions work, and a folder-level setup that keeps a team wiki both open and safe.

Google Drive permissions come down to three things: who has a role on a file or folder (viewer, commenter, editor), who else can open it through general access (only invited people, your whole company, or anyone with the link), and how access flows down from folders to everything inside them. Get these right at the folder level and a team wiki in Drive stays both open and safe. Get them wrong one file at a time and nobody knows who can see what.
The building blocks
Roles. Each person or group gets a role on a file or folder:
| Role | Can |
|---|---|
| Viewer | Open and read |
| Commenter | Read and add comments or suggestions |
| Editor | Change content and, depending on settings, share it |
| Owner (My Drive) | Everything, including deleting and transferring ownership |
In shared drives, membership roles replace ownership: managers, content managers, contributors, commenters and viewers apply to the whole drive. More in shared drives vs My Drive.
General access. On top of named people, a file can be open to everyone at your company or to anyone with the link. This is where most accidental oversharing happens.
Inheritance. Files inherit access from the folder they're in. Give a group view access to a folder, and every doc you add later is visible to them too. That's what makes folder-level permissions the right default for a wiki.
Groups. Share with Google Groups (such as everyone@ or engineering@) rather than individual people. When someone joins or leaves a group, their access follows automatically.
A permission setup for a team wiki
| Area | Who gets access | Role |
|---|---|---|
| Company-wide knowledge | Everyone at the company (a company-wide group) | Viewer, or Commenter so people can flag outdated pages |
| Each section | The section owner and a few contributors | Editor |
| Team spaces | The team, plus the company as viewers unless there's a reason not to | Editor for the team, Viewer for the rest |
| Restricted areas (finance, HR cases) | Only the people involved | Editor or Viewer, never company-wide |
| Client or partner areas | That client's people only | Viewer or Commenter |
| Customer help center | Public, read-only | Anyone with the link, Viewer |
Three rules keep it manageable:
- Set access on folders, not files. Exceptions on single files are invisible until something goes wrong.
- Keep restricted content in its own folder. Never mix confidential and company-wide docs in one folder.
- Review once a quarter. Check general access on top-level folders and remove people who no longer need access.
How a wiki tool should handle Drive permissions
If you put a wiki layer on top of Drive, its permissions should never quietly differ from Drive's. Otherwise someone sees a page in the wiki they couldn't open in Drive, or the other way round. Ask three questions before you connect one:
- Does it bypass Drive permissions or follow them?
- How much of my Drive can it see? Only the folders you connect, or every file? More on why a Drive wiki tool shouldn't need access to all your files.
- Can it share with people outside the company, and is that visible?
Here's how Spaceli answers them:
- Access is kept in line with Drive. Space access is reflected on the space's Drive folder, so the wiki and Drive agree.
- Minimal Google access. Spaceli only works with the folders you connect and the files you create or choose, and can't see the rest of your Drive.
- Roles carried over. When you connect a folder, Spaceli offers to invite everyone who already has access, with editors as Editors and commenters and viewers as Viewers.
- Clear sharing levels. Organization-wide (can view or can edit), invited members, external collaborators invited to specific spaces only, and public spaces by link.
- Tied to your Google domain. Colleagues on your domain can join automatically, or request access for an admin to approve.
FAQ
Do files inherit folder permissions in Google Drive?
Yes. Files and subfolders inherit the access of the folder they're in, and can have extra access added on top.
What's the safest general access setting for a company wiki?
Restricted to your company domain, so only people signed in with a company account can open it. Use public links only for content meant for customers.
Can I give contractors access to part of the wiki?
Yes. Share only the folders they need, ideally through a group you can remove them from when the work ends.

Writes about wikis, documentation and how teams keep their knowledge easy to find.
Keep reading
All articles →How to Create a Wiki in Google Docs (Step by Step + Free Template)
Build a team wiki in Google Docs step by step: folder structure, home page, headings, links and permissions. Free template plus a faster way to do it.
How to Build a Public Help Center from Google Docs
Turn a Google Drive folder into a public help center customers can read without signing in. Plan it, write it in Google Docs and keep it current.
Google Drive Folder Structure for Teams: A Template That Scales
A Google Drive folder structure that scales: five rules plus copy-ready templates for startups, agencies and engineering teams.
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.