This file has been truncated. show original
description: Channels allow you to dynamically change the deployment logic and lifecycle of a project based on the version being deployed.
As you deploy your projects, you can assign [releases](/docs/managing-releases/index.md) of projects to specific channels. This is useful when you want releases of a project to be treated differently depending on the criteria you've set. Without channels, you could find yourself duplicating projects in order to implement multiple release strategies. This would, of course, leave you trying to manage multiple duplicated projects. Channels lets you use one project, with multiple release strategies.
Channels can be useful in the following scenarios:
- Feature branches (or experimental branches) are deployed to test environments but not production.
- Early access versions of the software are released to members of your early access program.
- Hot-fixes are deployed straight to production and then deployed through the rest of your infrastructure after the fix has been released.
When you are implementing a deployment process that uses channels you can scope the following to specific channels: