Uploaded image for project: 'Atlassian Intelligence'
  1. Atlassian Intelligence
  2. AI-110

Ability to disable/enable Atlassian Intelligence (AI) for only a specific space/project (not the entire Confluence / Jira / etc. site)

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Admin - General
    • None
    • 21

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      It would be great to allow admins to disable/enable AI for only a specific space / project or selected spaces / projects.

      Currently, you can only enable or disable it for the entire Confluence site (or other products): https://support.atlassian.com/organization-administration/docs/activate-atlassian-intelligence-for-products/ 

          Form Name

            [AI-110] Ability to disable/enable Atlassian Intelligence (AI) for only a specific space/project (not the entire Confluence / Jira / etc. site)

            Thomas Balasch added a comment - - edited

            There was a feature on the Cloud Roadmap für exactly this issue!

             

            AI Access Rule for Rovo and Atlassian Intelligence (COMING SOON Q3 2025)
            The ability to block LLM access to data in specific containers (projects/spaces) within an organization's Atlassian products.
            https://www.atlassian.com/wac/roadmap/cloud/AI-Access-Rule-for-Rovo-and-Atlassian-Intelligence?status=comingSoon;future&search=data&p=e820bf53-97

            I documented it, because it was very much relevant for our decision to enable Atlassian Intelligence.
            Now this feature is gone from the roadmap.

            What happened Atlassian?

            Thomas Balasch added a comment - - edited There was a feature on the Cloud Roadmap für exactly this issue!   AI Access Rule for Rovo and Atlassian Intelligence (COMING SOON Q3 2025) The ability to block LLM access to data in specific containers (projects/spaces) within an organization's Atlassian products. https://www.atlassian.com/wac/roadmap/cloud/AI-Access-Rule-for-Rovo-and-Atlassian-Intelligence?status=comingSoon;future&search=data&p=e820bf53-97 I documented it, because it was very much relevant for our decision to enable Atlassian Intelligence. Now this feature is gone from the roadmap. What happened Atlassian?

            Dylan Reeder added a comment -

            It would be nice to have more granular restrictions. Like having the capability to disable Atlassian Intelligence for specific users or disabling just pieces of Atlassian Intelligence like Atlassian Definitions.

            Dylan Reeder added a comment - It would be nice to have more granular restrictions. Like having the capability to disable Atlassian Intelligence for specific users or disabling just pieces of Atlassian Intelligence like Atlassian Definitions.

            Rune Rasmussen added a comment -

            We absolutely need to be able to restrict AI.
            In Confluence as well as in Jira.

            We have some thousands of spaces with Customer data.
            We don't own that data, we only store and process it, so the things we can do with that data is determined by the contracts we have with our customers.

            As it stands right now, we won't be able to justify enabling AI on Confluence.

            In the future it is entirely realistic that we would end up handling data in Jira that shouldn't be accessible by AI, so being able to restrict access in Jira is also a requirement for us.

            Rune Rasmussen added a comment - We absolutely need to be able to restrict AI. In Confluence as well as in Jira. We have some thousands of spaces with Customer data. We don't own that data, we only store and process it, so the things we can do with that data is determined by the contracts we have with our customers. As it stands right now, we won't be able to justify enabling AI on Confluence. In the future it is entirely realistic that we would end up handling data in Jira that shouldn't be accessible by AI, so being able to restrict access in Jira is also a requirement for us.

            Ashish Dobhal added a comment -

            Assigning the ticket to product team. 

            Ashish Dobhal added a comment - Assigning the ticket to product team. 

              351ded8d2d25 Denise Day
              505da7f6a08d Roberto M.
              Votes:
              65 Vote for this issue
              Watchers:
              45 Start watching this issue

                Created:
                Updated: