Why Your Drive Wiki Tool Shouldn't Need Access to All Your Files
Drive apps can ask for one file or your whole Drive. How Google's Drive scopes work, why narrow access is safer, and a checklist to use before you approve one.

A wiki built on Google Drive only needs the folders you turn into a wiki. Yet some Drive apps ask for permission to see, edit, create and delete every file in a user's Drive: contracts, HR files, financial models, everything. For an IT admin approving apps, the scope an app requests matters as much as what it does.
This article explains how Google's Drive access scopes work, why narrow access is safer, and a short checklist to use before you approve any Drive app. We make Spaceli, which uses the narrowest file scope, so we've linked the sources for how scopes are classified.
How Google Drive access scopes work
When an app connects to Google Drive, it asks for one or more OAuth scopes. The consent screen turns them into plain sentences, and those sentences tell you how far the app can reach.
| What the consent screen says | Scope | What the app can reach |
|---|---|---|
| See, edit, create and delete only the specific Google Drive files you use with this app | drive.file | Only files you create with the app or explicitly open or pick with it |
| See and download all your Google Drive files | drive.readonly | Every file in your Drive, read-only |
| See, edit, create and delete all of your Google Drive files | drive | Every file in your Drive, with full control |
Google treats the broad Drive scopes as restricted. Apps that request restricted scopes must pass a security assessment, renewed every year, while apps using only non-sensitive scopes such as drive.file don't need one (Google Workspace Marketplace Help, Nango). The assessment is a useful safeguard, but it checks the vendor's security, not whether the app needs that much access in the first place.
Why narrow access matters
- Smaller blast radius. If an app with full Drive access is ever compromised, every file of every user who connected it is exposed. With file-level access, only the wiki's files are.
- Least privilege. A wiki needs the wiki's folders. Granting more than that breaks the basic rule security teams apply everywhere else.
- Easier approval. Narrow scopes are faster to review and easier to explain to your security team and auditors.
- Clearer for users. People are more willing to connect an app when the consent screen asks for specific files, not their whole Drive.
- No accidental indexing. An app with full access may read or cache files nobody meant to put in the wiki, such as personal or confidential documents.
Scopes are one layer; the file and folder permissions inside Drive are the other. Here's how Google Drive permissions work for a team wiki.
A checklist before you approve a Drive app
- Which scopes does it request? Read the consent screen or the Marketplace listing's permissions section.
- Does it need every file, or only the ones you choose?
- Does it keep copies of your documents? For how long, and who can access them?
- Does it follow Drive permissions, or can it show files to people who couldn't open them in Drive?
- Can it share content outside your domain, and can you see when it does?
- What happens to your content if you stop using it?
How Spaceli answers it
Spaceli requests only drive.file, plus your email address and basic profile to sign you in.
- Only what you connect. Spaceli works with the folders you connect and the files you create or choose, and can't see the rest of your Drive.
- No permanent copies. A temporary, access-controlled text cache of up to 30 days keeps pages fast.
- Permissions kept in line. Space access is reflected on the space's Drive folder.
- Visible sharing. External collaborators are invited to specific spaces, and public spaces are opened on purpose, by link.
- Analytics only with consent.
- No lock-in. Your docs stay regular Google Docs in your Drive.
FAQ
What is the drive.file scope?
It lets an app access only the Drive files a user creates with it or explicitly opens or picks with it. The app can't list or read anything else in the user's Drive.
Can admins restrict which Drive apps users connect?
Yes. Google Workspace admins can control which third-party apps can access Workspace data and review the scopes each one uses.
Does narrow access limit what a wiki can do?
Not for a wiki. A wiki only needs the folders it shows. Spaceli builds its sidebar, search and pages entirely from the folders you connect.
Sources
Checked July 21, 2026.

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.