Answers to Questions @ Rovo Is for Everyone — Ready to Lead the Change? (Community-Led Class)

[#1]

You brought the energy and the questions — from how Rovo handles blocked users to Data Center integration and agent behavior quirks. We've rounded up your top Qs (and real answers!) from the class. below to help you keep the momentum going. 

💬 Want more? Head over to the discussion board to check out the April's Sherif-sclusive and catch the Q&A from the Unleash Your Team with Rovo webinar.

Let’s keep leading the change together!

Q1: How does Rovo work with JSM customers?

A: Rovo integrates natively with Jira Service Management (JSM). You can use it to triage requests, summarize tickets, and interact via Dev Agents or support agents. It complements, not replaces, the Virtual Agent.

Q2: If someone is on my blocked users list on Google, Rovo won't scan their content, right?

A: Correct. Rovo respects Google Workspace permissions. If a user is blocked or doesn’t have access, Rovo cannot index or retrieve that content through the Gmail or Drive connectors.

Q3: When will Data Center connect be available?

A: The Confluence Data Center connector is already available. Jira Data Center is scheduled for release by October 2025. Updates will appear on the Rovo roadmap.

Q4: To connect Data Center to the enterprise cloud, what is the network configuration?

A: You need to deploy a secure connector, often hosted behind a firewall or proxy. Admins must allow access between Rovo Cloud and the Data Center app instance, typically via token-based or OAuth configuration.

Q5: Why do you say Jira is that JSM as well?

A: "Jira" often refers to the entire platform (Jira Software, JSM, and the formerly Work Management). Rovo works with both Jira Software and Jira Service Management, offering tailored experiences based on the project type.

Q6: What is the difference between the out-of-the-box agents and more agents?

A: Out-of-the-box agents are prebuilt by Atlassian for common tasks (like onboarding or triage). Think of them as a starting point for you to edit to your needs. You can also create agents in Rovo Studio from scratch. Agents in general perform specified tasks.

Q7: Will Rovo work with JLM or other project types?

A: Rovo supports all Jira project types (software, service, business). "JLM" likely refers to Jira lifecycle or custom labels. Rovo agents can operate across these projects if granted access.

Q8: Is there the ability to disable connectors for users as we wanted to have some control on how to roll that out?

A: Yes. Only admins can configure connectors. End users cannot independently add connectors unless permitted. Role-based access control for finer control is on Atlassian’s roadmap.

 Q9: Can you use Rovo as a chatbot in Jira Service Management?

A: Yes. Rovo can act as a smart assistant in JSM, suggesting request types, triaging issues, and summarizing tickets using contextual knowledge from Confluence and linked data.

Q10: Can Rovo help you troubleshoot automations?

A: Indirectly. Rovo can analyze linked documentation or tickets related to your automation issues, but it doesn’t currently run or debug automation rules itself.

Q11: Is Rovo Studio free for Premium users?

A: Yes. Rovo Studio is included for Premium and Enterprise plan customers. It allows creation of custom agents and agent actions.

Q12: Is Rovo secure when using it with sensitive content like Google Drive?

A: Yes. Rovo adheres to Atlassian’s cloud security and compliance policies. It respects source system permissions and does not store or train on customer data.

Q13: Can Rovo integrate with Microsoft Teams or Slack?

A: Yes, Atlassian Rovo integrates with both Microsoft Teams and Slack to enhance your organization's search capabilities across communication platforms. Rovo offers a native connector allowing it to index chats and channels. Currently, Rovo does not support direct interaction within Slack or Microsoft Teams (e.g., chatting with Rovo or creating Jira issues from within these platforms). However, Atlassian has acknowledged this limitation and is actively working on bringing more interactive Rovo experiences into Slack and Teams.

Q14: Can I treat a Rovo agent like an Active Directory account?

A: No. Rovo agents are not service accounts and do not function like directory-bound user identities. They follow access rules of the user who invokes them.

Q15: How do I sign up for the Dev Agent beta?

A: Read the instructions here https://community.atlassian.com/forums/Rovo-Dev-AI-Agents-Beta-articles/Get-started-with-the-Rovo-Dev-Agents-now-in-beta/ba-p/2986367

Q16: Does Rovo support Google Workspace integration?

A: Yes. Rovo can index content from Google Drive, Gmail, and Docs, if configured by an admin and permitted by OAuth scopes.

Q17: MS365 Copilot can be integrated with Jira/Confluence. Why would we need Rovo?

A: Rovo offers 4 key advantages over Copilot:

1. Native integration with Jira/Confluence, no setup needed.
2. Permission-aware—respects Atlassian access controls.
3. Uses the Teamwork Graph to personalize responses based on your work and team context.
4. Action-ready agents that can create/update issues directly in Atlassian tools.

Q18: What will Rovo cost in the future?

A: Rovo is currently being rolled out to be included in all plans at no additional cost. Atlassian is exploring a consumption-based pricing model that includes usage limits, aligning with common practices in the AI industry. This approach promotes sustainability and responsible use while making Rovo more adaptable to different team needs.