Google Drive Knowledge Base — Folder-level selection not supported

Q&A
, ,
1

Hi everyone,

We’re setting up Amazon Quick for our internal teams (Sales, Marketing, Finance, HR). Our Google Shared Drives are organized by area — one Shared Drive per department (Marketing, Finance, HR, etc.), and within each drive we have multiple folders (50+ client folders, internal processes, etc.).

For our Marketing team, I was able to connect the entire Shared Drive by specifying just the Shared Drive ID, which brought in all files automatically. That works great because we need everything in that drive.

However, for our Finance and HR teams, I only need specific folders within the Shared Drives — not the entire drive. Currently, the Google Drive connector only seems to support two options:

  1. Entire Shared Drive (by specifying the Shared Drive ID)

  2. Individual file selection (one by one)

There’s no option to select specific folders within a Shared Drive. I also tried using a Google Drive folder ID instead of the Shared Drive ID, but that doesn’t work either.

Selecting files individually is not feasible when you’re dealing with folders containing dozens or hundreds of files that need to be indexed.

Request: Could folder-level selection be added as a supported option when configuring a Google Drive Knowledge Base? Something like allowing users to specify one or more folder IDs to scope the content that gets indexed.

This would be extremely helpful for teams that need a curated subset of a Shared Drive without having to reorganize their entire Google Drive structure or manually pick files one by one.

Thanks in advance for any guidance or workarounds I might be missing!

2

Hi @gabriel.maia and welcome to the community!

Thanks for providing so much detail about this case. As per my understanding, you’re correct that the Google Drive connector currently only supports connecting an entire Shared Drive or selecting individual files. Unfortunately, I do not think there is a real workaround for this other than the two options you’ve already identified. I will go ahead and mark this with the ‘feature-request’ tag and archive this post, so that it promotes greater visibility to the product team.