On this page
How can I check which third party apps access Google Workspace?
Look at the connected apps in your own Google account. For the whole organisation, use the app access controls in the Workspace admin console. For each app, check what it can reach, who allowed it and why you still need it.
Review shared files as a separate job. An app’s permission and a sharing link are two different routes to your data.
What does OAuth mean?
What OAuth means.
OAuth is how you let an app into your Google account without giving it your password. You click Allow, and the app receives a permission with a set scope, for example the files you pick, or everything in Drive.
That permission can stay in place after you stop using the app. That is why a review looks at the permission, not only at the apps you still open.
What is the admin console?
What the Workspace admin console is.
The settings area where a Google Workspace administrator manages the users, apps and security settings of the whole organisation.
Which app controls you see there depends on your Workspace edition and on your admin role.
A free trial can leave a connection behind.
A designer tries a PDF tool. A founder connects a meeting assistant. A growth consultant gives an automation access to a spreadsheet. Each choice made sense at the time. Months later the subscriptions and projects have changed, and nobody can say for sure which apps can still reach company information.
Start with the accounts used for client work and the services connected to them. Ask each person which tools they still rely on. Do this before you block apps you do not recognise, because an unfamiliar name might run a real part of how you deliver to clients. You want the forgotten access gone and the necessary work still running.
Read the permission, not only the app name.
Google describes what a connected app can do with permission scopes. In plain words: can it read files, change them, send email or reach other information? The exact scope matters. Access to a few files you picked is very different from access to all of Drive, and a familiar supplier name does not tell you which of the two an app has.
Write one sentence for each connection: “This app needs this access because it does this job.” If nobody can finish the sentence, look closer. Note the person responsible, the connected account and the date you reviewed it. Do not treat every connection as suspicious. The real problem is access nobody understands, or has a current reason to keep.
Provider guidance: Google: control app access to Workspace data
one sentence per app26.09.2026
| App | What it can reach | Why it stays |
|---|---|---|
| PDF toolconnected by Ana during a free trial | Every file in Drive, to read and to change | Nobody can finish the sentence. Ask Ana, then remove it. |
| Meeting assistantconnected by Luca | Calendar events and meeting notes | It writes up client calls. Keep it. |
| Reporting automationconnected by Mira | One spreadsheet | It sends the weekly campaign report. Keep it. |
Check file sharing as a separate job.
Removing an app’s access does not change the other ways a file is shared. A folder might still include a former contractor. A document might have a sharing link that anyone can open. A client file might belong to one person instead of the organisation. Review these next to the app list, and keep the two apart.
Say a freelancer who has left used a reporting app and was also added straight to a campaign folder. Review the app’s permission and the folder membership separately. If a tool already copied information, removing its future access does not pull those copies back. When that matters for the project, check the provider’s deletion process.
one folder, two ways in26.09.2026
app access
Which tools have account permission?
- The freelancer’s reporting appreads the whole folder
- Meeting assistantreads the calendar only
file sharing
Which people and links reach the files?
- The former freelancercan edit the folder
- Anyone with the linkcan view one document
Removing the reporting app leaves the freelancer and the link in place. Keep only what current work needs, on both sides.
Removing access today does not pull back what was copied yesterday.
Make the change, then check the result.
Ask the owner whether the connection is still needed. If it is, reduce its access where the provider allows it, and test the real workflow. If it is not, remove it through the account or admin controls. Follow Google’s current instructions for your edition.
Keep a dated note of what changed and why. After a removal, check that the connection is really gone and that the important work still runs. Look again at a client handover or when a colleague leaves. A small review you repeat is easier to keep up than a big audit that happens once.
Provider guidance: Google: sharing account access with third party apps
Give the team one way in, with a second lock.
Every app with its own password is one more door to lose track of. Single sign on means people reach many apps with one set of login details. Google Workspace can do that in two ways: apps that offer a sign in with Google button, or an outside identity provider connected through the standard Google supports for it, SAML or OIDC. For a team of five, the first is usually enough. It gives you one account to switch off when someone leaves.
The second lock is a second step at sign in, called multi factor authentication in general and 2 Step Verification by Google. A stolen password then is not enough. In the admin console, a super administrator opens Security, then Authentication, then 2 step verification. You can enforce it at once or from a date you choose, and give new people a sign up window, from one day to six months, in which a password alone still works. You also choose which methods count. Security keys and passkeys resist fake sign in pages best, and you can require only those. If you exclude codes sent by text or call, move people who rely on them to another method first, or they are locked out.
Single sign on, MFA, 2 Step Verification. Which is which?
Three names, two ideas.
Single sign on is about the front door: one account opens many apps. Multi factor authentication is about the lock on that door: a second proof beyond the password, such as a security key or a code. Google’s name for it is 2 Step Verification.
They work together. One account with a second step is easier to protect than ten accounts with ten passwords.
Give each person only the access the job needs.
The same idea that applies to apps applies to people. Google offers prebuilt administrator roles, such as User Management for creating accounts and Help Desk for resetting passwords, so the person who handles accounts does not need the keys to everything. The Super Admin role reaches every feature in the console. When no prebuilt role fits, a super administrator can build a custom one.
Google’s own advice for the super administrator accounts is short. Have more than one, held by different people, so a lost account does not lock you out. Give each of those people a separate account for everyday work, so the powerful one is not used to read email. Require 2 Step Verification on them, with security keys where you can. Sign in as a super administrator only for the task that needs it, then sign out.
For ordinary files, put client work in a shared drive where the team is a member, rather than in one person’s My Drive. Google notes that moving files to a shared drive keeps them from being deleted when the owner’s account goes.
Use a short list when someone joins, moves or leaves.
Most forgotten access starts with a change of people. Say Mira moves from reporting to client delivery. Her new folders arrive on day one, and nobody removes the old ones, so a year later she can open everything. A person who leaves is the sharper case, because the apps they connected stay behind, and so do the files and links they shared. Run the same few steps each time.
when people changedone by hand in the admin console
- joinerCreate the account with the role the job needs, no more.
- joinerAdd them to the groups and shared drives for their projects, not to single files.
- moverRemove the old role’s access before you add the new role’s.
- moverAsk which apps they connected for the old work and whether the new work needs them.
- leaverSuspend the account first, so nothing changes while you work.
- leaverTransfer the Drive files they own, and move shared client work into a shared drive.
- leaverReview the apps they connected and the files shared with them, and remove what work no longer needs.
- leaverDelete the account only after the transfers are done.
Suspending blocks access to your Google services and keeps the data. Deleting is permanent: data you did not transfer is removed, though Google keeps some of it for 20 days, and a deleted account can be restored within that window. If a transfer fails, the deletion stops and the account stays. If you want to keep a former colleague’s data, suspend or archive instead of deleting.
Google: delete or remove a user The same list for a freelancer who leaves
Where Cybee fits.
Google Workspace: Coming soon.
What to remember.
- Review app permissions and file sharing separately.
- Give every connection a purpose, an owner and a review date.
- Removing future access does not bring back what was already copied.
- One sign in with a second step, and only the admin role each job needs, shrink what a lost password can reach.
Sources and further reading.
Written by Cybee for small teams. Product scope and provider guidance can change, so check the linked source for your own setup.
- Google: control app access to Workspace data
- Google: sharing account access with third party apps
- Google Workspace Help: about single sign on
- Google Workspace Help: deploy 2 Step Verification
- Google Workspace Help: prebuilt administrator roles
- Google Workspace Help: security best practices for administrator accounts
- Google Workspace Help: delete or remove a user
When someone leaves, check what stays behind.
Cybee shows the Mac and the AI tools of someone who joins or leaves, and keeps a dated record.


