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

# What is a channel?

export const DefinitionDescription = ({children}) => <dd className="definition-description">{children}</dd>;

export const DefinitionTerm = ({children}) => <dt className="definition-term">{children}</dt>;

export const DefinitionList = ({children}) => <dl className="definition-list">{children}</dl>;

A channel is a location where the platform looks for packages. In Anaconda Platform, channels are made available to a [perimeter](/docs/platform/concepts/what-is-a-perimeter), and the packages they provide are governed by the [policies](/docs/platform/concepts/what-is-a-policy) applied to them.

<Tip>
  For the general concept of a channel in conda, see [What is a channel?](/docs/getting-started/concepts/what-is-a-channel) This page describes how channels work within the platform.
</Tip>

## Why channels matter

Channels are how data scientists get access to packages, and how your organization keeps that access governed. Rather than pulling packages from arbitrary sources, [workloads](/docs/platform/concepts/what-is-a-workload) in a perimeter draw from the channels registered to it. This gives your teams a curated, security-reviewed set of packages to build on, and gives your organization a single place to control what those packages can be.

## How channels work in the platform

A perimeter's channels come from two sources:

<DefinitionList>
  <DefinitionTerm>
    Secure channels
  </DefinitionTerm>

  <DefinitionDescription>
    Channels from Anaconda's curated repository, containing security-reviewed packages. Every perimeter receives a default set of secure channels.
  </DefinitionDescription>

  <DefinitionTerm>
    External channels
  </DefinitionTerm>

  <DefinitionDescription>
    Package sources that have no Anaconda channel behind them, such as conda-forge. An administrator registers external channels to the perimeter that should have access to them.
  </DefinitionDescription>
</DefinitionList>

Because access follows the perimeter, every workload in a perimeter can use its channels, and no workload can use channels registered elsewhere.

Secure channels carry [policies](/docs/platform/concepts/what-is-a-policy) that filter which packages are actually available. A policy might exclude packages with known vulnerabilities, for example, so that data scientists can only install packages that meet your organization's security requirements. Policies rely on Anaconda's package security metadata, so they apply to secure channels rather than external channels. When the platform resolves packages for a workload, it draws from the perimeter's channels with those policies already applied.

## Managing channels

For setting policies and registering external channels, see [Channel governance](/docs/platform/guides/governance/channel-governance). For browsing channels and inspecting their packages, see [Packages](/docs/platform/guides/resources/packages).