Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | ## An unapproved Google OAuth scope can block consent |
| 2 | |
| 3 | Google can block sign-in when an OAuth app requests a sensitive or restricted |
| 4 | scope that is not approved for that app. Use the scopes already available on |
| 5 | the selected Composio auth config, or create a customer-owned Google OAuth app |
| 6 | and complete Google's required verification before requesting additional |
| 7 | scopes. After changing scopes, create a fresh connection so the user grants the |
| 8 | new scope set. |
| 9 | |
| 10 | Google's current verification requirements are documented in its |
| 11 | [OAuth 2.0 policies](https://developers.google.com/identity/protocols/oauth2/policies) |
| 12 | and [sensitive-scope verification guide](https://developers.google.com/identity/protocols/oauth2/production-readiness/sensitive-scope-verification). |
| 13 | |
| 14 | ## A customer-owned OAuth app controls the provider consent-screen brand |
| 15 | |
| 16 | Use a customer-owned Google OAuth app when the Google consent screen should |
| 17 | show the customer's app name and branding. A callback forwarder on the |
| 18 | customer's domain still redirects the browser to Composio; it does not hide |
| 19 | Composio's domain. The forwarding endpoint receives the authorization code and |
| 20 | state, so its query string must not be logged. See |
| 21 | [callback-domain limits](/docs/authentication/white-labeling-authentication#routing-the-callback-through-your-domain). |
| 22 | |
| 23 | The OAuth app's authorized redirect URI must still match the callback URI |
| 24 | shown by Composio. Provider consent-screen branding and the URL to which the |
| 25 | customer's application sends a user after authentication are separate settings. |