Connections#

A connection is an authenticated link to one external system. It is the platform's atom: you connect a system once, and every product operates over that connection.

What's in a connection#

• A type (salesforce, hubspot, stripe, …) and a stable id.
• Non-secret config on the connection row — a Salesforce org id, a JIRA site URL and project key, a Zendesk subdomain, a Dynamics environment URL.
• Secrets kept separately in the encrypted credential store, keyed <type>:<id> and scoped to your tenant.

Isolation#

Connections are per-tenant. A connector's HTTP session is bound to one tenant and one connection, so auth never bleeds across orgs. Credentials are read at use time, never cached across tenants, never returned by any read API, and scrubbed from errors.

The directory#

The console's Connections screen is a read-time union of your Salesforce orgs and your connector connections, with each one's capabilities (stream-capable, load-capable), auth method, and health. Different products read different slices of it — the Stream org filter sees the stream-capable subset; the Load wizard sees the load-capable, verified subset.