Connection Types and Teammate Access

A connector is the app or service Type knows how to use. A connection is the authenticated integration between Type and that app.

There are two separate concepts:

• Connection type: whether the integration is connected through one person’s account or at the organization level.
• Teammate access: which AI teammates are allowed to use that connected integration.

Personal connections

A personal connection is connected through one user’s account. It can access what that user can access in the connected app.

For example, if you connect your personal Linear account, Type can use the Linear access available to you. Personal connections are useful for tools where each user has their own permissions, such as email, calendar, documents, issue trackers, and source control.

Organization-level connections

An organization-level connection is connected for the workspace or company account. It can access the app data available to that organization-level integration.

For example, you might connect HubSpot as an organization-level integration so teammates can work with the shared CRM data. Organization-level connections are useful for shared business systems, team-wide data sources, support platforms, CRMs, and warehouses.

Global availability

When an integration is connected, it becomes available globally in Type as a connected integration. That does not mean every teammate should use it for every task.

Add connected integrations to the specific teammates that need them. A Product Engineer teammate might get GitHub and Linear. A Sales Operations teammate might get HubSpot or Salesforce. A Sidekick might get the owner’s personal Gmail, calendar, and documents.

Practical rule

Connect the right account type first: personal when the integration should reflect one user’s app permissions, organization-level when it should reflect shared company access. Then assign that connected integration only to the teammates whose role needs it.