Issue Description
Connectors (both out of the box and custom-built ones) currently cannot be permissioned to individual features like Agents only.
Root Cause (if known)
Connectors are globally made available with no admin permission
Proposed Solution/Enhancement
We would like to see that Connectors could be made available only to Agents and disabled/not visible for Search and Chat Assistant for users. Some data sources we like to have on the Glean platform should only be serviced for particular group of users through an Agent custom build for that data source as chat or search input triggered. But the content should not show up in any regular search/chat assistant UI for all users.
This would apply to Glean default out of the box connectors and any custom build connectors by us. Although custom API Actions might be built for Agents, we would rather have natively this feature in place through the admin RBAC/Connector settings.
Hence, it would be nice to have an RBAC → Connector by Feature permission schema in Glean, so that by Feature we can decide which connectors are allowed for Search, Chat Assistant and Agents to be used as well as limit that by role-based end users of the platform.
Impact
We have internal applications (e.g. Productboard) in our company, we do not want the content to be exposed to in the general population for search / assistants, but we do want to offer end users Agents to specifically search or chat with Productboard data directly if Agent is shared to those users/groups.
The exposure of certain external public data like Govwin or draft feature / ideas in our Productboard is not something we like to include in results for proposals but still as sources individually have value to be in Glean made available.
