My situation: I built a web application that connects with Google Drive API. Users can log in through our platform and import their Drive images directly into our tool. This integration works perfectly for our needs.
The problem: Even though we only want one-way integration (users accessing Drive from our app), Google Drive automatically adds our application to the “Open with” menu that appears when users right-click files in their Drive interface.
What I want: I need to prevent our application from appearing in Google Drive’s context menu options. Users should only be able to access Drive content through our platform, not the other way around.
Question: Is there a configuration setting or API parameter that controls whether an integrated app shows up in Drive’s “Open with” dropdown menu? I want to maintain the API connection but remove our app from that particular user interface element.
check your apps manifest file in the google workspace marketplace sdk config. theres usually a driveExtension section that controls this stuff. just remove or comment out the openUrlTemplate parameter and it should stop showing up in the context menu. worked for me when i had same issue last year
Had this exact scenario with a document processing app we developed. The key is in your Google Cloud project’s OAuth consent screen configuration, not just the Drive API settings. When you set up OAuth scopes, there’s a section for application type that defaults to allowing Drive integration. You need to modify the OAuth configuration to specify restricted scopes that only allow reading Drive content without registering as a Drive app handler. This prevents Google from automatically adding your application to the context menu registry. The process requires re-verification if your app is already published, but it completely removes the unwanted menu appearance while preserving your API functionality. Worth noting that changes can take up to 24 hours to propagate across all user accounts.
The display of your application in the Google Drive ‘Open with’ context menu is tied to your app’s settings in the Google Cloud Console rather than the Drive API itself. When your application was registered, the default settings enabled this integration based on the types of data you specified.
To address this, access your project in the Google Cloud Console and locate the Google Drive API configuration. Within the ‘Drive UI Integration’ settings, you can find an option to disable this integration, allowing you to prevent your app from appearing in the context menu while maintaining API access. I’ve experienced similar issues before when developing tools, and removing unnecessary UI integrations clarified user interactions without affecting functionality.