Google Workspace Third-Party App Access: Reviewing Connected Apps

A hospice office manager tries a free scheduling tool one afternoon. It asks to "Sign in with Google," shows a list of things it wants to see, and she clicks Allow. The tool works nicely. Six months later she has forgotten about it, but it still has permission to read her calendar and her Drive. The company that makes it has since been sold twice.

Outside apps connected to Google accounts are one of the quieter ways data leaves an organization. This article shows how to see them and how to set limits.

How apps get access

When someone uses "Sign in with Google" or approves an add-on, they grant the app permissions called scopes, such as viewing contacts, reading email or managing files. The app receives a token that continues to work until it is revoked. Changing a password does not necessarily cancel it.

Most apps are honest. But even an honest one can be sold, breached or poorly written, and a dishonest one can be built to look helpful. Staff who handle client or patient information in Drive and Gmail should not be the only line of defense against that decision.

Seeing what is already connected

In the Google Workspace admin console, the security area includes API controls, where an administrator can view apps that users have connected, how many users have connected each one, and what access they received. Names and menu paths change over time, so ask your administrator or IT provider to find the current location.

When reviewing, look for:

Apps nobody recognizes.

Apps connected by only one user, particularly with broad access to mail or Drive.

Apps with permissions that seem out of proportion to what they do, like a calendar tool asking to read all email.

Old trials, browser extensions and tools from former employees.

Apps with the word "mail" or "drive" in the permissions, since those carry the most risk.

What you can do about them

Google lets administrators set the trust status of apps. Generally you can mark apps as trusted, limit what they can do, or block them. You can also control what kinds of access users are allowed to grant on their own, such as allowing only low-risk permissions and requiring approval for access to Gmail or Drive.

A practical posture for care organizations:

Block or remove apps nobody can justify.

Mark a short list of approved tools as trusted.

Restrict access to the sensitive services (mail and files) so that only approved apps can use it.

Require users to ask before connecting anything new.

Questions to ask IT

Can we see a list of all apps connected to our Google accounts and the permissions they hold?

Which of them are unfamiliar, and what is the plan for each?

What is our current setting for new apps? Can any user approve any app?

Can we restrict access to Gmail and Drive to approved apps only?

Who reviews requests when staff want a new tool, and how quickly?

If we remove an app, what will break, and who needs to be told first?

The last question matters. Someone may depend on a tool without telling anyone. Ask department heads before cutting anything that has many users.

Setting up a request path

Restrictions only work if staff can get what they need. If the answer to every request is "no" or "wait three weeks," people will find workarounds, perhaps with personal accounts. Agree on a simple form or email address, a named person who reviews it, and a target for responding. Keep an approved list that staff can see.

Include a few questions in each review: what does the app do, what data does it touch, does it keep a copy, who is the vendor, and is there a written agreement if protected health information is involved? That last point is a matter for your compliance advisor or counsel, not just IT.

Repeat it

Check connected apps a couple of times a year, and whenever someone leaves. Revoke their connected apps and tokens as part of offboarding, along with suspending the account.

Finally, do not forget browser extensions and add-ons that staff install on their own. They can request similar access, so ask IT whether those can be managed too, and whether staff need approval before adding one on a work computer.

How we can help

UnityCare IT reviews the apps connected to your Google Workspace accounts, removes the ones that should not be there, and sets rules so new ones need approval. We can also run the request process for your staff so approvals are quick and consistent.

Related service

Security monitoring, HIPAA safeguards, backups and staff training for healthcare and small businesses.

Related articles

Keep reading

Contact UnityCare Technologies

Call or text: 405-285-3845

New customers: start@unitycareit.com

Existing customers: support@unitycareit.com

Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas

Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support