Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Allow individual users to disable/hide Rovo AI features without admin involvement

Claus Praefcke
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 20, 2026

Summary

As a non-admin user, I would like the option to disable or hide Rovo AI (Atlassian Intelligence) features in my Jira and Confluence interface, without needing to contact an organization administrator.

Problem

Currently, Rovo AI features can only be disabled at the organization level by an admin — either for entire apps or (on Enterprise plans) for specific user groups. There is no way for an individual user to opt out. This means users who prefer not to use AI features must either ignore them in the interface or request admin action, which may not always be practical — especially in large organizations.

Proposed solution

Add a per-user setting (e.g., under Personal Settings or Profile Preferences) that allows individual users to:

  • Hide or disable Rovo Chat and AI-powered suggestions in Jira and Confluence

  • Opt out of AI-generated summaries, recommendations, and other AI-driven UI elements

  • Re-enable AI features at any time if they change their mind

This would give users control over their own experience without affecting other team members or requiring admin involvement.

Why this matters

  • Not every user finds AI features helpful for their workflow

  • Reducing UI clutter improves focus and productivity for users who don't use AI

  • It respects individual user preferences while keeping AI available for those who want it

  • It reduces unnecessary admin overhead for what is essentially a personal preference

Who benefits

Any Jira or Confluence user who prefers to work without AI features, across all plan tiers (Standard, Premium, Enterprise).

1 answer

1 vote
Nikola Perisic
Community Champion
July 20, 2026

Hello @Claus Praefcke 

There is a reason why only organization admins can do this. They are the ones with the highest privileges and they control all sites under an organization. Having any user disabling it would disrupt the current governance that is being held by org admins. I don't believe that this will happen in the future. Besides, you probably do have an org admin and they are the ones who can disable the Rovo.

They can also choose which users can access which agents based on the roles:

  • Manager - can delete and edit agents; can invite people
  • Editor - can only edit agents; cannot invite people

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events