nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do I use Atlassian Studio correctly?

Eric Roetenberg

Dear Atlassian Users,

We want to start using Studio in a structured way within our organization for, among other things:

Agents and automation, but I’m not sure how to implement this within our company. Can every user access Studio from within Jira?

What’s the difference between creating automation rules in Studio versus simply through Settings and System?

Who has experience using Studio? Help!!

Where can I find the right information on how to handle this?

Grtz Eric,

Accepted answers

Sarah Marenchino | Devoteam

Hi Eric,

Rovo Studio is evolving rapidly, and I think the best way to introduce it across an organization is to establish a clear governance model from the beginning.

Let me address your questions.

1. Can every Jira user access Studio?

Currently, Studio access is automatically granted to existing Jira, Confluence and JSM users in certain configurations, particularly following the Studio V2 rollout.

However, access can be managed separately through Atlassian Administration.

Atlassian has documented a procedure to remove Studio access from specific groups without affecting their Jira or Confluence licenses:

Manage automatically granted Studio access

There's also an important distinction between accessing Studio and being allowed to create agents, apps or automation flows. Creation permissions can be restricted separately through Studio settings.

2. What's the difference between Studio automation and Jira Automation?

Studio provides a centralized environment for building automation flows, Rovo agents and apps.

Jira Automation remains available through the familiar Jira administration interfaces.

These aren't necessarily separate automation engines. Studio offers a broader entry point, particularly when combining automation with AI agents and capabilities across Atlassian applications.

I wouldn't recommend migrating existing Jira automation rules simply because Studio is available.

3. How should Studio be introduced within an organization?

From a governance perspective, I'd recommend starting with a controlled pilot:

Identify a limited group of authorized creators.
Define ownership, naming conventions and documentation standards.
Establish a review process before deploying agents or automations into production.
Review agent identities, permissions and access to sensitive information.
Monitor execution logs, failures and automation usage.

I'd also distinguish between experimental agents and production agents, particularly when automations can modify business data.

4. Where can you find reliable information?

I'd start with these official Atlassian resources:

One final recommendation: Before rolling Studio out organization-wide, decide whether you want a centralized governance model, with a limited number of authorized creators, or a federated model where individual teams can build their own solutions within defined guardrails.

That decision will influence your access management, security model and long-term maintainability.

Hope this helps!

All comments

Sarah Marenchino | Devoteam

Hi Eric,

Rovo Studio is evolving rapidly, and I think the best way to introduce it across an organization is to establish a clear governance model from the beginning.

Let me address your questions.

1. Can every Jira user access Studio?

Currently, Studio access is automatically granted to existing Jira, Confluence and JSM users in certain configurations, particularly following the Studio V2 rollout.

However, access can be managed separately through Atlassian Administration.

Atlassian has documented a procedure to remove Studio access from specific groups without affecting their Jira or Confluence licenses:

Manage automatically granted Studio access

2. What's the difference between Studio automation and Jira Automation?

Studio provides a centralized environment for building automation flows, Rovo agents and apps.

Jira Automation remains available through the familiar Jira administration interfaces.

These aren't necessarily separate automation engines. Studio offers a broader entry point, particularly when combining automation with AI agents and capabilities across Atlassian applications.

I wouldn't recommend migrating existing Jira automation rules simply because Studio is available.

3. How should Studio be introduced within an organization?

From a governance perspective, I'd recommend starting with a controlled pilot:

Identify a limited group of authorized creators.
Define ownership, naming conventions and documentation standards.
Establish a review process before deploying agents or automations into production.
Review agent identities, permissions and access to sensitive information.
Monitor execution logs, failures and automation usage.

I'd also distinguish between experimental agents and production agents, particularly when automations can modify business data.

4. Where can you find reliable information?

I'd start with these official Atlassian resources:

That decision will influence your access management, security model and long-term maintainability.

Hope this helps!

Matthew Sinclair

Studio is how you build Rovo Agents - and/or Deploy them to make them available to your instance/site.

You have 3 modes of access -

Open to all
Limited to Atlassian Groups (Org Admin managed)
Closed to all ( or something to that effect )

There's new updates coming our way to make this better/more granular.

But until then you are urged to proceed with caution - opening it to all means you risk "Agent Sprawl" where folks can build/duplicate/replicate/copy agents doing same things.

Our org will likely handle it like we handle automation - only Jira-Admins (not space admins) can handle Agents and deploy them.

At least something to that effect - need to test in our sandbox.

Keep in mind when Automation offers Studio as an option - you're likely dealing with Rovo itself - not Jira Automation.

Both have separate meters - Automation uses Steps - Rovo uses Credits.

Also keep in mind this isn't to do with Studio Seat access - Studio itself is generally free when you have Jira and/or JSM with appropriate access to Rovo. Nor does it override the Admin setting on who can access it.

If AI Security is a concern - you may want to look into Atlassian Guard Premium - new features that will monitor what your users are doing with Rovo in terms of interception.

Sarah Marenchino | Devoteam

One additional governance point worth checking after the Studio V2 rollout:

For organizations that previously used Studio, Atlassian automatically granted the Studio app admin role to existing Jira, Jira Service Management and Confluence app admins.

This matters because Studio app admins have full creation permissions, even if agent creation was previously restricted elsewhere.

Before rolling out Studio more widely, I would therefore review both:

Studio app roles in Atlassian Administration.
Creation permissions for agents, apps and automations in Studio settings.

These are separate controls, and reviewing only one of them may leave broader creation rights than intended.

Atlassian documentation: Use Rovo Studio in your organization

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira