Agent integration data connection access
Workspace Admins can limit which data connections the Hex Agent may use in Threads that are started outside of the Hex app.
- Users require an Admin role to access this setting.
- External integration data connection controls apply to both the Hex Agent in Slack and the Hex MCP Server.
When a user starts a Thread from an external integration — like the Hex Agent in Slack or the Hex MCP Server — the Hex Agent automatically selects from connections the user has access to, which means a casual question in Slack or an MCP chat could route analysis against data you'd rather keep out of those surfaces.
External integration data connection access controls which connections the Hex Agent may use for Threads started outside the Hex app. Connections you don't include are unavailable for those external workflows, regardless of the user's individual access. Many teams use this to exclude sensitive or regulated sources from external Threads while keeping day-to-day connections available.
For best practices on descriptions, exclusions, and connection permissions, see Optimizing your data connections for the Hex Agent.
Configuration
Configure External integration data connection access in either:
- Settings → Integrations → External integration data connection access
- Settings → Data sources → select a data connection → Access
Related documentation
- Hex Agent in Slack: using the agent in Slack, permissions, and setup.
- Hex MCP Server: connecting Claude, Cursor, and other MCP clients to Hex.