Hello,
I have read the available articles regarding Rovo but could not find answers to the following questions.
As I understand, Rovo itself is not billed directly, except through AI credit consumption. I would like to better understand how we can limit these costs and ensure that only predefined users are allowed to consume credits.
More specifically:
Is it possible to limit the use of Rovo to specific users only (to better control costs)?
Can I select which users are allowed to consume credits?
Is it possible to enable Rovo only within automations, without providing access to the Rovo chat feature?
Thank you for your clarification and guidance.
Best regards,
Jean-Marc
Or rather: not yet.
The usage quotas and limits will not be enforced until we as Admins have much better control and insights on the usage.
We will most likely be able to disable some features (either site wide or per user) and therefore limit who can consume credits (as credits are only consumed within Agents & Chat (Deep Research)). That feature would solve all your questions at once, however I don't believe in restricting Rovo too much.
There is no ETA on this yet but make sure to watch this Community space - I also found this feature request https://jira.atlassian.com/browse/ROVO-107 which is asking for more granular control over all AI features in general.
I think for a wide user base, Rovo search and chat will be a time saver and possibly worth paying for some extra credits. There are still some features missing for that but recent developments were promising.
Back to your question: Atlassian promised to deliver these needed governance features before enforcing the quotas and informing us at least 90 days prior.
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.