Description: When creating an auth config with use_composio_managed_auth and overriding credentials.scopes to a narrower scope (e.g. https://www.googleapis.com/auth/gmail.readonly instead of the default https://mail.google.com/), the OAuth consent flow fails with Google's "This app is blocked" error. Steps to reproduce: http POST /api/v3/auth_configs { "toolkit": { "slug": "gmail" }, "auth_config": { "type": "use_composio_managed_auth", "credentials": { "scopes": "https://www.googleapis.com/auth/gmail.readonly" } } } Then initiate a connection using that auth config and complete the OAuth flow. Google blocks with: "This app tried to access sensitive info in your Google Account." Expected behavior: The scope override should work, or the API should return a clear error indicating that the custom scope is not supported under managed auth. Actual behavior: Auth config is created successfully with no error. The failure only surfaces at runtime during the OAuth consent step, making it hard to diagnose. Question: Does Composio's managed OAuth app have verified scope coverage for gmail.readonly, calendar.readonly, drive.readonly, spreadsheets.readonly? If not, is there a way to know which scopes are supported for scope overrides on managed auth, or a recommended alternative for granting read-only access?

Hey @John, our default OAuth app is not verified for https://www.googleapis.com/auth/gmail.readonly scope. You can use your own credentials to use the specific sensitive scope: https://docs.composio.dev/toolkits/gmail#why-am-i-seeing-app-is-blocked-when-connecting-gmail Thanks!