Atlassian Rovo

Description Features Permissions Security & Compliance

Atlassian Rovo is your intelligent AI assistant for real-time search, knowledge discovery, and seamless collaboration. Rovo brings together the power of Atlassian's AI with Slack's communication, enabling you to find answers, summarize threads, and automate support—all without leaving your chat.Whether you need to search across Atlassian and external tools, get instant help via @mentions, or deploy custom agents for specialized workflows, Rovo is designed to make your team faster and smarter. Enjoy private DMs, right-rail AI assistance, and flexible agent configurations—all in one unified app.You can also bring Slack to Rovo and connect it to find your conversations where you work. That means you can search your channels and messages from within your Atlassian apps to find key conversations. This requires an organization admin sets up the Slack connector in Atlassian AdministrationSee more about how Atlassian handles data privacy.Atlassian Rovo uses AI. It can make mistakes so ensure you verify its responses.Note: This app uses the assistant:write scope, which requires a paid Slack plan.Features• Direct Messaging with RovoChat privately with Rovo to get instant answers, search knowledge, or automate tasks.• AI Assistance in the Right RailAccess Rovo's AI in Slack's right rail, leveraging channel context for smarter, more relevant help.• @Mention Atlassian RovoMention Rovo in any channel to get immediate, context-aware assistance or thread summaries.• Configure triggers in different channelsSet up triggers for Rovo or custom agents for specific uses like deflecting questions in help channels.• Thread SummarizationUse the message action or @mention Rovo in a thread to get concise, AI-generated summaries.• Easy Migration from Legacy AppSimple steps to migrate from the legacy Rovo app—ensuring a smooth transition for your team.Configuration• InstallationGo to Slack's Apps section and search for "Atlassian Rovo."Add the app to your workspace and follow the steps to connect your Atlassian account (if required).Start a DM with Rovo, or invite it to channels for group assistance.• PermissionsIn DMs, Rovo uses your user permissions to provide personalized answers.In channels, Rovo uses bot permissions to protect sensitive information.Rovo can view messages, respond to mentions, and summarize threads as authorized.• Custom Agent SetupUse /rovo add to select or add custom agents.Manage channel settings with /rovo manage• Top Bar SetupAdd Rovo to your top bar for quick access to AI assistance in any channel.

Permissions

Atlassian Rovo will be able to view:

Atlassian Rovo will be able to do:

Review the details to better understand this app’s security practices. To learn more about assessing apps for your workspace visit our Help Center.

General

Privacy & data governance

Data retention policy

It is important to understand how Rovo and Atlassian handle permissions and your data. As with any generative AI product, experiences and quality can vary and be dependent on a number of things including the knowledge sources provided, the user's access, and the probabilistic nature of LLMs (large language models) Connections with third-party apps Rovo includes features that are designed to integrate with third-party apps. For example, you may connect third-party apps to Rovo using connectors. Before connecting to a third-party app, we recommend reviewing the types of data stored in that app, and confirming that connecting the data aligns with your internal data use policies and practices. See Manage Rovo connectors for more information. Connecting Rovo with third-party apps may give third parties access to information you choose to use in connection with their apps, and your use of third-party apps and information you share may be governed by their terms and policies, including their privacy policies. For example, if you use an Agent purchased by your organization from Atlassian Marketplace, your use of that Agent is subject to the third-party’s terms and policies. For more detail, see https://support.atlassian.com/rovo/docs/rovo-data-privacy-and-usage-guidelines/

Data archiving and removal policy

Deleted data For admin managed connectors, we ‘listen’ for content deletion, and update the Rovo index with changes. For example, once the Rovo index is updated, content that’s deleted from a connected third-party app will not appear in Rovo results. For more information on permissions and connectors, see Manage Rovo connectors. For Smart Link connectors, deleted Smart Links may still show up in Search Results. However, if a user clicks on a link to deleted content or clicks on a link they no longer have access to, the link will appear broken. See Search with Smart Links for more information. If an organization admin disconnects a third-party app from Rovo, we will delete the content we've indexed from the third-party app within 30 days. However, deletion for GitHub content works differently. Because your GitHub data is integrated through the GitHub for Jira app, data is deleted only if you disconnect GitHub from Rovo and uninstall the Github for Jira app. See how to disconnect GitHub from Rovo for more information. For more detail, see https://support.atlassian.com/rovo/docs/rovo-data-privacy-and-usage-guidelines/

Data storage policy

Data usage We index the entire workspace of the third-party app you connect (for example, the entire Google Drive or the SharePoint workspace). You can refine the scope of the data indexed with some specific connectors (such as Google Drive and SharePoint) using a blocklist. For more, see Manage blocklist. To provide Rovo, we store the content for each file found in a third-party app and associated usage data. We also store permissions settings about the file to ensure that we only show content that users have access to. We use this data to serve your Atlassian features, such as Rovo Search, Chat and Agents. We may also use it for troubleshooting and debugging, or to solve support queries you or your team raise with us. For Chat and Agents, we retain your inputs and outputs for 30 days for safety and security purposes. User data obtained via Google Workspace API Sensitive or Restricted scopes is not used to develop, improve, or train generalization AI and/or ML models. For more detail, see https://support.atlassian.com/rovo/docs/rovo-data-privacy-and-usage-guidelines/

App/service has sub-processors

yes

Guidelines for sub-processors

https://www.atlassian.com/legal/sub-processors

App/service uses large language models (LLM)

yes

LLM model(s) used

GPT-4o

LLM retention settings

Data residency gives you control over where your in-scope app data for Jira, Jira Service Management, Jira Product Discovery, and Confluence is hosted. details - https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/

LLM data tenancy policy

While our customers share a common cloud-based IT infrastructure when using Atlassian’s products, we have measures in place to ensure they are logically separated. More details - https://www.atlassian.com/trust/security/security-practices

LLM data residency policy

Certifications & compliance

Security