🆕 IT'S HERE: Rovo Agent Governance + Create Permissions

[#1]

This is not a drill: one of our most requested features by admins, Rovo Agent Create Permissions, is HERE! 🎉

Why this matters

From day one, admins have asked for more granular control over who can create Rovo agents in their organizations. Well, we heard you, and we’re excited to deliver. 🫶 

This release is about making agent management safer and more manageable as usage grows. For enterprise customers, it means you can roll out agents with more confidence. For admins, it’s a way to keep things under control without extra hassle. 

So, what’s new?

• 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.

• Clear UI: If you don’t have permission to create agents, the option will be disabled (or in some cases hidden) and you’ll see a message explaining why. This applies to both creating and duplicating agents.

How does it work?

1. Navigate to your Rovo admin settings in Studio.

2. Find the new “Agent Create Permissions” section. 

3. Select users or groups who should have agent creation rights.

4. Save your changes — that’s it! Users without permission will see a clear message if they try to create an agent.

Want to see it in action? For step-by-step instructions, visit SAC here, or check out this quick demo video from our resident Rovo Agent Queen, @Jensen Fleming :

We want your feedback!

This feature was built in direct response to your requests, so keep the feedback coming! Let us know how these new controls are working for you, and what else you’d like to see to make Rovo even better for everyone.

Drop your questions, suggestions, or predilections in the comments below.

Happy Agent building! ☺️

[Daniele Tagliani]

Well done! 

[Sheikh_ Salah _IDA_Senior Expert_]

Do you have plans on the roadmap to allow permissions to be distinguished between production and sandbox environments? At present, the new Create Permissions appear to apply globally. For many organisations, having separate controls would be essential and enabling more freedom for testing in sandbox while keeping stricter governance in production. @Janessa Drainville 

[Janessa Drainville]

Hi @Sheikh_ Salah _IDA_Senior Expert_! That's a great question – at the moment, no, there is no mention of a roadmap item or upcoming feature that would allow for separate permission controls between these environments. 

You can activate and test Rovo in sandbox environments, but the permission model remains consistent across both production and sandbox. This is because Rovo respects existing Atlassian permissions and AI settings, but does not accommodate environment-specific permission granularity at this time. 

I've taken a spin through JAC and it doesn't look like there's an existing feature request for this, but if it's a feature you'd like to see, please submit a feature request here. This way folks can upvote it and we can get this supported on the roadmap! 💙

How to Create a New Feature Request

Click the Create button.

Select the appropriate project (e.g., “ROVO” linked above).

For Issue Type, select Suggestion (for feature requests).

Fill out the form:

• Summary: Use a clear format like “Doing X on Y feature has Z result.”
• Description: Include as much detail as possible:
• Issue Summary
• Steps to Reproduce (if applicable)
• Expected Results
• Actual Results (if relevant)
• Workaround (if any)
• Component: Select the relevant component to ensure correct routing.
• (Optional) Add any relevant attachments or screenshots.

Click Create.