Hello, Team!
With our research we found that it’s not trivial, because at the moment Rovo (from Atlassian) credits overconsumption doesn’t trigger severe immediate consequences — but there are important implications and potential risks, especially looking ahead. What happens (or what might happen) if the team overconsumes Rovo credits?
Thanks in advance
Hi @Sales SoftGile - welcome to the Community,
the only published information is this: Rovo usage quota | Rovo | Atlassian Support
I've checked Partner ressouces as well, there is nothing more than that. So: Aside from the info that there will be credits, there is nothing on what happens on overconsumption, how the credits are calculated in detail or what extra credits will cost.
There probably will be a generous grey area, but again. Nothing official on that yet. The usage quotas won't be enforced before Admins get full insights into usage - and that view is not provided yet. I am assuming it will be in late Q1/26
@Sales SoftGile I second what @Rebekka Heilmann _viadee_ says and add: Today, if an org overconsumes Rovo credits, there’s no immediate penalty or service shutdown. Once credits are exhausted, Rovo features may be throttled, limited, or paused for affected users until the next reset or additional credits are assigned. Atlassian has indicated that enforcement and billing behavior may evolve as Rovo moves toward general availability, so the longer-term risk is tighter limits or paid overages. Best practice is to monitor usage in Admin Hub and scope access intentionally.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.