Blog/ Buyer guides

Google CASA Verification: What It Is and Who Needs It

Nafiul HasanNafiul Hasan· 10 min read
Diagram illustrating Google CASA verification for email apps — the path from restricted Gmail scope request through an independent security assessment to verified status on the OAuth consent screen

The short answer

Google CASA (Cloud Application Security Assessment) is the security assessment Google requires, every year, from apps that use restricted Gmail scopes such as gmail.modify and store or transmit that data on servers. An App Defense Alliance authorized lab validates the app against OWASP ASVS-based requirements and issues a Letter of Validation. It is a security baseline, not a Google endorsement.

What is Google CASA? The security assessment required for apps that use restricted Gmail scopes: levels, cost, timeline and how to check an app.

On this page
  1. 01What is Google CASA verification?
  2. 02Does an email app need CASA to connect to Gmail?
  3. 03CASA tiers vs assurance levels: Tier 2, AL1 and AL2
  4. 04How the CASA process works, step by step
  5. 05Getting CASA certified: cost, timeline and what the lab checks
  6. 06What happens if an app is not verified
  7. 07How to check whether an email app is Google verified
  8. 08Common misconceptions about Google CASA
  9. 09How CASA shows up in AI Emaily

What is Google CASA verification?#

Google CASA verification is the security assessment step of Google's restricted-scope review. Any app that requests a restricted Gmail scope, such as gmail.modify, and stores or transmits that mail data on its servers must pass it before Google approves the scope. An authorized lab validates the app against CASA requirements, then the developer sends the lab's Letter of Validation to Google.

CASA comes from the App Defense Alliance (ADA), and its requirements are built on the OWASP Application Security Verification Standard (ASVS). People call the result a CASA certification, assessment, audit or review; Google's own pages say security assessment. It repeats every year. Whether an app needs it depends on the scopes it asks for:

Scopes the app requestsWho reviews itIs CASA required?Gmail example
Non-sensitiveNo scope review (brand verification can still apply)Nogmail.labels
SensitiveGoogle's OAuth app verificationNogmail.send
Restricted, but data never stored or sent through the developer's serversGoogle's restricted-scope verificationNogmail.readonly used only on the device
Restricted, with data stored or transmitted on serversGoogle, plus an ADA authorized labYes, every yeargmail.modify, gmail.readonly, mail.google.com

Some apps are exempt from review

Google does not require submission for personal-use apps, development and testing projects, apps used only inside your own Google Workspace organization, and a few other cases listed on its restricted-scope verification page. CASA is aimed at apps offered to the public.

Does an email app need CASA to connect to Gmail?#

Almost always, if it is a full email client with a back end. Google's Gmail API scope table lists most of the scopes an email app needs as restricted: https://mail.google.com/, gmail.readonly, gmail.modify, gmail.compose, gmail.insert, gmail.metadata and gmail.settings.basic. Only a few are lighter. gmail.send is sensitive, and gmail.labels is non-sensitive.

gmail.compose is restricted too, so an app that only writes drafts is still in scope. Apps that reach Gmail over IMAP or SMTP with OAuth need the full https://mail.google.com/ scope, since Google documents it as the scope for IMAP, POP and SMTP access. Google's own guidance is to avoid that full-access scope unless an app must permanently delete mail and bypass the trash.

For a closer look at what each permission lets an app do, see restricted vs sensitive Gmail scopes and what Gmail OAuth permissions actually allow.

CASA tiers vs assurance levels: Tier 2, AL1 and AL2#

Older CASA material, assessor pages and some Google pages still talk about Tier 2 and Tier 3. Google's current Security Assessment help page uses assurance levels instead: every assessed app is assigned AL1 or AL2. The lower level is widely treated as the successor to Tier 2 and AL2 as the successor to Tier 3. The ADA does not publish an official one-to-one mapping, so follow the wording in your own notice from Google.

The developer does not pick the level. The ADA says the framework user (Google, in this case) sets the required level based on how sensitive the data is, how many users the app has, and other risk signals. Google adds that the level can go up as the user base or data practices change, and that an app validated at AL2 stays at AL2 in later years.

AL1AL2
ADA labelLab tested, lab verifiedLab tested, lab verified
How it is assessedAuthorized labs describe it as evidence the developer provides, such as scan results and a security questionnaire, verified by the labThe lab tests the application, its deployment infrastructure and any user data storage
RequirementsAll CASA requirementsAll CASA requirements
Older nameUsually described as Tier 2Usually described as Tier 3
Who gets itAssigned by Google based on riskHigher-risk apps, assigned by Google

How the CASA process works, step by step#

CASA is the last step of restricted-scope verification, not the first. Google says to finish its other verification requirements before the assessment starts.

  1. 1

    Submit the app for restricted-scope verification

    The developer configures the OAuth consent screen, lists the scopes, links a privacy policy and justifies each restricted scope in the Google Cloud console.

  2. 2

    Wait for Google's notice

    Google's Trust and Safety team tells the developer when to start the security assessment and how to proceed.

  3. 3

    Choose an ADA authorized lab

    The ADA publishes its list of authorized labs. Firms such as Bishop Fox, DEKRA, NetSentries, TAC Security and Valuementor appear on it. Labs must be ISO/IEC 17025 accredited.

  4. 4

    Complete the assessment and fix findings

    The app is checked against the CASA requirements, which come from OWASP ASVS. Findings are fixed and rechecked until every requirement is met.

  5. 5

    Send the Letter of Validation to Google

    Once the app passes, the lab issues a Letter of Validation (LOV). The developer submits it to Trust and Safety to complete the review.

  6. 6

    Revalidate every year

    Google requires reverification and a new assessment at least every 12 months from the assessor's approval date, and emails the developer when it is due. Keeping restricted scopes depends on it.

Getting CASA certified: cost, timeline and what the lab checks#

Google does not run the assessment and says it has no control over it. Issues go to the lab you chose. These are the figures Google publishes. Its Google Health API verification page gives them for CASA in general, and the Gmail-specific pages give no numbers.

  • What the lab checks: CASA requirements drawn from OWASP ASVS, covering areas such as authentication, session management, access control, data protection and cryptography.
  • What it is not: a feature review, a privacy-policy audit or a check on how the vendor uses AI. Those questions stay with you.
  • Budget for the year, not just the first pass: the assessment and its fee come back every 12 months.
QuestionWhat Google saysNotes
Who gets paidFees are payable to the third-party assessorGoogle itself does not list a fee
Cost$500 to $4,500 USD, depending on the app's complexityLabs set their own prices; the higher level costs more
Assessment time2 to 3 weeks for tier-2 apps, 4 to 6 weeks for tier-3 appsTime spent fixing findings comes on top
Whole restricted-scope reviewCan take several weeksBrand verification is usually 2 to 3 business days
ShortcutsHITRUST, SOC 2 and ISO/IEC 27001 certifications may expedite CASAThrough the CASA accelerator
RenewalEvery yearA new assessment each cycle

What happens if an app is not verified#

Google shows an unverified app screen before the consent screen when an app requests sensitive or restricted scopes and has not finished verification, or when the scopes in its code do not match its consent screen. Until it is verified, the app is limited to 100 new users. Google's Security Checkup can also list it as risky and unverified.

That warning is about verification as a whole, not only CASA. An app showing it might be new, mid-review, waiting on its lab, or missing an earlier step such as brand verification. From the warning alone you cannot tell which.

Inside Google Workspace, verification and admin approval are separate. In the Admin console (Security, then Access and data control, then API controls), admins set each app to Trusted, Limited, Specific Google data or Blocked, and can restrict Gmail to configured apps only. Verified apps show a Verified label there, but Google does not say verification grants access by itself.

For team rollouts, check admin policy too

If your organization restricts Gmail access, a verified app still needs an admin to configure it as Trusted or give it Specific Google data access. Confirm both the app's verification and your own policy before a rollout.

How to check whether an email app is Google verified#

There is no single public lookup to rely on, so check the app itself and ask the vendor.

  1. 1

    Read the screens when you connect

    A verified app goes straight to Google's consent screen, with no unverified warning first. Read the list of permissions it asks for.

  2. 2

    Match the scopes to the requirement

    If it asks for full mailbox access (read, change or delete mail) and runs a cloud service, it is in CASA scope. Ask the vendor which assurance level it was assigned and when its last Letter of Validation was issued.

  3. 3

    Review it later in your Google Account

    Your Google Account lists every third-party app with access and what it can see. Workspace admins can check the Verified label under API controls. See how to review third-party apps with Gmail access.

Common misconceptions about Google CASA#

  • Is CASA a Google endorsement? No. It shows the app met a security baseline at the time of assessment, not that Google vouches for its quality, features or reliability.
  • Does an unverified warning mean the app failed CASA? No. It means verification is not complete, which can have several causes, including steps that come before CASA.
  • Does CASA cover everything a vendor does with my mail? No. It checks application security against CASA requirements. Ask separately about AI model use, sub-processors and retention; see does AI email train on your emails.
  • Is CASA the same as SOC 2? No. Google accepts SOC 2, ISO/IEC 27001 and HITRUST to speed CASA up, but a CASA letter is not a SOC 2 report.
  • Is passing once enough? No. Restricted-scope apps revalidate every year, so ask when the most recent assessment was completed.
Conceptual illustration showing the bridge between an unverified app state and Google-verified status, with a security assessment as the step connecting the two sides
For restricted Gmail scopes handled on servers, the security assessment is the step between requesting access and verified status.

How CASA shows up in AI Emaily#

We build AI Emaily, so this is our own example. AI Emaily connects to Gmail with the restricted gmail.modify scope, which it needs to label, archive and triage mail, and it does not request the full https://mail.google.com/ scope. That puts it in CASA scope.

Our CASA Tier 2 / AL1 assessment is completed, verified by an authorized lab, and Google verified our consent screen in July 2026. It renews annually. Workspace admins who restrict Gmail access still decide whether to trust it. Details are on our security page, and the vendor question list covers what else to ask.

Frequently asked

Nafiul Hasan

Written by

Nafiul Hasan

Nafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.

EntrepreneurAI Automation System BuilderAI EnthusiastBuilds AI Enterprise Solutions10+ years experience
More from Nafiul
Ready when you are

An email client that completed Google's CASA assessment

AI Emaily's CASA assessment is completed, verified by an authorized lab, and renews annually. Connect Gmail, Outlook or IMAP mailboxes and try it with a 7-day free trial on Pro or Autopilot. See plans at aiemaily.com/pricing.

  • 7-day free trial
  • Cancel anytime
  • Every provider