Can we restrict access to Rovo advanced features (like Agent creation or Studio) in Jira/Confluence?

[Sudarsana G]

Hi team,

We’ve recently enabled Rovo across our Atlassian Cloud site and are exploring its capabilities. We’ve noticed that all licensed users currently have access to create Rovo Agents and use features like Rovo Studio, even if they are not part of any designated user group.

We’d like to understand:

1. Is there a way to restrict or control access to advanced Rovo features (such as Agent creation, Studio, or Developer CLI)?

2. Can we configure permissions based on Atlassian user groups, so only specific users (e.g., rovo-dev-agents-admins) can create or modify agents?

3. Is there a roadmap to implement more granular permission controls for Rovo within Jira and Confluence?

We have internal governance policies in place, but technical enforcement would help us maintain compliance and security more effectively.

Any guidance or official documentation would be greatly appreciated.

By default any user groups will get created as soon as we enable Robo like below

rovo-dev-agents-admins-powerschoolgroup

Grants access to Rovo Dev Agents and Rovo Dev Agents administration features on powerschoolgroup

rovo-dev-agents-users-powerschoolgroup Default access group

Grants access to Rovo Dev Agents on powerschoolgroup

[Dwight Holman · Accepted solution]

Don't really want to speak for them, but Atlassian don't usually reply here.

I understand they have focused on delivering function first, and then addressing Enterprise needs (like permissions/access control) later. 

1. No not currently - but Atlassian are working on some of these you could follow in JAC:
   • ROVO-76 Limit via Permissions on who can create Rovo Agents
   • ROVO-130 Ability for Multiple Users to Edit Rovo Agent
   • ROVO-23 Ability to assign Rovo access based on user group membership
   • ... + more
2. See #1- I assume they will do something like that.
3. Atlassian are reluctant to provide a roadmap for AI features because this can limit their ability to change direction.

My suggestion would be to follow the backlog items - perhaps post comments or questions there.

Or you could contact Atlassian support and ask some questions. 

[Janessa Drainville]

@Dwight Holman, JAC-76 just got resolved earlier this week! 🥳  

• Org Admin Controls: Only users or groups that an org admin selects will be able to create Rovo agents. By default, everyone has create permissions but org admins will now have the power to remove this from everyone or limit agent creation to selected groups.

@Sudarsana G Here's a quick Loom with details on it 💙