What is Rovo Studio?
The new Rovo Studio experience is currently limited to customers in our early access program.
Join the waitlist
Rovo Studio is an AI‑powered builder workspace that unifies how you design, automate, and connect solutions across your Atlassian work apps.
Makers, whether a knowledge worker or tech‑savvy power user, can use natural language to easily create and manage:
Rovo agents
No‑code apps
Automation rules
Rovo Studio uses Rovo AI and your organization’s Teamwork Graph (the data that connects people, work, and content in Atlassian Cloud) so the solutions you build can act with context about your projects, spaces, coworkers, and customers, while still respecting your existing permissions.
Rovo Studio requires AI to operate. If your organization has not enabled AI, you can open Studio but won’t be able to do anything.
Rovo Chat can solve it – and build it
When you’re in Studio, Rovo Chat is designed to act like an Atlassian tooling and workflow expert.
Describe whatever complex, workflow problems you’re trying to solve for yourself, your team, or your organization — and Rovo will recommend, step-by-step, what automations, agents, and/or apps you should build and how to do it. For example:
“Coordinate incident response across multiple teams”
“Reduce manual handoffs between sales and support”
A multi‑step solution might include:
Sequentially building automation rules
Configuring or creating agents
Assembling apps (and in the future, hubs)
This is intended for the kinds of problems an organization might otherwise bring to an internal expert or a services partner. Rovo Chat in Studio helps you go from a high‑level problem statement to a concrete, implementable solution.
You can then review, adjust, and manage everything Rovo creates using the same Studio libraries and governance controls.
What you can build in Rovo Studio
If you know exactly what you want to build, you can also start smaller. In Studio you work with a few core creations: agents, automation rules, and apps. (Hubs will be added soon.) Once again, you can simply describe your creation to Rovo Chat, or you can build agents and rules step-by-step from scratch.
Agents
Create AI‑driven agents that can:
Answer questions using your organization’s knowledge
Follow multi‑step scenarios
Take action in work apps like Jira and Confluence
You define each agent’s identity, instructions, knowledge sources, and skills, then choose where people can use it (for example Rovo Chat or embedded in Jira or Confluence).
All agents you create live in the Agents library in Studio, where you can update their behavior and control which places they appear in.
Automation rules
Design automated rules that can:
Respond to events (like an issue being created or a page being updated)
Evaluate whether particular conditions are present
Run actions across Atlassian and connected third‑party apps
Rules are made of familiar automation components including triggers, branches, conditions, and actions.
All automation rules you create live in the Automation library in Studio, where you can monitor their usage and turn them on or off.
Apps
Assemble no‑code apps that can:
Extend functionality in Jira, Confluence, etc
Use agents, automations, and skills behind the scenes to perform work
Can be brought into the Forge CLI to continue development with code
All apps you create live in the Apps library in Studio.
Who Rovo Studio is for
Rovo Studio is for people who shape how work happens, not just complete individual tasks:
Makers and tech‑savvy power users – Atlassian champions, operations owners, and other non‑developer builders who design workflows, automations, agents, and solutions for their teams.
Admins and team leads – App and org admins, or team leads who need to standardize processes, enforce guardrails, and safely roll out AI‑powered helpers.
Builders across the organization – People in support, IT, product, marketing, and other functions who want to turn their expertise into reusable agents, rules, and apps.
Anyone in your organization can open Studio from the Atlassian app switcher, but specific tools and tasks require appropriate permissions (for example, app or org admin rights to run certain automations).
Was this helpful?