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; } } }

Double Clicking on Rovo Usage Quotas - Update to give you more flexibility and control

Danielle Dannenberg

At Team '25, we announced that Rovo is now included in all paid Jira, Confluence, Jira Service Management, and Teamwork Collection subscriptions, each with built-in usage quotas. We were overwhelmed with excitement and feedback, and we've been listening to you. Today, we're sharing an update on some recent changes we've made to provide you more clarity, control, and value, and make your adoption journey smoother and more predictable.

Why do we have usage quotas?

This enables us to offer you the most advanced models and AI capabilities to accelerate teamwork and automate your workflows while providing you the flexibility to dial up and down your usage.

What to know about Rovo’s usage quotas

Commitment to predictable billing to give you more certainty

All customers will receive a notice by email a minimum of 90 days before any enforcement of Rovo’s usage quotas and by that time, we will rollout admin controls (more on this below) so you can monitor and manage usage with confidence.

When we start enforcing usage quotas, customers will have the option to purchase additional credits for usage beyond what’s included in their subscriptions. If you wish to buy more credits, you’ll be able to pre-pay in advance or pay-as-you-go, on a monthly basis and pricing will be published 90 days prior to enforcement. If you do not purchase additional credits, usage will be limited to what’s included in your plans. Our tools intend to help you forecast predicted usage so you can make the choice that’s best for your organization. No surprise billing here!

More admin controls for managing usage

We’re prioritizing the delivery of dashboards, notice periods, governance, and controls before enforcing Rovo’s usage quotas — especially for Rovo Agents – so you can view and adjust the monthly usage for your organization.

Types of admin controls in the works:

View projected usage towards your included quota
Manage who can create a Rovo Agent
Admin authority to manage and delete Agents
Manage number of Chat and Agent requests per user
Enhanced tools to manage, optimize, and disable automation rules that use Rovo Agents
Quota management controls to select which data is ingested by Rovo Connectors, such as blocklists, allowlists, and time-based ingestion

Giving you more flexibility with increased quotas

We want you to have the flexibility to use as much Rovo goodness as your organization needs. To do this, we’ve recently made some stellar improvements to our efficiency that have allowed us to include more usage in all Premium and Enterprise subscriptions, making it easier for you to experiment and scale without worrying about hitting limits too quickly.

What's new:

Indexed objects - We are giving you 5x more indexed objects from external platforms. An object may be a document (Sharepoint, Google Drive), a chat thread (Slack, Teams), a webpage (Custom website), or any other single indexable item from any of the Rovo connectors. For example, our Enterprise Teamwork Collection subscription now includes 6,250 indexed objects per user.
AI Credits - We are giving you 2x more AI credits to engage with Rovo’s most complex features. AI Credits are a unit of consumption based on the usage of Rovo features, like Rovo Chat and Rovo Agent requests.

The updated usage quotas are now live. Consumption rates for new features will be added as they are made generally available.

A frictionless path to adopting more AI-powered features

Reasonable use of core AI features — like summarization, smart answers in Rovo Search, and issue work breakdown — will not consume AI credits. Currently, this applies to all non-Chat/Agent features that exist today, so you can confidently use these tools without worrying about unexpected charges within the Atlassian Acceptable Use Policy. We will notify you if we add additional AI features that are subject to AI Credits.

Thank you for your partnership and feedback. If you have questions or want to learn more, check out our updated usage quota documentation or comment below! We’ll be checking this post and responding to any questions or comments.

Comments

Josh

@Danielle Dannenberg thank you for the information here! This answers a lot of our lingering questions.

Raef Makrai

@Josh No problem 😊 We're glad the information was helpful and answered your questions!

Dr Valeri Colon (Connect Centric)

Thanks for this detailed update—really helpful to see how usage quotas and admin controls are evolving. It’s great to see Atlassian move toward a consumption-based pricing model, which aligns with where the AI industry is headed. This approach supports flexibility, promotes sustainable and responsible AI use, and helps organizations scale with clarity. Also, thank you for continually being transparent about pricing—it really builds trust!

Raef Makrai

@Dr Valeri Colon _Connect Centric_ Thank you! We really appreciate your feedback—and couldn’t agree more about flexibility and responsible AI use 🙏

Brita Moorus

Thanks for the clear update - really appreciate the transparency and the direction this is heading ✨

Adam England_m6h7pq

Appreciate the baseline clarity, but this still remains highly ambiguous, and I can't plan to roll out features that may blow our Jira budget out the water.

The usage limits seem really low on the outset, and you haven't released any ideas of costs with the tiering. I'm evaluating the AI suite of tools now and can see a huge benefit to my organization, but not when I have to run back and say it's going to be a massive bill, and that's AFTER upgrading to Premium. We still have a sour taste in our mouth from the Automations will forever be free pivot when you started introducing caps.

I can see comments on trust here, and I would challenge this is anything but trustworthy. Credits, are we talking ChatGPT style pricing, or are you going super aggressive where it prices your smaller customers out?

Bring me sunshine, Atlassian! Help us out here, we want to use your tools, but our stakeholders don't want surprises.

Chris Price_zv7r3w

Thanks for this update, it's great to see so many useful admin features in the pipeline. Is there any timeline available for when the usage dashboard will be rolled out? Very eager to see this one in particular 😊

John Dunkelberg

Sounds like it's making progress. We're looking forward to completion of usage controls so we don't have unbounded exposure to costs, at which point we'll be able to look at adoption.

Peter Norris

I completely agree with @John Dunkelberg's comment.

@Danielle Dannenberg we cannot turn on Rovo until we have a mechanism to ensure that we don't get an unplanned bill at the end of the month. A report that tracks usage through the month is useful, but we need an absolute guarantee via some configuration switch that Rovo will be turned off, should we hit our limit.

Do you know when this will be rolled out?

Ariel Kauan_e6cjkt

Do we have any updates on that?

I can't ‘sell’ Rovo if I don't have any metrics.

Fazila Ashraf

Hi @Danielle Dannenberg

Where can we find the current consumption trend of our AI credits and indexed objects?

Renata Bianchi

@Danielle Dannenberg , @Raef Makrai ,

I've been using Rovo quite a bit lately and noticed a drop in its performance. I'm trying to check my current consumption but haven’t been able to locate it. Could you please let me know where I can find that information?

Thanks in advance!

Renata Bianchi

Rovo has just answered me:
You do not need to worry about exceeding your Rovo quota at this time, as quotas are not enforced and there is no current dashboard for individual usage. Atlassian will notify you well in advance before any enforcement or charges begin.

Adam England_m6h7pq

@Danielle Dannenberg

I'm still lost with this - I can't roll anything out yet, the 90 days "warning" isn't going to fly. It's incredibly concerning you're wanting customers to run riot and find value in this, only to pull the rug.

Please speak to your product team or anyone who can give your customers the reassurance. Right now we're just waiting on what pain Atlassian might inflict later, and it's massively damaging to your reputation with our stakeholders.

恩田翔

While there are some comments on this, it's difficult to explain usage in situations where budget control is challenging.

Therefore, I have submitted a ticket as an improvement request to set system-level upper limits.

If you are a user facing similar issues, we would appreciate your vote.

https://jira.atlassian.com/browse/ROVO-532

Welcome!

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

Quick Links

Find more posts tagged with

rovo-atlassian-intelligence

rovo