Hey everyone! I’m working on a Google Drive integration for my company and I’m wondering if it’s possible to build this without going through the Chrome Web Store approval process. We just need it for internal use.
I’ve been following the Google Drive API documentation and managed to get the OAuth flow working. Users can authenticate successfully, but then I hit this error message: “403 : The Authenticated user has not installed the app with the client id {my_client_id}”
It seems like Google expects the app to be installed from their store, but that doesn’t make sense for internal tools. Has anyone dealt with this before? Is there a way to configure the API permissions differently for private applications?
This is a workspace config issue, not an app store thing. When you set up your Google Cloud project, it needs to be tied to your organization’s Google Workspace domain. That error usually pops up when the logged-in user’s domain doesn’t match what the project expects. Go to your Google Cloud Console → IAM & Admin settings and check that the project is actually linked to your company’s workspace. Also make sure everyone trying to use your app has accounts under the same org domain. I hit the same problem building our internal file sync tool - turned out some test accounts weren’t set up right in our workspace directory. Fixed the domain alignment and the 403 errors went away completely.
yeah, you should def skip the chrome store! make sure your oauth scopes are correct. try changing your app to ‘internal’ in the google cloud console. also, check your redirect uris to match exactly what you have in your code. gl!
Had this exact problem last year building an internal doc management system. You don’t need to publish to the Chrome Web Store - internal-only apps work fine. That 403 error usually means your Google Cloud Console project isn’t set up right for internal use. Go to OAuth consent screen in your GCP project and make sure you picked “Internal” as the user type. This locks it down to just your organization’s domain. Also check that you’re using the right client credentials and that Drive API is enabled. I’ve seen the error stick around when there are old cached tokens floating around. Clear your browser storage and re-authenticate after fixing the config. Setting it to internal should fix your installation problem completely.