Connect Atlassian Rovo to Google Drive
What Atlassian Rovo and Google Drive document about their connection: what it does, what it takes to turn it on, what it costs and the data that passes from one to the other. Each fact with its source at the vendor and its date.
What the connection does
- What it does. Google Drive is connected to Teamwork Graph so that workspace files can be searched in Rovo Search, Chat and agents (according to Atlassian's documentation, read on 10/17/2026).
- The direction. From Google Drive to Atlassian Rovo.
- The mode. Through an integration offered by the vendor.
What it takes to turn it on
- The editions or licenses required. Rovo, including Search, Chat, Studio and agents, is available with a Standard, Premium or Enterprise Cloud plan of Jira, Confluence, Jira Service Management, or Service and Teamwork Collections. If the organization has at least one of these paid Cloud plans, Rovo is added automatically to eligible sites as part of the rollout, with no separate Rovo purchase required (according to Atlassian's documentation, read on 10/17/2026).
- What it costs on top, or how it is billed. The subscription includes an indexed objects allowance that depends on the number of seats and the edition; allowances are pooled at the organization level (according to Atlassian's documentation, read on 10/17/2026).
- Who turns it on. The organization admin (or someone with access to Atlassian Administration and Google Admin) completes the setup, including domain-wide delegation in Google; each team member then connects their own Google account to Atlassian when prompted, so that Rovo only returns the Drive results they are allowed to see (according to Atlassian's documentation, read on 10/17/2026).
- The prerequisites. One needs a Google account that can use the Google Admin console with the privileges described (read-only access to the Admin API is enough; a Super Admin may be needed to create that account or role), as well as domain-wide delegation in Google Workspace for Atlassian's client ID and OAuth scopes (according to Atlassian's documentation, read on 10/17/2026).
The data that flows
- What passes. Google Drive data is synced to Atlassian for indexing and search; when Rovo runs, the person's own Google Drive access is used (according to Atlassian's documentation, read on 10/17/2026).
- Whether the source tool's permissions are respected. Google Drive sharing settings continue to apply; Teamwork Graph does not bypass them (according to Atlassian's documentation, read on 10/17/2026).
- Where the data is processed. The organization admin can choose where the relevant Rovo data is stored, using the data residency controls in Atlassian Administration (according to Atlassian's documentation, read on 10/17/2026).
- Training. User data obtained through sensitive or restricted Google Workspace API scopes is not used to develop, improve or train general-purpose AI or machine learning models (according to Atlassian's documentation, read on 10/17/2026).
- Retention. If an organization admin disconnects the third-party app from Rovo, the indexed content from that app is deleted within 30 days (according to Atlassian's documentation, read on 10/17/2026).
With Ojja
Ojja tells you whether you already pay for both tools, whether the connection is turned on in your company, who uses it, and the usage before and after: it is the “Connect” lever of what your tools can already do.
What Ojja never does
- Ojja does not advise you to choose a vendor: it records what each one documents.
- Ojja does not say whether a use is permitted: it gives the facts, and the points to review with your counsel.
Ojja does not provide legal advice: it records and documents; how the law applies to your situation is for your counsel to determine.
Checked on 10/17/2026. When a vendor says nothing, the page says “not documented by the vendor”.