Latest

Atlassian's Rovo Search: What It Covers, Its Documented Limits, and When to Roll It Out

According to Atlassian, Rovo Search spans Confluence, Jira, and Atlas and can pull in connected third-party apps—but a documented edge case means some users may see recently viewed items they no longer have access to.

What Rovo Search actually covers

According to Atlassian's official documentation, Rovo Search operates at two levels. The quick-find layer surfaces recently viewed or edited content, related spaces, and related people as soon as you begin typing in Confluence—useful for resuming work without a full query. The full-page search extends results across Confluence, Jira, and Atlas, and can pull in connected third-party apps such as Google Drive or Slack once you have authorised each connection.

Atlassian states that access control is enforced at the connection stage: you will only see results you have permission to view, and Rovo requires you to connect each third-party app precisely so it can apply those permissions. However, the documentation notes one documented gap—in rare circumstances, some users may see items in their "Recently viewed" list that they have since lost access to. That is a small but concrete edge case worth noting before rollout.

When to proceed and what to verify first

The case for trialling Rovo Search is strongest when your organisation already uses Confluence and Jira, and your access permissions in those tools are well-maintained. In that situation, the documented access model maps cleanly onto what you already control. The "Recently viewed" anomaly is worth flagging to users in sensitive roles, but Atlassian describes it as rare rather than systematic.

Hold off on a broader rollout if you rely heavily on Confluence or Jira Data Center instances connected in parallel: Atlassian's documentation states that search results across multiple Data Center instances are not filtered per individual instance, and result counts may appear higher than the items actually accessible. That behaviour warrants testing in your specific environment before users interpret inflated counts as genuine matches. Independent performance and regional availability have not been verified by Chooscope; the Rovo Search documentation remains the authoritative source for current scope.

Sources

  1. Atlassian — 2026-10-18

Change history

  • rev.1Published

Display language

Related