Google Connection: Permissions Missing Warning

Modified on Thu, 25 Sep at 7:48 AM

Google’s latest OAuth flow lets users select only some permissions (scopes) when connecting an app. That flexibility can leave required permissions ungranted, which then breaks features (e.g., connecting Google Business Profile).
This release adds clear in-app warnings and a one-click fix so users can grant missing permissions, if required.
What’s New
  • Google Oauth from integration page now gives scopes with checkbox, Users can select scopes that they want.
    (It is recommended to select all scopes)
  • Warning badge on the Google integration card whenever required scopes are missing.
  • Details screen listing highlighting which scopes are missing, and which features are affected
  • Reconnect CTA that re-runs Google OAuth so users can grant the additional scopes.
How to use:
  1. Go to Settings → Integrations → Google.
  2. If you see a warning on your primary Google account, click the message.
  3. Review the missing scopes & affected features, then click Reconnect.
  4. In Google’s consent screen, allow the additional scopes and finish.
  5. Return to the integration page; the warning should be cleared.
Why it Matters
  1. Reduces “it’s connected but not working” confusion.
  2. Self-serve remediation for common tickets (e.g., “Primary Google connected, GBP is not connecting”).
  3. Fewer support escalations.
Preview:
Permissions with checkbox in Oauth flow:
Optional_Scopes_Oauth
Warning on Google card, if all scopes are not added:
Warning message
Permission feature mapping to guide which permissions affect which features
Scope_feature mapping


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article