Use Rovo across multiple sites
Rovo Search, Chat and agents can now draw on knowledge from up to five sites in the same Unit. It is coming soon to Atlassian Cloud.
- Coming soon
- Low impact
- Admin review: api change
What it is
Improvement
Rovo can find information and answer questions using content from up to five sites in one Unit. In Search and Chat, you choose which sites to include. For an agent, you set its knowledge sources from those sites. Existing permissions still apply, and selecting a site does not grant extra access.
In Confluence full-page search and in Rovo Chat, users pick which sites to include, and each feature and site keeps its own selection.
No additional admin action is needed to use multi-site Rovo, and existing permissions apply.
Multi-site Rovo capabilities are also available through the Model Context Protocol (MCP).
Written from Atlassian's release note and checked against it automatically. Atlassian's original stays the source of truth.
Before it lands
- Check whether your organization has multiple sites in the same Unit.
- Confirm you do not use customer-managed keys (CMK), which multi-site Rovo does not support.
- Note that third-party connector content is not supported across sites.
- Review permissions on your sites, since existing access rules still apply.
What changed
- Added to Atlassian's release notes as coming soon
- First published by Atlassian
Atlas Bench began tracking Atlassian Cloud on 29 Oct 2026. Changes before that date are not in this history.