Problem Definition

Currently, Rovo Chat uses the whole organisation's knowledge when interacting with end users. 

Suggested Solution

Add a scoping capability for Rovo Chat to be similar to what is currently available for Rovo Agents, i.e., the ability to define knowledge scope at the Confluence space/page level or Jira project/space level.

The settings is to enable per-site or on the organisation level by the administrators to restrict Rovo Chat to specific subsets of content, aligned with customer's internal access controls and regulatory requirements.

Workaround

There's currently no workaround for this.