Administer Rovo
10 min
By the end of this lesson, you'll be able to:
- Distinguish admin responsibilities from user actions
- Identify where Rovo is administered in Atlassian Administration
- Explain why a single admin decision in Atlassian Administration affects all Rovo services
What is Rovo?
Rovo is an AI tool designed to work for you in every Atlassian app. Rovo can help you do straightforward tasks like summarizing content or comments, creating pages and work items, or finding answers within your organization. More advanced users can create Rovo Agents, use Rovo within developer tools, and much more. You can use natural language with Rovo, instead of complex queries, to work more quickly and easily within Atlassian apps.
Some of Rovo’s key benefits are that it:
✔ Supports individual productivity and efficiency by helping people move faster with AI-assisted writing, summarization, and task execution.
✔ Connects work and collaboration across teams by coordinating work, automating routine steps, and keeping teams aligned.
✔ Turns organizational data into insights and actions with AI search and chat can quickly surface the information you need to act.
Make the most of the capabilities offered by Rovo
Rovo features are available across various apps in the Atlassian cloud platform. The features differ from one app to another.
Rovo respects app permissions, so users can only see and modify content they have permission to view or modify.
Here are a few things Rovo can do:
✔ Automatically write queries so you can pull data into Atlassian Analytics.
✔ Help you pick the right request type for a customer’s request in the Jira Service Management portal.
✔ Set up automation in Confluence, Jira, and Jira Service Management to save time, reduce mistakes, and connect work across apps.
✔ Summarize Jira work items, extract key details, and surface related work.
✔ Draft, refine, and summarize Confluence page content so you don’t have to start from a blank page, can spend less time digesting and editing, and can keep content up to date.
We’re updating Rovo all the time. You can review the most up-to-date features on the Explore AI features page.
Allow or block Rovo
Rovo provides AI-powered features in every Atlassian app. Rovo is allowed by default and can’t be turned off, though org admins can block AI features in individual apps. If org admins block AI for an app, they turn off the AI features, and all content stays the same. This includes work that users created with AI assistance, such as Jira tasks or Confluence pages.
To allow or block AI in your apps:
- Go to Atlassian Administration at admin.atlassian.com.
- Select your organization.
- Expand Rovo.
- Select Rovo access.
- Block AI features from an app by selecting Add app.
- Select the app or apps you would like to remove AI features from.
- Select Block access.
- Allow AI features back in an app by selecting Remove next to a listed app.
👇 Here’s how AI app settings will show up in Atlassian Administration.
The steps to allow AI for Bitbucket and Trello differ from those for other apps. To learn more about how you can allow or block AI features in Bitbucket, visit Activate AI for apps. To learn more about allowing AI in Trello, visit Activate AI for your Trello Workspace or Enterprise.
Rovo admin responsibilities
Rovo admins make high‑level decisions about how Rovo is set up, controlled, and monitored across the organization. Rovo users and builders use Rovo and create agents within the guardrails admins put in place.
Admins are responsible for the configuration, governance, and oversight of Rovo. This is different from what end users and builders do.
👇 Click the tabs below to compare what Rovo admins do to what Rovo users and builders do.
Rovo admins are responsible for:
- activation and rollout decisions
- security and governance controls, including Model Context Protocol (MCP) and external AI governance
- data access, data connections, and external integrations
- ongoing monitoring, auditing, and incident response
- setting the boundaries that users and builders operate within
👉 For example: Aisha, a new starter, needs access to Rovo features in Jira and Confluence, and she needs to access Rovo Studio. She asks Tom, the Rovo admin, for help.
Tom ensures Aisha’s permissions and access are correct in accordance with company guidelines. Once Aisha has access, she decides she’d like an “Escalation Triage” agent to help her team. She works with Charlotte, a Rovo agent builder, to design and test the new agent in Rovo Studio.
Tom then makes sure Charlotte and Aisha build safely, with the right rules and access to data.
Administer Rovo in Atlassian Administration
Org admins manage Rovo in three areas in Atlassian Administration.
👇 Click the tabs below to explore where these settings are.
Organization settings are where security controls that apply to the whole organization, including IP allowlisting.
To locate the IP allowlists settings:
- Expand Security in the sidebar.
- Expand Device security.
- Select IP allowlists.
- Create and manage IP allowlists across your organization.
👇 This is where IP allowlists are created and managed.
Rovo settings do not live in Jira space settings, Confluence space settings, or individual app configuration panels. Instead, administration is split across two levels:
Organization-level governance (such as enabling Rovo, data security, and external connectors) is managed in Atlassian Administration by Org Admins.
Agent-level governance (such as who can create agents and agent access permissions) is managed within Rovo Studio settings by Studio Admins.
How Rovo services connect
All Rovo features are built on the same foundation, so they all follow the rules and settings that admins configure in Atlassian Administration.
👇 Click the boxes below to review admin responsibilities for each Rovo feature.
Here’s what Rovo Search and Chat need to work in your organization:
✔ Rovo activation
✔ Approved data connections
✔ Connector settings
✔ Existing product permissions
✔ Approved data connections
✔ Connector settings
✔ Existing product permissions
Admins are responsible for activating these features for the right sites, managing the data connections they depend on, and making sure access controls and source permissions are respected.
👉 For example: Ali, a Rovo admin, enables AI features for the apps her organization uses and confirms that approved data connectors are in place. Users can then use Rovo search and Chat within the boundaries Ali has set.
A single admin decision in Atlassian Administration will consistently affect Rovo Search, Chat, Studio, Agents, the MCP server, and the browser extension because they all share the same activation and access controls.