Search, chat, and agents that read your whole estate.
Rovo provides search, chat, and agents across Atlassian and connected third-party systems, reading from the Teamwork Graph rather than from one product at a time. Our work is scoping what it can reach, defining ownership for agents, and the permission work underneath.
Rovo works across the Atlassian estate and whatever is connected to it. Its reach is your permission model, which is why the governance work sits underneath rather than inside it.
What it is
Rovo provides search, chat, and agents across Atlassian and connected third-party systems, reading from the Teamwork Graph rather than from one product at a time.
It is for organizations that already hold it in an entitlement, which is most of them, and have not yet asked what it can see.
What it does
It reads across the estate
Which is what makes the answers useful and what makes the permission model the control.
Agents act within existing permissions
Scope is inherited, so an agent is exactly as bounded as the identity behind it.
It is usually already included
Held in an entitlement and switched on, which means the governance decision is often retrospective.
Where it fits
L4, agents and automation, with its control surface at L1. Rovo answers from what the asking user may already access. That makes it useful, and it makes an estate with a decade of accumulated permissions uncomfortable in a specific and productive way.
What we do with it
Permission review before rollout
Establishing what it can actually reach, which is a question about your groups rather than about the product.
Usage policy and guardrails
What may be used where, what must escalate, and what evidence is retained.
Change control for what it touches
Where output becomes an action, the approval model has to exist first.
Custom agents where native stops
Built on Forge, inside the same permission model.
Where it earns its place
An organization asked what it can see
The answer is a permission model, and it either exists or it gets written during the review.
An estate with inherited space permissions
Assistive search is the fastest way to find out what people can actually open.
A team wanting agents without a programme
One scoped agent against one clean process beats a broad rollout nobody can evaluate.
Proof
Monthly active users on Rovo, which makes the capability table stakes and the governance the differentiator.
Atlassian Q2 FY26 shareholder letter.
AI Innovator Finalist, 2026
Atlassian Partner Awards, 2026
Questions we get
Can we turn it off?
Is this the same as Rovo Dev?
Licensing
Rovo capacity is metered against your entitlement, so consumption is worth tracking during the year rather than reconciling at renewal. That reconciliation sits with the rest of the estate in licensing and renewals.