Connectors
Connectors are how agents reach company tools. Every connector carries a
data class — external, internal, commercial, personal — which the
data-flow policy uses when results may leave the workspace.
The catalog
Section titled “The catalog”Official MCP servers (Notion, Slack, Jira, YouTrack, Salesforce, …). An admin enables a service and chooses, per service, which connection methods are on:
- OAuth sign-in — each person connects through the vendor’s consent screen. Optionally register your org’s own OAuth app so the vendor admin can approve exactly one app.
- Shared org token — one company credential, stored encrypted; everyone connects in one click. Right for wikis and knowledge bases where personal identity doesn’t matter.
Access is scoped by groups (a service with no groups ticked is visible to the whole org).
Custom MCP servers
Section titled “Custom MCP servers”Anything the catalog doesn’t cover: register your own MCP endpoint (HTTP/SSE or stdio) with one vaulted org credential, then grant it to specific people or groups. Members granted access run through it without ever seeing the secret.
For each person
Section titled “For each person”Members connect their own accounts under Connectors; an admin can open any member’s row under Members to see exactly what that person can reach — and where each right comes from (whole org / via a group / a direct grant).