Atlassian Rovo & Slack Integration

Atlassian Rovo

Description Features Permissions Security & Compliance

Atlassian Rovo is your AI teammate that lives in Slack.You're in a conversation. Someone flags a blocker. A decision gets made. Context is flying by. Rovo makes sure none of it gets lost — and none of it requires you to leave the chat to go do something about it.With Rovo in Slack, you can turn conversations into answers, work items, pages, and automated workflows — without switching tools.Find answers, not tabs:* Ask Rovo anything — get direct answers pulled from Jira, Confluence, and your connected apps. No more opening six tabs to find that one decision from last quarter.* Catch up on threads instantly — missed a 50-message thread? Right-click → Summarize, or @mention Rovo and ask "what did I miss?" Get the TL;DR in seconds.* Get context-aware help in the sidebar — open Rovo from the top bar and it reads the channel you're in, so its answers are relevant to what you're actually working on.Turn conversations into work — right where they happen:* Create Jira issues from a discussion — spot a bug, a task, a decision? Ask Rovo to create the ticket. It pulls context from the thread, fills in the details, and lets you review before submitting.* Summarize projects and issues — ask Rovo to give you a quick status on any Jira issue or project so you can make decisions without digging through boards.* Document decisions as Confluence pages — a thread just resolved something important? Ask Rovo to turn it into a page so it doesn't disappear into chat history.Deploy agents that handle the repetitive work:* Set up custom agents in channels — deflect repeat questions in help channels, triage incoming requests, onboard new teammates. Configure what triggers them: keywords, emojis, or every new message.* Browse and use your org's agents — discover agents your team has built from the Home tab and start a private conversation with any of them.* Let agents handle the follow-ups — once triggered, agents keep replying in the thread so the person asking gets a complete answer, not a one-shot response.And Slackbot can tap into Atlassian too:Rovo also powers Slackbot with Atlassian workflows through Rovo MCP (Model Context Protocol). That means anyone in your workspace can ask Slackbot to pull information from Atlassian products, right where they're already working.* Ask Slackbot to triage Jira work — check sprint status, find blockers, or create tickets right from a conversation.* Pull up Confluence knowledge on demand — specs, runbooks, project context — Slackbot retrieves it in real time.* Natural-language access across Atlassian — Slackbot invokes the right tools on your behalf. No extra install required.Always available, your way* DM with Rovo — chat privately to get instant answers or take action. All DMs use your personal permissions.* @Mention in any channel — type @Rovo for immediate, context-aware assistance.* Bring Slack to Rovo — https://support.atlassian.com/organization-administration/docs/connect-slack-to-rovo/ so you can search channels and messages from within Atlassian apps.

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