Atlassian Intelligence not approved for use by our organization.

[Paul A Gagne]

Our Security team reviewed and discovered that Atlassian Intelligence is sending data worldwide to be processed, and it seems to be an all-or-nothing thing for each product. Our Security team said they could consider enabling it for only one project, but it has to be turned on at the product level (Jira, Confluence, etc).”

[Sara Hekmat]

Hi Paul,

I'm part of the Atlassian Jira AI team. Currently, AI controls are applied at the product level. However, we're working on implementing more granular AI enforcement at the container level. This means users will soon be able to enable or disable AI at the project level in Jira. This additional control will prevent the use of customer data from a specific Jira project with AI.

https://www.atlassian.com/wac/roadmap/cloud/AI-Access-Rule-for-Jira?search=container&p=a0000a52-c7

Regards,

Sara

[Paul A Gagne]

My main desire is to enable Confluence to use AI support.  However, our Security team has determined that the tool cannot be approved for use in Confluence due to the following concerns:

1. AI is a Binary Option

The tool cannot be enabled for specific teams or groups—it is either on for the entire organization or completely disabled.
There is no way to limit access to certain users or restrict AI functionality based on business needs.

2. Data Exposure Risks

Confluence contains a wide range of sensitive information, including proprietary data, performance reviews, and other confidential content.
The AI tool processes data automatically, which could lead to unintended exposure of sensitive information.

3. AI Bypassing Access Controls

AI-generated responses could summarize or reference restricted pages, potentially exposing data that a user does not have direct access to.
This creates a security risk by unintentionally providing insights from protected or confidential content.

[Sara Hekmat]

The container-level enforcement feature will also be available for Confluence, allowing customers to enable or disable AI access for specific Confluence Spaces. This enhancement addresses your concerns, as sensitive information is often stored within particular Confluence Spaces. With this capability, you can restrict AI access to those sensitive areas, ensuring better control and security over your data.

[Paul A Gagne]

Sara, do you know when these changes will happen?

[Sara Hekmat]

I just know that the team is actively working on this feature, but I am not sure about the exact release data. You can follow this link for any update: https://www.atlassian.com/wac/roadmap/cloud/AI-Access-Rule-for-Jira?search=container&p=a0000a52-c7

[Kristian Klima]

Hi @Paul A Gagne 

This may not be a plausible option for you but it is technically possible.

Within your Atlassian Organization, you can create a new Jira instance, give access to people who need to participate on the project, and activate Intelligence just on that Jira site.

[Jim Knepley - ReleaseTEAM]

Hi @Paul A Gagne and welcome to the community. I'm glad you brought that up. Rovo in particular trains an instance of the "Atlassian teamwork graph" on product data, so I always suspected that it could exist in a different region from our cloud instance. It's good to know that Atlassian Intelligence is similar, but I'm not sure that "worldwide" is accurate. From: https://www.atlassian.com/trust/atlassian-intelligence

Do Atlassian Intelligence and Rovo respect data residency?

Not at this time. If you have data residency turned on, all of your in-scope product data

will remain stored in the region you’ve selected. However, Atlassian Intelligence and Rovo

data may be stored outside of that region, specifically in the US in order to appropriately

deliver their services.

(emphasis mine)

[Paul A Gagne]

I believe data residency is what we're looking for here. My next step would be to find out when it will be enabled for Atlassian Intelligence and how to turn it on.

[John Funk]

Hi Paul - Welcome to the Atlassian Community!

I am pretty sure it will never be able to be turned on for just a single project. You can open a support ticket with Atlassian to get clarification, though. 

https://support.atlassian.com/contact/#/