Atlassian Intelligence - Scoping a definition

[Dan Crews]

Context: Confluence is divided into multiple spaces, and in many organizations each space defines its own bounded contexts, each with its own set of terminologies and definitions. This can make the "define" functionality a completely new set of problems  and a source of confusion when it sources answers across all of the organization.

Example: In an API Architecture space, the term "consumer" would specifically refer to an API consumer, perhaps defined by a web client. In a product-focused space, the term "consumer" represents an end user who purchases a product.

Question: Is it possible to define any kind of boundaries around Atlassian Intelligence? Or perhaps is there any kind of weighting mechanism that prefers local definitions over others; i.e. can I improve definitions by creating a page of terms within a space?

[Shawn Doyle - ReleaseTEAM]

I don't believe there are any settings to tweak how Atlassian Intelligence works with confluence yet.

[John Dunkelberg]

It's certainly a good thought.  Certainly there are terms like Component and Module that are highly overloaded already and confuse human intelligence.  :)

Also I could speculate that Legal might feel better if we could define such boundaries to exclude AI's reach into specific spaces.  It would be simpler than what people would really want, which is "If JohnD doesn't have access to Space XYZ, then Atlassian Intelligence cannot answer a question for him using contextual information found in Space XYZ."

[Emilie Rochedy]

Hi @Dan Crews

Atlassian Intelligence is based on your teamwork graph so the definitions will be relevant to specific teams. Users can also vote on the relevance of the definition to improve results.