We have recently published a chat app to the Google Workspace Marketplace (here’s the app if you want to check it out). The only scope we have is the external_request scope, which is necessary to allow communication with our backend. For having that scope, users need to click on a configure button after they install the app. For some reason, they are sometimes redirected to request access to the apps script file of the app instead of granting permissions. Has it occurred to someone else?
1 Like
Hey,
Hope you’re keeping well.
This usually happens when the Chat app is still linked to an underlying Apps Script project in the same deployment, and the script’s permissions are being surfaced instead of just the add-on scopes. In the Google Cloud Console, check your deployment configuration to ensure the Chat app is published as a standalone project and not referencing the Apps Script manifest directly for OAuth. If you’re using Apps Script as the backend, verify the appsscript.json only declares the external_request scope and that all other services are removed. Also confirm in the Google Workspace Marketplace SDK settings that the OAuth client matches the intended app and doesn’t point to the script’s default client. This helps avoid the “request access to script” redirect issue.
Thanks and regards,
Taz