Unable to Select Specific Google Drive Files/Folders as Knowledge Source for Rovo Agent

[Rhick Esteves]

I’m trying to configure a Rovo agent to use content from Google Drive as a knowledge source. While Google Drive appears as an available source, there doesn’t seem to be any option to select specific files or folders within Drive.

My goal is to restrict the agent’s knowledge to a particular file or folder, rather than granting access to the entire Drive. At the moment, it’s unclear how to do this or whether it’s supported.

Could you please clarify:

• Whether it’s possible to select individual Google Drive files or folders as a knowledge source for a Rovo agent

• If so, what steps are required to enable or configure this

• If not, whether this is a known limitation or something planned for future support
  
  

Any guidance or documentation would be appreciated.

[Ryan Boyd · Accepted solution]

In my experience it's a known limitation. I've tried Rovo within a specific folder by hard coding it in the instructions and the output doesn't land well. It has a hard time seeing within the folder and navigating due to google edge cases. 

[Dr Valeri Colon _Connect Centric_]

Welcome to the community @Rhick Esteves and @Ryan Boyd is correct - Rovo’s Google Drive connector doesn’t yet allow selecting individual files or folders. Once connected, it indexes Drive at the scope granted to the app, and you can’t narrow it to a specific path for an agent. This is a current limitation of the connector rather than a misconfiguration. Atlassian has noted finer-grained source selection is planned, so watch release notes for updates.