User Problem

Currently, Rovo will index the entire site once activated. That is not always desired for NDA Project/Spaces and Projects/Spaces that are subject to elevated data sovereignty- or data protection requirements.

Suggested Solutions

Just like in the definition in Rovo Agents it should be possible to define by site which Spaces / Projects / Repositories, etc. should be indexed and which cannot. The functionality is available already when creating Rovo Agents, this should be extended to the Rovo Configuration page at the organization level to better define Rovo scope within the specific site.

Current Workarounds

There is currently no workaround, Rovo is activated for the entire site and its products