Rovo Studio Access Automatically Granted to All Users After V2 Upgrade

Summary

After enabling Atlassian Rovo or upgrading to Rovo Studio V2, administrators may find that all licensed users (specifically those with Jira or Confluence access) are automatically granted access to Rovo Studio.

Diagnosis

Administrators often expect that restricting the "Agent Creation" setting in the Rovo configuration will remove access to the Studio interface entirely, but this setting only prevents users from building agents, not from accessing the Studio app.

Cause

When Rovo Studio was upgraded to V2, it was transitioned into an independent application within the Atlassian Cloud ecosystem. During this migration:

• Studio access was mapped to existing groups that already had product access (like Jira and Confluence).

• By default, many of these groups were granted the "Studio" app permission to ensure a seamless transition for existing users.

Solution

To restrict Rovo Studio access to specific groups (e.g., Administrators only), you must manage the application permissions at the group level within Atlassian Administration.

Step-by-Step Instructions:

1. Log in to admin.atlassian.com.

2. Select your organization and go to Directory > Groups.

3. Use the Product filter to select Studio. This will display all groups currently granted access to Rovo Studio.

4. For each group that should not have access:

   • Click on the group name.

   • In the Product access section, find Studio.

   • Toggle the switch to Off or remove the Studio application from that group's access list.

5. Ensure that only your intended administration groups retain the Studio product access.

Note: Removing a group from Studio access does not affect their Jira or Confluence licenses. It only removes the "Studio" entry from their product navigation and prevents them from accessing the Rovo Studio interface.