google drive connector doesn't work with access to specific files
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.2k
- Forks
- 751
- Avg merge
- 12h 1m
- Merged PRs (30d)
- 43
Description
When authoriszing grok bot to connect to google drive, there are two options:
- Allow it to download ALL the files
- Give it "See, edit, create, and delete only the specific Google Drive files you use with this app"
Google doesn't let you pick the files for security reasons. Instead the onus is on the authorising app to have a file picker. But grok bot doesn't.
Seems weird that only way grok bot works is by giving it access to ALL my files?
Notes from gemini:
It is completely normal that you didn't see a screen to select your files during the authorization process. This is a very common source of confusion!
When you grant an app the "see, edit, create, and delete only the specific Google Drive files you use with this app" permission (known technically as the drive.file scope), the initial consent page is not where you pick the files. Instead, you are simply granting the app the capability to access individual files on a case-by-case basis later on.
Here is how the app will actually gain access to specific files once authorized:
1. The In-App File Picker
Most apps using this permission will feature an "Import," "Open," or "Select from Google Drive" button inside their own interface. Clicking this opens a secure, Google-hosted pop-up window. When you select a file in that window, you are securely handing the app the "keys" to just that specific file.
2. The "Open With" Menu
If you go to your standard Google Drive web interface, right-click a file, select Open with, and choose the authorized app, it immediately grants the app access to that single file so you can work on it.
3. Files the App Creates
The app automatically has full access (view, edit, delete) to any brand new files or folders it creates directly within your Google Drive.
Why Google Uses This Method
- Enhanced Security: By not asking for blanket access to your entire Drive, your private data is kept much safer. The app can only see exactly what you explicitly hand over to it.
- Better Workflow: Instead of making you guess which files you might want to use during the initial login screen, you can just pick files naturally as you use the app over time.
If the app hasn't shown you a way to select files yet, try looking for an import or browse button within the app itself.
Have you been able to find a button inside the app's interface to open your Drive files, or are you still stuck trying to get the app to work?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the Google Drive connector and its authorization flow, then determine how users can select individual files after granting access. Done means the connector supports specific-file access without requiring permission for the entire Drive, with coverage for that authorization path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100