Rovo turns on automatically for Standard, Premium, and Enterprise Cloud plans, so on those plans it already answers from your spaces. Extra usage billing starts on December 3, 2026. Before then, settle data terms, clean the spaces people ask about, connect only the apps you need, and set credit and agent rules.
When you need this
- Your organization is on a paid Confluence or Jira Cloud plan, so Rovo is already active or about to be.
- Security or legal asks what Atlassian does with your pages now that the data contribution settings apply from August 17, 2026.
- Teams have started building agents in Studio and nobody owns the list.
Evaluation criteria
Setup: who gets Rovo, and on which plan
Which apps and plans in your organization include Rovo, and who has no seat?
Look forCheck each user's plan. Standard, Premium, and Enterprise Cloud plans for Jira, Confluence, or Jira Service Management include Rovo Search, Chat, Studio, and agents. Assign an organization admin on a verified business domain. For people without a Jira or Confluence seat, assess Rovo Standard, which is in beta. Decide whether to block Rovo in any app.
Governance: data terms settled first
Will Atlassian use your in-app data, and where will Rovo data live?
Look forCheck data contribution under Security in Atlassian Administration. From August 17, 2026, Free and Standard default to contributing in-app data, and Premium and Enterprise default to off. In April 2026, admins on Hacker News reported the setting missing from their console, so confirm it appears before you rely on it. Pin Confluence data residency. On Enterprise, decide whether to request Atlassian-hosted LLMs only.
Content: clean the spaces people ask about
Will the first Rovo answers come from current pages or from duplicates and drafts?
Look forMerge duplicate project pages, archive stale ones, and name an owner for each space that answers the most questions. One PeerSpot reviewer gets fifteen pages back for one project. A Reddit user gets good Rovo-drafted stories only when the Confluence documentation behind them is solid.
Connectors: index only what you mean to
Which third-party apps will Rovo index, and how much of each?
Look forTurn on admin-managed connectors one at a time. Set a blocklist for Google Drive and SharePoint, because each connector indexes the whole workspace. Confluence plans cap indexed objects at 100, 250, or 625 per user. Atlassian deletes indexed content within 30 days of a disconnect.
Agents: who builds, who sees
Who can create agents in Studio, and which ones are shared company-wide?
Look forIn Studio settings, limit agent creation to named groups, up to 10. Name an owner and managers for each shared agent, and verify the agents meant for everyone. An agent acts with the permissions of the person using it, and an automation call acts with the access of the user who connected it.
Cost control: limits before December 3
What happens to the bill when the pooled allowance runs out?
Look forCap extra usage, which defaults to on and bills at US$10 per 1,000 credits. Send the 80% and 100% allowance alerts to admins. Review Platform usage by app and user every month.
Questions to ask vendors
- Which data contribution defaults apply to our highest active plan, including any trials?
- Do we need Atlassian-hosted LLMs only, and is our organization on Enterprise to request it?
- Which connectors will index whole drives, and which teams own the blocklist?
- What spending cap and alert recipients will we set before December 3, 2026?
Red flags
- Leaving the data contribution setting at its default on a Standard plan without a decision on record.
- Turning on Google Drive or SharePoint connectors with no blocklist.
- Letting every user publish agents company-wide with no owner or verification.
- Reaching December 3, 2026 with extra usage on and no spending cap.
Products in this piece
Sources
- Official documentation
- 10
- Public source
- 3
- Atlassian: Rovo plans and trial
- Atlassian Support: What is Rovo Standard?
- Atlassian Support: Manage Rovo access
- Atlassian Support: Data contribution settings
- Atlassian Support: Understand data residency
- Atlassian Trust Center: Rovo AI security and trust
- Atlassian Support: Rovo data, privacy, and usage guidelines
- Confluence pricing
- Atlassian Support: Rovo agent permissions and governance
- Atlassian Support: How Rovo credits work
- PeerSpot review by Patrik Rosendahl: duplicate pages and search (Mar 19, 2026)
- Reddit r/jira comment on Rovo drafting stories from solid Confluence docs (Apr 11, 2026)
- Hacker News comment on the data contribution setting missing from admin (Apr 20, 2026)