Unverified50% confidenceFactExact time
The "Internal" user type of the OAuth consent screen is limited to accounts within the same Google Workspace organization and does not require Google verification; the "External" user type is open to any Google account and remains in "Testing" status until published as "Production," with limits on the number of test users and token validity period.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Step-by-Step Guide to Connecting Gmail to n8n with Custom Google OAuth
youtubeNeuralVarsity10/18/2026
Related Entities
Related Claims
UnverifiedFor Workspace business accounts, Google promises that in-domain content will not be subject to human review and will not be used to train models outside that domain without permission.71% similarUnverified在Google产品体系中,Workspace和Google One虽都提供AI能力,但企业级产品出于安全合规考虑会限制某些消费级功能70% similarUnverifiedGranting a third-party AI access to Google Workspace data involves the OAuth authorization scope mechanism; once authorized, the app can access continuously within the scope rather than only for a single session.67% similarUnverifiedHolding a Google One membership is not equivalent to being recognized as a genuine paying user in the Antigravity system, as the two account entitlement systems have hierarchical differences.65% similarUnverifiedBecause identity verification for personal developer accounts is relatively simple, Google has set stricter closed-testing prerequisites for listing review, and continues to tighten personal developer policies, including requiring address verification, identity proof, and testing headcount and duration requirements for new accounts.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1061724API
curl https://kongchang.com/api/v1/knowledge/claims/1061724MCP
get_claim(id=1061724)