> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superember.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Channels and connectors

> Learn how SuperEmber separates communication channels from tool and app connectors.

Channels and connectors solve different parts of the system.

Channels move work between people and SuperEmber. Connectors let SuperEmber act on external systems.

## Channels

Channels are communication surfaces.

Slack is the primary self-serve channel because teams already delegate work there. A channel can trigger work, carry context, receive questions, collect approvals, and show results.

A team can designate one channel as **Main**. Delegated work creates operation threads there, and human escalations are surfaced to the responsible team before the exact action resumes.

Microsoft Teams is represented as a preview/admin-install surface. Other supported intake surfaces can include dashboard commands, schedules, webhooks, email, connected app triggers, and messaging channels where enabled.

## Connectors

Connectors give agents and workflows controlled access to external apps.

Examples include Gmail, Slack, CRM systems, project management tools, analytics tools, and company HTTP APIs.

Connector access should be governed through scoped credentials, policy checks, approvals, and audit history.

## Why the distinction matters

A Slack message can be both a channel event and a connector action target:

* As a channel, Slack starts the work and receives replies.
* As a connector, Slack can be an app where a workflow posts a status update or reads channel context.

Keeping the boundary clear makes permissions, audit logs, and approvals easier to reason about.

## Related Pages

* [Channel support](/reference/channel-support)
* [Integrations](/product/integrations)
* [Connect tools](/guides/connect-tools)