Manage A2A connections in Admin Hub
The A2A Rovo x Gemini integration allows Rovo to use Gemini for organization-approved AI assistance. While in beta, the integration is disabled by default and must be explicitly enabled by an admin in Admin Hub.
Key behaviors:
Disabled by default during the beta period.
Admins can enable or disable the integration in Rovo MCP within Admin Hub.
The integration respects the organization’s AI-enabled apps setting.
Users must complete OAuth 2.1 authorization before Rovo can call Gemini on their behalf. More information on the setup .
Rovo only acts within the authenticated user’s existing permissions in connected systems.
Prerequisites
Before enabling the A2A Rovo x Gemini integration, confirm:
You are an organization admin with access to Admin Hub and Rovo MCP.
Your organization has AI-enabled apps turned on for the relevant products; if AI-enabled apps are turned off at the org level, this integration remains effectively disabled even if switched on in Rovo MCP.
Your security and compliance teams have approved using Gemini with Rovo.
Enable/disable in Admin Hub (Rovo MCP)
The integration is disabled by default while in beta. Admins control it from within Rovo MCP in Admin Hub.
To enable:
Go to Atlassian Administration > Rovo > Rovo MCP server.
Locate the A2A tab.
Turn on the Allow A2A toggle to enable the A2A integration. Gemini will then be available to Rovo in any products where AI-enabled apps are allowed by your organization’s settings.
How access is enforced
Rovo enforces multiple layers of control when using the Gemini integration:
Org-level control: If AI-enabled apps are turned off at the organization level, Rovo will not use Gemini even if the integration is enabled in Rovo MCP.
App-level control: The integration toggle in Rovo MCP determines whether Rovo can send requests to Gemini at all.
User-level control: Rovo only uses Gemini with a valid OAuth 2.1 grant and always acts within the user’s effective permissions.
Troubleshooting
Use the checks below if users report that Rovo cannot use Gemini.
Integration appears unavailable to all users:
Confirm the A2A Rovo x Gemini integration is enabled in Rovo MCP in Admin Hub.
Verify that AI-enabled apps are turned on in your organization settings.
Specific user cannot use Gemini features:
Ask the user to complete or retry the OAuth 2.1 authorization flow when prompted by Rovo.
Check that the user has sufficient permissions in the underlying products and data sources; Rovo will not exceed the user’s existing permissions.
Behavior differs between environments or groups:
Confirm that org-level AI-enabled apps settings are consistent across the affected environments.
Verify that the Gemini integration toggle in Rovo MCP is set as expected in each environment.
Was this helpful?