Unable to add custom knowledge with my space info for Rovo Agent

[Venkatesh Gandham]

I'm trying to create Rovo Agent for specefic confluence space.  It gives me option only to select all content.  I don't see drop down with all spaces listed.

Can do we add custom knowledge to point it to certain spaces in Confluence only?

[Gaurav · Accepted solution]

Hello @Venkatesh Gandham

While you review the custom ROVO agent, you get the option to select the specific Confluence Space to be added under 'Custom Knowledge'. Refer the below screenshot.

Please share your thoughts and feedback.

-GG

[Felipe Justino]

@Gaurav 

 Thanks for sharing knowledge

[Venkatesh Gandham]

I don't see any spaces. I only see all content. How did you get to show the spaces ?

[Laura Campbell]

@Venkatesh Gandham It should look something like this, and you can start typing to search for a space you want to add. 

If you only want certain child pages, you should select "content under" and then pick the parent page. The Rovo agent will only use the pages under that parent page item as the custom knowledge.

[Dr Valeri Colon _Connect Centric_]

To add to this thread @Venkatesh Gandham: Both things are true, depending on rollout status and permissions. Space-level and page-level scoping is being rolled out gradually. If you only see “All Confluence content,” your tenant hasn’t received the granular selector yet. On tenants that do have it, you can search for a space or use “Content under” to scope knowledge to a parent page and its children. Until rollout completes, permission-based restriction or dedicated parent pages are the only reliable workarounds.

[Felipe Justino]

Based on current testing and the official Rovo documentation, it’s not yet possible to select specific Confluence spaces when adding custom knowledge to a Rovo Agent.
Right now, Rovo only allows selecting “All Confluence content” as the knowledge source, the space-level selector has not been released yet.
What you can do for now:
Restrict permissions directly in Confluence
A Rovo Agent can only access pages that both you and the agent have permission to view.
So even when selecting “all content,” it will not index or use pages that don’t have read permissions.
Create dedicated pages or content areas
As a workaround, some teams create a dedicated folder/section containing only the content they want the agent to reference, and then guide the agent (via its instructions) to focus only on that area.
Wait for Atlassian to release more granular selectors
Atlassian has confirmed that they are working on more fine-grained knowledge controls (by space and even by page), but this has not yet been rolled out to all customers.

[Venkatesh Gandham]

If this is the case. What is the point in building custom agent if Rovo agent already looks at your entire confluence content?  I thought ability to build custom agents is to enable specialized knowledge in a. business group instead of enterprise wide knowledge. 

As a workaround i like your idea to restrict only to certain spaces rather than entire content.