Best practices for Rovo + Google Drive (Permissions & Indexing)

lrusu

Hi everyone,

We are currently exploring Atlassian Rovo and looking to integrate our Google Drive workspace to enable cross-platform search and Agent actions.

• Before we go live, I wanted to ask those who have already made the jump about a few specific areas:
• We’ve noticed that while the Admin Connector (via Domain-Wide Delegation) respects our Shared Drive allowlists, individual user OAuth seems to bypass this, allowing Rovo to see personal "My Drive" content. How are you handling this from a governance perspective? Are you restricting the Atlassian app scopes in Google Admin, or just relying on user education?
• For those with large Drive environments (10k+ docs), how long did the initial crawl take before results became reliable in Rovo Chat? Did you notice any "index lag" for new documents?
• Has anyone successfully built a Rovo Agent using Forge that can write back to Google Sheets/Docs based on Confluence data? I’d love to hear if you used the native connector or built a custom MCP bridge for more granular "Write" actions.

Appreciate any insights or "lessons learned" you can share!

Thanks,
Liv

Nancy Thomas_4f29q8

We’ve also noticed that user OAuth bypasses Shared Drive restrictions, and we're exploring governance strategies. We restrict app scopes in Google Admin but also rely on user education. As for the initial crawl, it took around 2-3 days for large environments. For the Rovo Agent, we’ve considered using Forge with custom MCP bridges for granular actions.