Block Rovo access on a per-user basis?

[Mau Jimenez]

Hello team,

We have an organization with Premium membership in which we have several users, one of our biggest concerns is the amount of tokens each user is consuming. 

Since we will not have data available to determine the token signature of each user until later this year (with DX's acquisition) we want to block either Rovo for everyone but a bunch of people (whitelisting) or block Rovo for a specific ser of people (blacklisting).

Is this something that is currently available? Or would it be available in the future? I don't remember seeing anything about it on this year's Team26' event so I'm curious about it.

Thanks in advance and best regards!

[Rebekka Heilmann _viadee_]

I second @Jason Krewson and @Arkadiusz Wroblewski 

I have tried a workaround with using IP Whitelisting on the Rovo App. That sort of works, if you can give the whitelisted users access via the whitelisted IP.

But: Everyone will still see Rovo in the UI, but will get an error message in the Chat/as soon as they invoke any Rovo feature.

Definitely not ideal but something that is available with Premium subscriptions already.

[Arkadiusz Wroblewski]

Hello @Mau Jimenez 

Per-user blocking is not generally available. App-level blocking is available. Group-level control exists for Enterprise/new experience/beta, but not as a universal Premium per-user control.

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

Best,

Arek 🤠 

[Mau Jimenez]

Hello @Arkadiusz Wroblewski

Thanks for your swift response! We are glad to see Atlassian’s commitment to improving user controls and that the feature is already in a Beta for Enterprise users.

We have started watching the quoted ticket, however, we do have a quick question. Do you know if these features are something that could be available for Premium/Standard users? Or if Atlassian has anything on the works as of now? Or if there could be any third party apps on the Marketplace that could help us to establish a tighter control on user’s accesses?

Thanks in advance and best regards!

[Rebekka Heilmann _viadee_]

My 2 cents: I don't think Atlassian will deliver the user level control to Standard/Premium any time soon as they WANT us to consume more credits than we have available to push for Collections or additional credit purchases.

[Arkadiusz Wroblewski]

@Rebekka Heilmann _viadee_ Agree.

[Jason Krewson]

Hey @Mau Jimenez !

I will send you several references, I hope they help.

First off, Rovo Access is all or nothing, you can find more details about this at Manage Rovo Access .

Another thing to note is that currently there is no billing for Rovo and Atlassian will give you at least a 90 day notice requiring opt in if they do start to bill. Good reference for this is Rovo usage allowance .

And there is reporting, you can go to Admin.Atlassian.com > Rovo > Rovo Insights, this reference explains this well, Gain insights into Rovo AI activity . Another place you can see good information on usage is Studio > Insights, this shows agent usage.

 I'm not sure if Atlassian will add Rovo access by user in the future or not. 

[Mau Jimenez]

Hello Jason,

First of all, thank you so much for your quick and detailed response, I really appreciate it.

I understand your points, and unfortunately they also highlight two key limitations that Atlassian currently cannot address for us:

1. Token allowance visibility and control
   At the moment, our organization has a shared token allowance across multiple sites under the same Org. While the overall allowance may seem large, consumption can grow very quickly — especially when users start indexing external sources through connectors such as Google Drive, GitHub, and others.

2. Granular usage insights
   The current Rovo reporting provides a helpful high-level overview of adoption and activity, but it lacks the level of detail we need for governance and capacity planning. For example, we currently cannot identify which users consume the most tokens, how many tokens are used per query, or which connectors are driving the highest usage.

I believe features such as user-level access controls (whitelisting/blacklisting) and more detailed usage analytics would add significant value, especially as Rovo continues evolving into a strong competitor in the AI workspace space.

Regardless, thank you again for sharing these references. I’ll share this information with our internal team so we can better prepare for future changes and potential billing updates.

Best regards!

[Jason Krewson]

Anytime thanks!