> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/faq-and-troubleshooting/gmail-connection-blocked.md).

# Gmail connection blocked by Google

If Google displays “This app is blocked” while connecting Gmail, capture the exact message and identify the account you are trying to connect.

## Start with the built-in Gmail connection

1. In Jet Admin, open **Data → Add Resource**.
2. Select **Gmail**.
3. Sign in to the Google account whose mailbox you want to connect.
4. Review the requested access and complete the connection if Google permits it.

This is the built-in connection flow. If you are following instructions for a custom OAuth client and are being asked for a redirect URI, first check whether the [Gmail integration](https://docs.jetadmin.io/user-guide/data-sources/business-apps/gmail) meets your task.

## Google blocks authorization

A blocked authorization is different from an incorrect Jet Admin password. If this is a managed Google Workspace account, ask its administrator to check whether an organizational policy is involved.

If the block persists, contact Jet Admin support with:

* The app URL and exact Google error.
* Whether this is a personal or managed Workspace account.
* Whether the Gmail mailbox is different from the account used to sign in to Jet Admin.
* The time of the attempt and a screenshot with sensitive details removed.

The error alone does not establish whether the cause is an organization policy or an integration issue. Do not bypass the block or create a replacement OAuth configuration without confirming the cause.

## Verify the connection

Once authorization succeeds, confirm the intended Gmail resource appears and test a read operation before using it in an automation.

*Last reviewed: September 16, 2026.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/faq-and-troubleshooting/gmail-connection-blocked.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.