User Problem

Currently, when Rovo is activated on your site, all active users automatically receive access to it, with no existing controls to revoke this access. As a result, users who may not need access to Rovo are still included, and even if they do not require it, they are still considered billable.

With broad access enabled, certain projects, spaces, or other containers that need more sensitive controls end up becoming blockers for adoption since there's no granular control. 

Suggested Solutions

Implement a feature that allows administrators to assign Rovo product access to these specific containers. 

Current Workarounds

Deactivate Rovo from the site or to deactivate/suspend individual user access to the site (preventing access to other products on the same site). 

Keep all instances but Sandbox with Rovo Access turned off, as seen on -> https://support.atlassian.com/organization-administration/docs/manage-rovo-access/ or https://support.atlassian.com/organization-administration/docs/manage-rovo-access-for-enterprise/