I got permission from my company admin to deploy my Apps Script add-on to our internal Workspace Marketplace. During development and testing, everything worked perfectly and I could use all the features without any issues.
However, after publishing it officially through the Google Workspace Marketplace and installing it from there, the add-on appears grayed out and cannot be clicked. It shows up in the Extensions menu but is completely disabled.
I have included all the required OAuth permissions in my appsscript.json configuration file:
"oauthScopes": [
"https://www.googleapis.com/auth/documents.currentonly",
"https://www.googleapis.com/auth/script.external_request",
"https://www.googleapis.com/auth/script.container.ui",
"https://www.googleapis.com/auth/userinfo.email"
]
The add-on worked fine when I was testing it in development mode, but now that it’s officially installed from the marketplace, users cannot access it. What could be causing this issue and how can I fix it?
sounds like a classic issue with marketplace deployment. check the visibility settings in the admin console - sometimes org domain restrictions mess up after publishing. also, ensure your oauth consent screen is for internal use, not just the testing mode.
Had the same issue last month with my document automation add-on. Google Workspace Marketplace creates a different deployment context than your dev environment - your add-on’s probably running under a different script ID or deployment version after going live. Check your Apps Script project and create a new deployment specifically for the marketplace version. Also make sure the manifest version in your appsscript.json matches what you submitted. The marketplace sometimes caches old config versions. Try uninstalling and reinstalling after fixing your deployment settings. That grayed-out state usually means there’s a mismatch between expected and actual deployment config.
I’ve experienced this issue before and it’s indeed frustrating. The problem often arises because Google alters the verification requirements after your marketplace publishing. They typically require additional verification steps that weren’t necessary during development. Start by checking your Google Cloud Console for any pending verifications or security alerts. Additionally, ensure that your add-on’s installation URL is identical to what’s listed in the marketplace; even minor discrepancies in the deployment ID or link can lead to the add-on being grayed out. You may need to resubmit for verification or adjust your OAuth consent screen settings to align with the published version.