GILD verdict
Buy it if your company already runs on Jira and Confluence.
Before Rovo becomes the way people ask questions, settle the data terms, clean the busiest spaces, and cap extra usage. Limit Rovo to named groups until Atlassian fixes the URL retrieval flaw PromptArmor reported, because turning off web search does not stop it.
Confluence
Team Workspace by Atlassian
+8 MixedFit and limits
Who it fits
- Teams already document in Confluence and track work in Jira, so Rovo answers from both under each user's permissions.
- You want AI included in the seat: Rovo Search, Chat, Studio, and agents come with every Standard, Premium, and Enterprise Cloud plan.
- Other knowledge sits in apps on Atlassian's connector list, such as Google Drive, SharePoint, Slack, Microsoft Teams, GitHub, or Notion.
- Other AI tools need company context: the Atlassian MCP server serves Confluence and Jira to Claude, ChatGPT, Gemini, GitHub Copilot, and Cursor.
Where it falls short
- On Free and Standard, Atlassian uses in-app data by default from August 17, 2026 unless an admin opts out, and metadata is always contributed below Enterprise.
- Confluence's own keyword search is the most frequent complaint in public accounts, raised in 14, one more than AI placed on every page. Rovo answers only as well as the pages behind it.
- Users report summaries that invent meetings or definitions, and individuals cannot turn off the AI placed across pages.
- Extra usage past the pooled allowance is on by default and bills from December 3, 2026; full Rovo needs Cloud, and Data Center reaches end of life on March 28, 2029.
- PromptArmor reported on August 5, 2026 that Rovo's URL retrieval tool can send Jira and Confluence data to an attacker, even with web search turned off. Atlassian's advisories page and monthly bulletins carried no Rovo entry when GILD checked on October 25, 2026.
Implementation reality
Settle the data terms first
Check the data contribution setting under Security in Atlassian Administration: Free and Standard contribute in-app data by default, Premium and Enterprise do not, and only Enterprise can stop metadata contribution. Pin data residency for Confluence, and on Enterprise decide whether to request Atlassian-hosted LLMs only.
Clean the spaces people ask about
Merge duplicate project pages, archive stale ones, and name owners for the ten spaces that answer most questions. Test 30 or more real questions in Rovo Search and Chat before and after, since answers follow the pages and permissions behind them.
Connect apps on purpose
Turn on admin-managed connectors one at a time and set a blocklist for Google Drive and SharePoint, because each connector indexes the whole workspace. Indexed objects are capped at 100, 250, or 625 per user by plan.
Set agent and credit rules
Limit agent creation to named groups in Studio, verify shared agents, and set a spending cap on extra usage, which bills at US$10 per 1,000 credits from December 3, 2026. Quick answers cost 10 credits a message; one developer measured Think deeper replies at 65 and 86. He models 200 Jira Standard users asking one quick question a working day at about US$370 a month in overage. Review the Platform usage dashboard by app and user each month.
What to measure in your pilot
- GILD found no same-question test of Rovo, Glean, and Microsoft 365 Copilot; run 40 cross-source questions through each as one user, and let a 15-point lead in cited correct answers decide.
- Log extra Rovo credits weekly by app and user after December 3, 2026; set the cap from week four, and narrow agent access where a group's overage passes its seat cost.
- Check Atlassian's security advisories monthly for a fix to the URL retrieval flaw, and widen Rovo beyond the pilot groups only once one ships.
Sources
- Official documentation
- 17
- Public source
- 3
- Confluence pricing
- Atlassian: Rovo plans and trial
- Atlassian Support: How Rovo credits work
- Atlassian Support: Rovo data, privacy, and usage guidelines
- Atlassian: Available Rovo connectors
- Atlassian Support: Data contribution settings
- Atlassian Support: Understand data residency
- Atlassian Trust Center: Rovo AI security and trust
- Atlassian Support: Manage Rovo access
- Atlassian Support: Rovo agent permissions and governance
- Atlassian Support: What is Rovo Studio?
- Atlassian Support: Get started with the Atlassian MCP server
- Atlassian Support: Compare Rovo Chat reasoning modes
- Rovo in Confluence: AI features
- Atlassian: Data Center end of life
- Atlassian Trust Center: Security advisories and monthly security bulletins, January to October 2026
- Atlassian Engineering: Enhancing Rovo Chat with a hybrid LLM approach
- Mihai Perdum on DEV: Rovo credits per user, cost and usage per action, measured (Oct 15, 2026)
- PromptArmor: Atlassian Rovo exfiltrates data, bypassing controls (Aug 5, 2026)
- The Hacker News: Atlassian Rovo can be tricked into sending Jira and Confluence data to attackers (Aug 8, 2026)