Use Rovo Studio in your organization
Who can do this? Role: Organization admin Atlassian Cloud: Standard, Premium, Enterprise Atlassian Government Cloud: Not available |
Studio is an AI-powered workspace where you can design, automate, and connect solutions using automation flows, apps, or agents.
Read more about Studio and see what you can build
Your organization is now using the new Studio experience, either because it was automatically upgraded or an admin chose to turn it on.
This page explains what’s changed, how user access is set up, and what we suggest you do next.
What’s changed
Studio is now a standalone Atlassian app. Like Jira, Confluence, and Jira Service Management, you can manage user access to Studio directly from Atlassian Administration
How user access is set up
To keep things running, we’ve automatically granted the Studio user role to anyone who already had a User role in Jira, Confluence, or Jira Service Management. New users are also given the Studio user role.
This only applies to organizations with access to the previous Studio experience.
Everyone who had access to the previous Studio experience will continue to have access to the fresh version of Studio.
App administration roles in Studio
Users with the app admin role in Jira, Jira Service Management, or Confluence are also granted the app admin role in Studio. Again, this only applies to existing organizations with access to the previous version of Studio.
Studio app admins receive full creation permissions within Studio.
This means someone can create agents even if an organization admin has previously restricted their permissions to create agents in other products.
You can review and manage Studio user access at any time in Atlassian Administration.
Read more about managing role and app permissions
Manage who can create in Studio
As an administrator, you have full control over who can build in the new Studio experience. While initial access to agents and automations are open, you can restrict these permissions at any time via Studio settings.
New default permissions
Automations and apps: All users with Studio access have permission to create automations and apps by default.
Agents: Your existing configuration remains as is. Users who previously had agent-creation privileges will keep them in the new experience.
To modify permissions for automations, apps, or agents, or to limit creation rights to specific groups, navigate to Studio, then Studio settings.
Next steps
Now you’ve got the new Studio experience, it’s worth double-checking you’re happy with the roles and access set up for your organization.
Review user access. Go to Atlassian Administration to review who has the Studio user role and adjust access if needed.
Review creation permissions. Go to Studio, then Studio settings to manage who can create automations, apps, and agents. How to manage who can create in Studio
Get to know more about Studio. For an overview of what you can build, check out What is Studio?
Was this helpful?