Summary:

When building a custom Rovo Agent in Rovo Studio, the list of connectors available as Knowledge Sources is significantly smaller than the full list of connectors available in Rovo Search and Chat. This inconsistency creates a frustrating gap for customers who have already invested in connecting their tools to Rovo, only to discover those same tools cannot be used to power their agents.

Expected behavior:

All connectors that an admin has already connected and configured for Rovo Search/Chat should also be available as selectable knowledge sources when building Rovo Agents.

Why this matters to customers:

Limits agent usefulness for non-Atlassian-native teams — Many enterprise teams rely on tools like Notion, Box, Asana or HubSpot as their primary knowledge stores. If those can't be knowledge sources, Rovo Agents are simply not useful for those teams — even if Rovo Search works fine.
Inconsistency erodes confidence — When users see Slack, GitHub or SharePoint do work as agent knowledge sources but Asana, Dropbox or Notion don't, there is no intuitive explanation. It appears as an arbitrary limitation, not a deliberate design decision.