Choosing a Google Drive permissions checker for an in-house team
Your team shares files all year, and at some point someone asks, "Who can actually open the client folder?" A Google Drive permissions checker answers that question without you opening every file one by one. This guide covers what a good checker should do, compares three routes (the Share dialog, admin reports and a Chrome extension) and lists the questions to ask before you install anything. It is written for in-house teams who already know they need a check and want to pick a method with clear criteria.
In this guide
- What a Google Drive permissions checker should check
- Option 1: The Share dialog, file by file
- Option 2: Admin reports for Workspace admins
- Option 3: A Chrome extension that scans your Drive
- Comparison table: manual, admin report and extension
- Privacy questions to ask before installing a checker
- How Wistorix works as a permissions checker
- A review routine your team can keep
- Frequently asked questions
What a Google Drive permissions checker should actually check
A Google Drive permissions checker is only useful if it answers the questions your manager or an auditor will really ask. Three abilities separate a real checker from a list of file names.
Who has access, by person and by file
You need both views. By file: who can open this folder? By person: which files can this contractor still reach? Most manual ways to run a Google Drive permissions checker only give you the first view, and the second is the one you need when someone leaves or changes teams.
Public and external shares
Two kinds of sharing deserve a second look. The first is "Anyone with the link", which Google describes this way: "Anyone on the internet who has the link can open the file without signing in to a Google Account." The second is sharing with email addresses outside your company. A checker should flag both so you do not have to guess.
The ability to act, not only list
A report that you cannot act on creates a second task: someone has to go back into each file and fix it. Look for a Google Drive permissions checker that can revoke access or change a role (Viewer, Commenter, Editor) for many files at once, after you have reviewed the list.
Option 1: The Share dialog, file by file
This is the method everyone already has. It costs nothing and needs no install, which makes it a fair starting point for a small set of folders.
How to read the people list
Select a file or folder in Drive and click Share (see Google's guide to sharing files and folders). The dialog lists the people with access and their role. For the access list in the details panel, Google's help says: "In the details panel on the right, click Manage access." Read the list from top to bottom and note anything labeled "Anyone with the link" under General access.
Where it breaks down
The Share dialog works on one item at a time. For a handful of folders that is fine, but with hundreds of files it becomes a full day of clicking. It is also easy to miss a file that someone shared individually inside a folder that looks private.
It also cannot answer the by-person question. To find everything one contractor can reach, you would have to open every file and look. That is the point where most teams start looking for another route.
Option 2: Admin reports for Workspace admins
If your company uses Google Workspace and you hold admin rights, the Admin console may give you sharing or Drive activity reports. What you get depends on your Workspace edition, so check Google's Admin help for your plan before you build a process around it.
Who can use it
Admin reports need admin rights. If you are an editor on a team folder, or you work in an in-house role without access to the Admin console, this route is closed to you. In many companies the person who needs the check and the person who holds admin rights are not the same.
Reports still need action
Even with admin rights, a report tells you what exists. Someone still has to open each file and change the access, or ask the owner to do it. If your report shows 300 externally shared files, the report is the start of the work, not the end.
Option 3: A Chrome extension that scans your Drive
As a Google Drive permissions checker, a Chrome extension runs in your browser with your Google account. It scans the files you can see and builds a list you can filter, so you do not need admin rights to start.
What a scan should and should not read
A scan should read administrative information: file name, size, owner and sharing permissions. It should not need the content of your documents to tell you who can open them. If a tool says it must read content to check permissions, ask why.
Review before action
The safest design shows you the list first and changes nothing until you select items and confirm. After that, bulk revoke or bulk role change saves the hours you would spend in the Share dialog. A free scan with paid actions is common, so look at the vendor's pricing page instead of relying on a number quoted in an article.
Comparison table: manual, admin report and extension
Here are the three routes side by side, using the criteria from the first section.
| Route | Scope | By-person view | Public / external flags | Bulk fixes | Data read | Needs admin rights |
|---|---|---|---|---|---|---|
| Share dialog | One file or folder at a time | No | Manual check | No | What you open yourself | No |
| Admin reports | Workspace-wide, edition-dependent | Depends on the report | Depends on the report | Usually a separate step | Handled by Google | Yes |
| Chrome extension | Files your account can see | Yes, if the tool supports it | Yes, if the tool supports it | Yes, if the tool supports it | Depends on the tool; ask | No |
The table shows a pattern. The Share dialog is free and exact but does not scale. Admin reports scale but need rights many teams do not have. An extension fills the gap, as long as you check what it reads.
Privacy questions to ask before installing a checker
Any Google Drive permissions checker that connects to your Drive asks for access to company files, so treat it like a vendor review. Ask these three questions first.
Which Google permission does it request?
Look at the OAuth scope on the consent screen. Google describes the broad Drive scope as "View and manage all your Drive files." That wording is wide because Google defines scopes broadly, so the vendor's explanation of why it needs the scope matters.
Does it read names and sharing data, or file content?
Ask for a plain answer. A Google Drive permissions checker has no reason to open the text of your documents. It needs names, sizes, owners and sharing settings.
Where is data stored?
Read the privacy policy for what is kept, for how long and where. If you work in a company with a security team, send them the policy before you install. A short email to the vendor is also a fair test of how clearly they answer.
How Wistorix works as a permissions checker
What it scans and flags
Wistorix works as a Google Drive permissions checker: a Chrome extension with a web app that scans your Drive and lists files by sharing permission. You can also review by email, which shows the files one person currently has access to. It detects publicly shared files and files shared outside your organization so you can look at them first. It reads only admin metadata (name, size, owner, sharing permissions), not file content, and requests one Google permission, the Drive scope.
Acting on what you find
Revoking access or changing roles in bulk happens only after you review the list and choose the items yourself. Nothing is changed automatically. To see how this fits an in-house setup, read about the sharing risk scan and Wistorix for in-house teams. When you are ready, scan your Drive free at wistorix.com.
A review routine your team can keep
A one-off Google Drive permissions checker run helps, but permissions drift every time someone shares a link in Slack or email. A light routine keeps the result.
Pick a schedule and an owner
Choose a rhythm that matches how often your team shares files, such as monthly or quarterly. Name one person who owns the review and one place where the findings are recorded, such as a shared tracker. Without an owner, reviews slip after the second round.
Work in a fixed order
Start with what carries the most risk and move down. A simple order works well for most teams:
- First, public links ("Anyone with the link") on folders that hold client or finance files.
- Second, external email addresses, especially vendors whose project has ended.
- Third, former staff and anyone who changed teams.
For the deeper view on audits, see what a Google Drive audit tool is, and for choosing an add-on read about a Chrome extension for Google Drive. For the wider picture, the Google Drive management tool page covers the full toolset.
Frequently asked questions
What is a Google Drive permissions checker?
It is a method or tool that shows who can open which files in your Drive. A good one lists access by person and by file, flags public and external shares, and lets you fix them in bulk. Google's Share dialog is the manual version, and extensions automate the same job across many files.
Can I check Google Drive permissions without being an admin?
Yes. The Share dialog works for any file you can open, and you can see the access list in the details panel. A Chrome extension can scan the files your own account can see, so admin rights are not required to start. Admin reports are the route that does need them.
Does a permissions checker read my file contents?
It should not need to. To list who can open a file, a tool only needs the file name, size, owner and sharing settings. Ask each vendor directly and read the privacy policy. Wistorix reads that administrative information only, not file content.
Can Wistorix show who edited a file?
No. Wistorix shows who currently has access, not who viewed or edited a file. For edit history, use Google's own Activity and Version history features inside Drive.
sharing publicly?