AegisAI Perspectives · 158

How to control which third-party apps can access Google Workspace mail: admin steps

Admin steps for Google Workspace that show where API controls live, what the four access levels mean and how to restrict Gmail access.

TL;DR
Answer
For third-party apps, set each app's access level (Trusted, Limited, Specific Google data or Blocked) in the Google Workspace Admin console under API controls, then restrict Gmail.
Who it's for
If you run IT for a small business of 20 to 500 people on Google Workspace, with a small IT or security team and no SOC.
Watch out for
Setting Gmail to Restricted stops untrusted apps that were already installed and revokes their tokens, so set the apps you keep first.
What AegisAI does
AegisAI's AI agents start read-only: a pilot can list users and read mail for classification, nothing more, and removal needs write access your admin grants and can revoke.
Book a demo

See it on your own Google Workspace or Microsoft 365 tenant. No MX change.

Or get the Q3 2026 State of the AI Attack report (free, instant download)

Not ready for a demo? Check your domain.

How to control which third-party apps can access Google Workspace mail: admin steps

It is safer when you set the access level yourself: Specific Google data holds an app to the scopes you specify5. Set each app's access level in the Google Workspace Admin console at Menu > Security > Access and data control > API controls1. AegisAI works post-delivery through the Microsoft 365 or Google Workspace API20. That makes API controls the place where any mail tool, including a security tool, gets its access set and taken away.

If you run IT for a business of 20 to 500 people on Google Workspace, with a small IT or security team and no SOC, these steps decide which apps can read Gmail. How the product reads mail after delivery is on the inbound email security page. Whether to grant API access at all is answered in is it safe to give an email security vendor API access to our mailboxes.

Key takeaways

  • Each procedure on Google's page needs the Service Settings administrator privilege2.
  • The four access levels are Trusted, Limited, Specific Google data and Blocked346.
  • Google lists nine Gmail high-risk OAuth scopes that an admin can restrict9.
  • For unconfigured third-party apps, the default is Allow users to access any third-party apps10.
  • Scope-based configuration stops an app from gaining extra access without admin consent17.

The short answer

QuestionAnswer
Is it safe to give an email security vendor API access to our mailboxes?It is safer when you set the access level yourself. Specific Google data holds an app to the scopes you specify, and new scopes then need admin consent
Where is the setting?Menu > Security > Access and data control > API controls
Who can change it?An admin with the Service Settings administrator privilege
How do you stop untrusted apps reading Gmail?Set Gmail to Restricted; only Trusted or Specific Google data apps can then reach its data7
How do you take access back from one app?Change its access to Blocked, which can't access any Google service13
How do you confirm the change?Read the OAuth token audit log for Authorize and Revoke events19

What you can do by the end

  • Find every app that holds a token for Gmail in your Google Workspace domain.
  • Set each mail app to Trusted, Limited, Specific Google data or Blocked by org unit.
  • Show an auditor a record of each grant and revoke.

Short on time? Watch the explainer, or book a demo.

Which access level fits read-only and read-write permissions across scope tiers?

Pick the narrowest level that still lets the app do its job. Trusted gives an app access to all Google Workspace services (OAuth scopes), including restricted services. Limited lets an app reach only unrestricted Google services. Specific Google data lets an app request only the scopes you specify, plus the Google Sign-in scopes users need to sign in. Blocked can't access any Google service.

For a read only mail tool, Specific Google data is the level that names the scopes. Google's Workspace Updates note says scope-based configuration prevents an app from gaining more access without admin consent, even if it requests new API scopes later.

Write down the level and the scopes you approved for each mail app before you change anything.

Which email security API access scopes does Gmail treat as high risk?

Google lists nine Gmail high-risk OAuth scopes that can be restricted. They include mail.google.com, gmail.modify, gmail.readonly, gmail.send and gmail.metadata9. A Restricted service accepts only apps set to Trusted or Specific Google data. A Limited app therefore loses Gmail once Gmail is Restricted.

Match each scope an app asks for against the nine on Google's help page before you pick its level. What each Gmail scope allows is set out in Gmail API scopes and Microsoft Graph permissions an email security tool asks for.

How to evaluate a vendor's API access scope requests and restrict Gmail

Compare the scopes the vendor's app requests with Google's high-risk Gmail scopes, set the app's access level, then set Gmail to Restricted. Run the steps in order and plan them for a quiet hour, because untrusted apps stop at step 6.

  1. Sign in with an admin account that has the Service Settings administrator privilege.

  2. Go to Menu > Security > Access and data control > API controls.

  3. Open Manage App Access, then Accessed apps, then View list. Filter by Requested services to find the apps that reach Gmail. The list updates 48 hours after a token is granted or revoked15.

  4. For each app you keep, select Change access and pick the org units. Choose Trusted, Limited, Specific Google data or Blocked. Then select Next, then Change access.

  5. For an app not yet listed, select Configure new app and search by app name or client ID. Choose a scope and access level, then select Finish14.

  6. Set Gmail to Restricted. Previously installed apps that you have not trusted stop working, and their tokens are revoked8.

  7. Choose the setting for unconfigured third-party apps. The default is Allow users to access any third-party apps; apps you set to Trusted, Limited or Specific Google data are not affected.

  8. If you trust your own internal apps, check the Trust internal apps box on the Internal apps settings card11.

  9. Check the OAuth token audit log (Activities.list() with applicationName=token) for Authorize and Revoke events.

Write the date and the approver next to each step in your change log.

Use least-privilege principles for mailbox access control, setting by setting

Apply least privilege one setting at a time. The table shows what each setting does and where you set it.

Setting or levelWhat it doesWhere you set itSource
TrustedAccess to all Google Workspace services (OAuth scopes), including restricted servicesManage App Access, Change access
LimitedAccess to unrestricted Google services onlySame
Specific Google dataOnly the scopes you specify, plus the Google Sign-in scopes users needSame, or Configure new app
BlockedNo access to any Google serviceSame
Restricted service (for example Gmail)Only Trusted or Specific Google data apps reach its dataAPI controls
Unconfigured third-party appsThe default is Allow users to access any third-party appsAPI controls
Trust internal appsAllows API access for all internal appsAPI controls, Settings card, Internal apps
Don't allow users to access any third-party appsAn option of the same setting: users can't sign in with Google to any third-party apps and websites until you configure them with an access settingAPI controls26
Bulk configuration by CSVA super administrator uploads a file of up to 10 MB; removing an app from the file does not delete the appCSV file upload, see source16

Keep a copy of this table with the level you chose in each row.

How do org units affect compliance and audit readiness for API access scopes?

The first policy you set on an org unit stays. Google states that if you apply an access policy to an org unit and then a different policy to the whole organization, the first policy remains in effect for that org unit12.

For the audit trail, the OAuth token audit log records an Authorize event, when a user authorized access to an application for their data, and a Revoke event.

Check each org unit's setting under API controls after any change you make at the top level.

How AegisAI handles this

AegisAI works post-delivery through the Microsoft 365 or Google Workspace API20. AegisAI's AI agents start read-only: a pilot can list users and read mail for classification, nothing more, and removal needs write access your admin grants and can revoke23. Revoke AegisAI's permissions in Microsoft Entra (Enterprise applications) or in the Google Workspace admin console, and access ends21.

Book a demoSee inbound email security

See your own records: Check your domain.

How to measure it in 30 days

Track three numbers for Gmail.

  • Apps with Gmail access, from the Accessed apps list filtered by Requested services.
  • Apps set to Trusted against apps set to Specific Google data, from Manage App Access.
  • Authorize and Revoke events in the OAuth token audit log since the change.

To see the grant and the revoke for a mail tool in your own domain, walk through a connection with the team. On day 30, block any app nobody can explain.

Questions people ask

Is it safe to give an email security vendor API access to our mailboxes?

It can be, if your admin can take the access back at any time. Revoke AegisAI's permissions in Microsoft Entra (Enterprise applications) or in the Google Workspace admin console, and access ends. The admin steps on this page set and remove that access in Google Workspace.

Do I need super admin rights to change app access?

Not for single apps. Each procedure on Google's page needs the Service Settings administrator privilege. Bulk configuration from a CSV file needs a signed-in super administrator.

What happens to apps already connected when I restrict Gmail?

Untrusted third-party apps lose Gmail access, as step 6 above describes. Set the apps you keep to Trusted or Specific Google data first.

Can an app add new Gmail scopes later without my approval?

Not when it is configured by select API scopes. Google's Workspace Updates note says this prevents apps from gaining additional access without admin consent, even if they request new scopes.

Why does the app list not show a change I made today?

The accessed apps list updates 48 hours after a token is granted or revoked. The OAuth token audit log records Authorize and Revoke events.

Sources

  1. (Google Workspace Admin Help, Control which apps access Google Workspace data, 10 November 2026)
  2. (Google Workspace Admin Help, Control which third-party and internal apps access Google Workspace data, 10 November 2026)
  3. (Google Workspace Admin Help, Add and configure third-party apps in bulk, 10 November 2026)
  4. (Google Workspace Updates, configure third-party apps by select API scopes, 3 December 2024)
  5. (Google for Developers, OAuth token audit activity events, read 17 November 2026)
  6. (AegisAI Blog, email security and mail flow, read 17 November 2026)
  7. (AegisAI, Inbound email security, read 17 November 2026)
  8. (AegisAI, How AegisAI's AI agents are secured, read 17 November 2026)
  9. (AegisAI, Is it safe to give an email security vendor API access to our mailboxes, read 17 November 2026)

Recent posts

Every email, investigated.