實測封鎖 Jira 的 Rovo：5 個 AI 入口仍在，Chat 仍能摘要工單

To disable Rovo in Jira, an organization admin adds Jira to the blocklist on the Rovo access page in Atlassian Administration. We did exactly that on our own test org on 22 October 2026, and two minutes later five AI entry points had gone from Jira. Five others were still there, though. And when we asked Rovo Chat to summarise a Jira work item, with Jira still on the blocklist, it summarised it correctly, three times over half an hour.

So "disable" means less than most admins hope. The block turns off the AI features that belong to Jira itself. The features Jira shares with its sibling apps on the same site (Atlassian calls them the Jira family: Jira Service Management, Product Discovery, Customer Service Management and Assets) keep running until all of those are blocked too. Chat and Rovo's AI-powered search are among them. Atlassian's own doc says so in one sentence that's easy to read past.

The question comes up constantly. "How to disable Rovo" on the Atlassian Community has 33,130 views, and the accepted answer from an Atlassian staff member, quoting the docs, says "No, you can't turn off Rovo." Another thread, "How can disable ROVO?", has 16,489. People asking aren't anti-AI cranks, either. A healthcare admin wrote "We are healthcare and so haven't activated AI as it's not currently HIPAA compliant. And yet, today, I see Rovo is active and can't turn it off."

My take, after going through the screenshots: blocking Rovo is a policy tool. If your reason is a written AI policy or a data question, block all the apps on the site and expect a couple of buttons to hang around. If your reason is the Rovo bill that starts on 3 December, blocking is the wrong lever, because the seats cost the same whether Rovo is blocked or not. A spending cap on extra usage does that job.

What we found when we blocked Rovo for Jira, then Confluence, then everything

We tested on wolfaenpak, our Atlassian test org, as an org admin. Jira and Confluence are on Premium there, and so is the Service Collection. Mihai's test harness (a script that drives a real browser) loaded the pages with a fresh browser profile for each check, so nothing cached could fool us, and it saved a screenshot plus all the button labels on the page each time. By "entry point" I mean any button or menu item that starts a Rovo or AI feature. We tracked 10 in Jira: 9 on a work item (TPP-41, a story in a test project) and Ask AI in issue search.

1. Blocking Jira took effect in under 2 minutes. The flag says "It may take a few minutes to take effect", and the doc says changes "do not take immediate effect". The first check, about 2 minutes after the click, already showed the final state, and nothing more changed at 5, 10, 20 or 30 minutes.
2. 5 of the 10 entry points went away. The Improve button and its whole menu, Summarize, Agents, the AI reply suggestions under comments, and the Jira quick actions inside the chat panel.
3. 5 stayed. Ask Rovo in the top bar, the floating chat button, Ask AI in issue search, and in the description editor both the Ask Rovo toolbar button and the Ask Rovo item in the slash menu.
4. Rovo Chat still read the blocked Jira data. About 14, 24 and 34 minutes after the block it answered "Summarize this work item in one sentence" with a correct summary of TPP-41.
5. Blocking Confluence as well cleaned up Confluence only. Its top-bar Ask Rovo and the editor's Write button went, along with Remix page and Listen. Chat and Ask AI kept working in Jira.
6. Chat and Ask AI stopped only after we blocked the last five apps in one go. Those were Jira Service Management, Customer Service Management, Goals, Projects and Studio. We didn't block them one by one, so we can't say which of them held Chat up. Atlassian's doc points at the Jira-family apps, which on our site means JSM and CSM.
7. "Blocked" still left 2 buttons on screen. The Jira editor's Ask Rovo and the Confluence floating button stayed, and clicking them opened a prompt to "Activate Atlassian Intelligence features for your users".
8. Restoring was just as fast. We removed all seven rows between 08:47 and 08:49 UTC, and all the entry points were back by the 08:51 check.

How to block Rovo access for Jira and Confluence

You need to be an organization admin. Atlassian's doc lists this page for paid plans only (Standard and up), and Free plans get no Rovo credits; we couldn't check what a Free-only org sees.

1. Open Atlassian Administration at admin.atlassian.com and pick your organization.
2. In the sidebar, open Rovo, then Rovo access. Our org showed those labels on 22 October. Atlassian's current doc calls the same place "AI and Rovo, then Access", and the old Atlassian Intelligence address in Administration redirected here, so look for either name.
3. Select Add app. A list opens with the apps that have Rovo, one row per app per site, with its plan.
4. Tick the apps you want to block and select Block access.

There's no confirmation step. The click applies straight away and you get a flag: "You blocked access to Rovo for 1 app. It may take a few minutes to take effect." On our org a "Rovo Admin Confidence Survey" popped up over the page right after each block, which felt a bit cheeky. To undo it, use Remove on the app's row. That one asks you to confirm.

Two things in that list are easy to miss. First, it mixes sites. Our picker also listed the apps of our other site, leanzero-demo, marked Sandbox, right next to the wolfaenpak rows. The tick box in the header selects all of them, so read the site column before you click. Second, Studio (Atlassian's builder for agents and automations) has its own row, and on our org that row belongs to the organization rather than to one site. So if you run more than one site, blocking Studio probably reaches all of them. Goals and Projects have their own rows too.

Blocking Rovo for a group is Enterprise only

On Standard and Premium the blocklist is per app and that's it. Atlassian's Enterprise doc describes a newer screen where you can allow or block Rovo per user group as well: with default access on, a user loses Rovo if either their app or their group is blocked. Atlassian says Enterprise orgs may see either the old blocklist or the new screen while it rolls out. We're on Premium, so we couldn't test that one.

A switch for single users doesn't exist on any plan yet. AI-930, "Ability to enable/disable AI for specific users", has 476 votes and the status In Progress (read 22 October 2026). It hasn't shipped yet.

What stays on after you block Rovo for Jira: Rovo Chat, Ask AI and 3 more

Atlassian's doc "Manage Rovo access" (updated 20 October 2026) carries the rule that explains most of this: "Certain AI features common across Jira family apps, such as Rovo AI-powered Search, Chat, and Create with Rovo, remain available as long as any Jira app on that site still has Rovo enabled."

On our site JSM is a Jira-family app (so is Customer Service Management), so blocking Jira alone left Chat and Ask AI running for the whole site.

If your reason for blocking is data, this is the screenshot to look at. Most admins would assume a blocked app is off for Chat too. The Rovo access page itself says "Rovo can still access data for the apps you block, but external AI models don't have access to that data." What we got was an AI-written summary of a blocked app's work item, and the screen doesn't say which model wrote it. Connected third-party tools aren't part of the switch either: Atlassian's feature table keeps Rovo Search and its connectors available without AI, and disconnecting a connector is a separate step that Atlassian says takes 48 hours to complete for most apps. If you're in healthcare, Atlassian keeps a separate page on using Rovo in HIPAA organizations, and it lists several Rovo tools as not HIPAA-compliant yet. So test it on your own site before you tell anyone Jira is "off".

Ask AI in issue search behaved the same way. With Jira blocked it still turned "stories in TPP created this year" into a working query.

The last two survivors are in the description editor: its Ask Rovo toolbar button and the slash-menu item "Ask Rovo" (subtitle "Collaborate with AI"). Both stayed through all four phases of the test. During the Jira-only phase our automated click didn't open the prompt, so whether they still worked then is unknown. I only know they were on screen.

Blocking every app on the site: what finally goes, and the 2 buttons that don't

We added Confluence to the blocklist at 08:01 UTC. By the 08:03 check Confluence had lost its top-bar Ask Rovo, Remix page, Listen, the editor's Write button, Suggest title and the slash-menu Ask Rovo. Jira didn't notice: at about 08:16 Chat still summarised TPP-41, because JSM and the other apps still had Rovo.

At 08:24 we blocked everything left on the site: Jira Service Management, Customer Service Management, Goals, Projects and Studio. By 08:26 the top-bar Ask Rovo was gone everywhere, the floating chat button had left Jira, Chat couldn't be opened, and Ask AI had disappeared from issue search.

Two things stayed for the full 20 minutes we watched. The Jira editor still showed its Ask Rovo button and slash item, and the Confluence floating button was still in the corner. Clicking either one opened an admin-only prompt like this one.

The message says it's "only visible to org admins". We tested as an org admin and didn't log in as a regular user, so we can't confirm what your users see there. A suggestion ticket, ROVO-596, describes exactly this split (admins still see entry points, users don't) and asks for a strict mode that hides them for everyone. It has 10 votes.

Search also kept working with everything blocked, as Atlassian's Trust page says it will: "non-AI powered Rovo features, such as Rovo Search, cannot be disabled." We saw no AI answers in search at any point, even before the block, so this test says nothing about AI answers in search.

Disable Atlassian Intelligence or block Rovo access: it's the same switch now

If you've got an old runbook that says "deactivate Atlassian Intelligence", it points at this page. On our org the old /atlassian-intelligence address in Atlassian Administration redirected to Rovo access, and Atlassian's old "activate Atlassian Intelligence" doc now redirects to "Manage Rovo access". The doc's own note says "All references to Rovo in this documentation include Rovo AI-enabled features and AI features."

That rename explains why Community answers disagree so much. Over the last eighteen months the accepted answers have said "deactivate AI in any of your apps" and later "Apps > AI settings > AI-enabled apps". A September 2026 answer says "Rovo > Rovo access". The doc now says "AI and Rovo, then Access". We couldn't find a separate AI switch inside Jira or Confluence administration on our site either.

The Ask Rovo button: can you hide it without blocking Rovo?

No. ROVO-741 asks for exactly that, "Hide or disable the in-product Ask Rovo floating button without turning off all Rovo/AI features for the app", and it has 68 votes. It's still Gathering Interest. Its own text says "The only supported way to remove the button is to block Rovo for that app at the organization level." In our test, blocking Jira alone didn't even remove it from Jira.

Can you turn off specific Rovo features? Not yet

No, not one at a time either. ROVO-369 asks to turn off things like Deep Research while keeping the rest, and has 17 votes. JRACLOUD-98103 reports the Rovo icon and Improve description still showing on the create screen and in comments after a Jira block. We saw half of that: the Improve menu on the work item went in 2 minutes, but the description editor's Ask Rovo button stayed. We didn't open the create screen. The Community fix people trade instead is a browser userscript or stylesheet that hides the buttons. That only changes what one person sees in one browser, so it's no help for policy.

Blocking Rovo doesn't lower your seat price

Send this section to whoever owns your Atlassian budget. Rovo comes with your Jira and Confluence subscription: Atlassian's September 2025 billing article says "you will not be billed separately for Rovo", and its usage-based pricing FAQ says seats don't change under the new pricing ("You continue paying for seats as before"). No Atlassian page we read says blocking Rovo lowers the licence price, and we found no paid plan without Rovo.

The new money is extra usage. Rovo chat messages, agent runs and most AI feature calls already spend Rovo credits (search, definitions and summaries are free). Each user brings a monthly allowance into one shared pool: 25 credits per user on Standard, 70 on Premium and 150 on Enterprise, for each of Jira and Confluence. Service Collection and Teamwork Collection users bring ten times that, 700 each on Premium. What changes on 3 December 2026 is that credits past the pool start costing $0.01 each, and unused ones never roll over. Atlassian's credits doc says extra usage is "enabled by default"; one of its pricing FAQs says it "requires opt-in". Check your own org before you rely on either. For a company with Jira and Confluence the pool works out like this.

The 10-credit and 310-credit figures come from our own org's Rovo credits export: a quick chat answer cost 10 credits, and our longest multi-step chat run cost 310. We wrote up the per-action costs in Rovo credits per user, and the full 2027 sums for 50, 200 and 500 seats in the usage-based pricing budget.

So a 200-person Premium company can run about 2,800 quick chats a month before a cent of overage. If what scares you is a surprise invoice, set a spending limit on extra usage, or turn extra usage off. Turning it off "takes effect immediately", according to Atlassian, and Rovo keeps working until the pool runs out. The steps are in our Rovo usage limit tutorial. Blocking Rovo for one app to save money mostly hides buttons: in our test Chat kept answering through the apps we hadn't blocked, and Atlassian bills each Chat message as an event.

We didn't measure whether credits still move while an app is blocked. A customer on JRACLOUD-98103 reported on 5 October that with Jira and Confluence both blocked "Rovo still works in Jira, and credits are used". Our Chat test fits that, but we didn't read the meter during the block, so it stays a customer report until someone measures it.

What I'd do in your seat

If you have an AI policy that says no Rovo, block all the apps on the site (Jira, Confluence, JSM, Customer Service Management, Goals, Projects, Studio, whatever your picker lists for that site), check the site column, and then open a work item and a Confluence page yourself after two minutes. Tell your users that a couple of entry points may stay on screen and open an admin prompt when clicked, and that search is not part of the switch. Content Rovo already wrote stays where it is: the doc says "Any content previously generated by Rovo will remain."

If you want Rovo off for Jira only, know that you're turning off the Jira-specific buttons and agents and leaving Chat and Ask AI running for as long as JSM or any other Jira-family app on that site keeps Rovo.

If your worry is cost, leave Rovo on and put a cap on extra usage before 3 December. A cap is the setting that actually touches the invoice.

And if you need it per person, vote on AI-930 and wait. Enterprise is getting group-level blocking; nobody has a per-user switch yet.

I'm curious how this went on your sites. If you've blocked Rovo for one app, did your users notice anything was gone, or did they just keep using Chat? Tell me in the comments under this post. I'd especially like to hear from anyone who checked the credits meter while an app was blocked.

Originally published on leanzero.net. More Atlassian, Forge and local-AI write-ups at leanzero.net/blog, and if you're planning a migration or a Forge app, that's what we do: leanzero.net/services.