Connect Google Workspace and Gemini to Jira, Confluence, and Rovo
Atlassian and Google connect in six ways: Teamwork Graph connectors for Google Drive, Gmail, and Google Calendar; the Atlassian Rovo Agent in Gemini Enterprise; the Atlassian MCP Server in Gemini CLI and Code Assist; and Gemini model selection in Rovo Agents. The connection runs both ways: bring Google Drive, Gmail, and Calendar into Rovo and enrich the Teamwork Graph or access Jira and Confluence context from Gemini Enterprise, Gemini CLI, and Code Assist. Users can also select Gemini models to build custom Rovo agents.
The result: AI grounded in the context of your work and less switching between tools.
The end-to-end experience
Connect knowledge: Sync permitted Docs, Sheets, and Slides from Google Drive.
Connect communication: Retrieve relevant Gmail context through the user’s authorized connection.
Connect commitments: Make permitted Google Calendar events available alongside plans and work.
Reason and act: Use Rovo, Gemini Enterprise, Gemini CLI, or a Rovo Agent to connect the context.
Keep work governed: Apply source permissions, administrator policy, OAuth, and human review.
One connected loop: Google Workspace contributes knowledge, communication, and meeting context → the Teamwork Graph connects it to Jira and Confluence → Rovo and Gemini help people reason and act → source systems remain authoritative.
Coming soon, Atlassian on Google Cloud will bring these tools together on one connected platform with one shared context, built for the way your teams actually work.
Explore the ways to connect Google and Atlassian
Teamwork Graph connector for Google Drive: Find Google Drive knowledge from Rovo
Best for: teams whose project plans, research, spreadsheets, and presentations span Google Drive and Atlassian.
Connect Google Drive to make permitted Google Docs, Sheets, Slides, and shared-drive content available in Rovo Search, Chat, and eligible Agents. Rovo can place Drive knowledge alongside Jira work and Confluence pages, helping teams find the answer without first knowing which system contains it.
Search by topic instead of guessing where a file was saved: Find the current Project Meridian customer onboarding plan and the Jira initiative it supports.
Value moment: Teams can understand a project across Atlassian and Google Drive without manually reconciling separate search results.
Requirements: An organization administrator connects Google Drive and configures the relevant users, groups, and content scope. Rovo carries source permissions into the connected experience.
Teamwork Graph connector for Gmail: Bring relevant Gmail context into Rovo
Best for: people who need to extract decisions, commitments, and customer context that lives in their inbox.
Gmail uses a federated connection: Rovo calls the Gmail API at query time with the user’s OAuth authorization instead of copying the inbox into a full Atlassian index. This lets Rovo retrieve relevant threads and messages while Gmail remains the source of truth.
Value moment: an important email becomes usable project context without turning the inbox into another manually maintained knowledge base.
Requirements: user OAuth authorization, an eligible Rovo experience, and any administrator approval required by the organization.
Teamwork Graph connector for Google Calendar: Connect Google Calendar commitments to the work
Best for: program, product, service, and leadership teams that need meeting and milestone context alongside Jira and Confluence.
When enabled by an administrator, the Google Calendar connector synchronizes permitted calendar events and their relevant metadata into the Teamwork Graph. Rovo can then connect meetings, attendees, dates, and recurring-event context to the projects and work they affect.
Value moment: calendar commitments become part of the delivery story instead of isolated dates on a schedule.
Requirements: administrator configuration, Google Workspace authorization with the required delegation and API access, and eligibility for the Calendar connector. Calendar context is read-only — Rovo doesn’t create or edit events.
Agent-to-Agent (A2A): Invoke Rovo from Gemini Enterprise
Best for: organizations that use Gemini Enterprise as an AI workspace and want Atlassian context and reasoning available there.
Generally available since April 22, 2026, the Atlassian Rovo Agent lets you bring Jira and Confluence context right inside Gemini Enterprise. Get it from Google Cloud Marketplace, and after a one-time install and OAuth consent, Rovo returns only the content you’re permitted to see without switching apps.
Connect Atlassian Rovo Agent and Gemini Enterprise
Value moment: people can reach Atlassian’s teamwork context and reasoning from the Google AI environment their organization already uses.
Requirements: Gemini Enterprise, an Atlassian Cloud organization with Rovo enabled, Google Cloud Marketplace installation, OAuth consent, and administrator policy allowing the A2A connection.
Get the Atlassian Rovo Agent on Google Cloud Marketplace · Learn about publishing agents in Gemini Enterprise
Atlassian MCP Server: Build with Atlassian context in Gemini CLI
Best for: developers who need Jira requirements and Confluence decisions available to move work forward without leaving the terminal
Access Jira context without leaving Gemini CLI
The Atlassian MCP server connects to Gemini CLI. After OAuth authorization, developers can retrieve supported Atlassian context from the terminal, keeping implementation grounded in the work and decisions tracked by the broader team.
Value moment: Track and create work items without leaving the terminal to stay in the flow.
Requirements: an eligible Gemini CLI or Code Assist tier (Code Assist for individuals, Google AI Pro/Ultra, or Code Assist Standard/Enterprise and Workspace AI Ultra for organizations), Atlassian Cloud access on any plan, repository access, and permission to the Jira and Confluence content requested.
Model selection: Choose Google Gemini models for a Rovo Agent
Best for: Rovo agent builders who want to match the model family and reasoning profile to the work an agent performs.
Put Google Gemini behind your Rovo Agents. Eligible builders can select from supported models — including Gemini — and match the reasoning profile to each use case, while every agent stays grounded in your Atlassian context, instructions, and permissions.
Choose Google Gemini models to build Rovo Agents
Value moment: organizations get model choice while retaining the Atlassian context and governance that make the agent useful at work.
Requirements: an eligible Rovo plan and permission to create or configure Rovo Agents. Available model options vary by plan, region, and product configuration.
How the experiences work together
These experiences solve problems across different jobs. Pull Google context into Rovo, reach Atlassian from Gemini, and put Gemini models behind your own agents. Start with the one that fits the job.
If you want to… | Start with… |
Find Docs, Sheets, Slides, and shared-drive knowledge with Atlassian work | Teamwork Graph connector for Google Drive |
Retrieve relevant decisions and commitments from email | Teamwork Graph connector for Gmail |
Connect meetings and dates to projects and delivery work | Teamwork Graph connector for Google Calendar |
Check launch or delivery readiness from Jira and Confluence while working in Gemini Enterprise | Rovo Agent in Gemini Enterprise through A2A |
Use Jira and Confluence context while coding | Gemini CLI or Gemini Code Assist with Atlassian MCP Server |
Use Gemini behind an Atlassian agent | Model selection in Rovo Agents |
These experiences are complementary. Drive and Calendar provide synced context, Gmail retrieves live user-authorized context, Gemini Enterprise invokes Rovo through A2A, Gemini development tools connect through MCP, and Rovo model selection brings Gemini into Atlassian-built agents.
Trust and control are part of the workflow
Different connectors, different data paths: Drive and Calendar can synchronize permitted objects; Gmail retrieves live data through the user’s authorized API connection.
Source permissions apply: connected experiences should expose only content and events the user is allowed to access in Google or Atlassian.
Secure authorization: Google and Atlassian integrations use OAuth and administrator-approved configuration rather than asking users to paste passwords into prompts.
Administrator controls: organizations can manage connectors, AI-enabled apps, and A2A/MCP connections according to plan and policy.
Human review: review high-impact email, calendar, Jira, Confluence, and code actions before execution.
Client terms matter: when Atlassian content is sent to a Google AI client, the organization’s Google plan and terms govern Google-side processing. This differs from Gemini models used inside Atlassian-managed Rovo experiences.
FAQs
How do I connect Google Drive to Rovo?
An organization admin adds the Google Drive connector in Atlassian Administration and sets up domain-wide delegation in Google, choosing which drives, groups, and content are in scope. Each team member then links their own Google account, so Rovo returns only the Drive files they’re already permitted to see.
What’s available today? You can connect Google Drive, Gmail, and Google Calendar to Rovo through the Teamwork Graph today, bringing permitted Google Workspace context into your Atlassian work. The Atlassian Rovo Agent is also live in Gemini Enterprise via A2A, and Gemini CLI and Code Assist connect through the Atlassian MCP Server.
Who can see what? Connected experiences should surface only the content and events a user is already permitted to access in Google and Atlassian. Connecting a source doesn’t widen access, and administrators control which users, groups, and content are in scope.
Can Gemini CLI create or update Jira and Confluence work, through the Atlassian MCP Server?
With the Atlassian MCP Server connected to Gemini CLI or Code Assist, your AI client can create and update Atlassian work — for example, draft a Confluence page and update the linked Jira issue in one flow. Every action runs under your existing Atlassian permissions, edits change only the parts you name, and high-impact changes can be previewed before they’re saved.
Is my Google data copied into Atlassian? It depends on the connector. Drive and Calendar index permitted content into the Teamwork Graph so Rovo can search it. Gmail uses a federated connection instead — Rovo calls the Gmail API at query time under your OAuth authorization, so nothing is copied and Gmail stays the source of truth.
Getting started
Choose the data path. Use a synced connector for Drive or Calendar and a direct, user-authorized connection for Gmail.
Confirm permissions and scope. Configure users, groups, shared drives, calendars, and administrator policy before rollout.
Add the AI surface. Install Rovo in Gemini Enterprise, connect Gemini CLI through MCP, or select Gemini for an eligible Rovo Agent.
Begin read-first. Test search and summarization before enabling write or agent actions.