nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Rovo Trends: What permissions are required?

Chris Green

I’m looking to access Rovo Trends within admin.atlassian.com to monitor Rovo adoption and agent usage.

The documentation lists Organization admin as the required role. Can anyone confirm whether that’s currently the only way to access these dashboards, or whether a more limited role or read-only permission is available?

It would be helpful to give those responsible for Rovo adoption and reporting visibility into these metrics without requiring full organization administration access.

Related: Rovo monitoring and dashboards

Accepted answers

Matthew Sinclair

What you saw in the documentation is truth.

Org Admins only.

In the future its possible they may provide some insights in the Jira-Admin level or possilby Site-Admin level - but for the time being that's all we got.

New features/toys are headed our way - who knows - maybe we'll get something in API or perhaps Atlassian Analytics per Teamwork Graph.

All comments

Matthew Sinclair

What you saw in the documentation is truth.

Org Admins only.

Josh

As of the current admin experience, Organization admin is still the gate for Rovo Trends in admin.atlassian.com. There is not a separate “Rovo analyst” or read-only org role that unlocks those dashboards today.

What teams usually do in the meantime:

Have an org admin export / screenshot the Trends views on a schedule for the adoption owners, or
Use product-level signals you can share without org admin (site admin reports, Rovo usage where exposed in the product UI, support-provided usage extracts).

Worth adding a short comment on the Atlassian feedback ticket / Community wish-list that you need delegated read access for adoption owners — that request comes up a lot. If Atlassian has added a finer permission since the last docs update, an org admin can confirm under admin.atlassian.com → Rovo → Trends whether a non-admin account can open the URL at all (usually they cannot).

Arkadiusz Wroblewski

Hello @Chris Green

Adding to Matthew’s answer, there is a narrower option for individual agent usage: an agent’s owner, managers and editors can view Studio → Agents → select the agent → Insights.

This shows average daily users and total conversations, without requiring organization admin access. Atlassian documents it here, currently in open beta.

That could help people who already manage those agents, but it doesn’t provide read-only access to organization-wide Rovo Trends. Those dashboards still require an organization admin.

Best,

Arek🤠

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-service-management

roles-and-permissions

rovo