links:

-title:About promotions

localurl:/gitops/promotions/promotions-overview/

-title:Getting started

localurl:/gitops/promotions/getting-started/

-title:Promotion building blocks

localurl:/gitops/promotions/promotion-components/

-title:Promotion setup guidelines

links:

-title:About promotions

localurl:/docs/promotions/promotions-overview/

-title:Getting started

localurl:/docs/promotions/getting-started/

-title:Promotion building blocks

localurl:/docs/promotions/promotion-components/

-title:Promotion setup guidelines

1.[User permissions]({{site.baseurl}}/docs/administration/account-user-management/gitops-abac/)

Users need permissions to create Promotion Workflows, configure promotion settings for products, and trigger promotions.

1.[Create Environments]({{site.baseurl}}/docs/environments/create-manage-environments/#create-environments)

1.[Create environments]({{site.baseurl}}/docs/environments/create-manage-environments/#create-environments)

Environments define the starting point and destination of promotions.

A promotion requires at least two environments:

* Trigger environment, the source of the changes being promoted

[About promotions]({{site.baseurl}}/docs/promotions/promotions-overview/)

[Promotion building blocks]({{site.baseurl}}/docs/promotions/promotion-components/)

[Promotion quick starts]({{site.baseurl}}/docs/gitops-quick-start/create-app-ui/)

[Trigger promotions]({{site.baseurl}}/docs/promotions/trigger-promotions/)

[Tracking product releases]({{site.baseurl}}/docs/promotions/product-releases/)

When a product is promoted manually or automatically, the promotion mechanism create a release for the product with a unique Release ID. The release provides a graphical representation of the promotion orchestration across the environments defined for it.

When a product is promoted manually or automatically, the promotion mechanism create a release for the product. The release provides a graphical representation of the promotion orchestration across the environments defined for it.

The visualization includes the Pre- and Post-Action Promotion Workflows within the environments, more specifically, the steps within the workflows.

{% include

Watch this video to see a promotion in action:

{::nomarkdown}<img src=../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/}[Drag-and-drop Promotion](https://www.youtube.com/watch?v=4isYoutmRco&t=1s){:target="\_blank"}

Watch this video to learn how to configure an automated Promotion Flow:

{::nomarkdown}<img src=../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/}[Promotion Flows](https://www.youtube.com/watch?v=M8G-AY7FIIg&t=76s){:target="\_blank"}

Codefresh extends Argo CD’s deployment modelfby introducing structured promotionflow with additional context and automation:

Codefresh extends Argo CD’s deployment modelby introducing structured promotionflows with additional context and automation:

***Declarative and version-controlled**

Every promotion is tracked in Git, tied to a commit, ensuring full traceability. Teams can see who approved or triggered a promotion and why.

Every promotion is tracked in Git, tied to a commit, ensuring full traceability. Teams can see who triggered a promotion and why.

***Context and visibility**

While Argo CD manages deployments at the application level, Codefresh GitOps goes beyond thiswith:

While Argo CD manages deployments at the application level,promotions withCodefresh GitOps goes beyond thisoffering:

***Environments**:

Represent stages in the software lifecyle, allowing teams to easily track application progression.

Read more on[Environments]({{site.baseurl}}/docs/dashboards/gitops-environments/).

%}

GitOps promotions require Runtime version 0.13.4 or higher. Ensure your runtime is updated to access promotion features.

Promotions in Codefresh GitOps require Runtime version 0.13.4 or higher. Ensure your runtime is updated to access promotion features.

CodefreshGitOps provides specialized functionality to streamline and automate promotions while maintaining consistency and control without the need for custom scripts. These capabilities enable predictable reusable delivery lifecycles with built-in validations, reducing operational overhead.

Codefresh GitOps provides specialized functionality to streamline and automate promotions while maintaining consistency and control without the need for custom scripts. These capabilities enable predictable and reusable delivery lifecycles with built-in validations, reducing operational overhead.

***Predefine properties to promote**

Control which application properties are promoted to avoid unnecessary changes.

See[Configuring version and promotable properties forProducts]({{site.baseurl}}/docs/products/promotion-version-properties/).

See[Configuring version and promotable properties forproducts]({{site.baseurl}}/docs/products/promotion-version-properties/).

***Enforce environment-specific checks**

Automate validations, compliance, and performance checks for different environments at different stages of promotions.

*[Multi-environment Promotion Flow]({{site.baseurl}}/docs/gitops-quick-start/multi-env-sequential-flow/)

***Advanced promotions**

*[Promotion Workflows]({{site.baseurl}}/docs/gitops-quick-start/policy-multi-env-promotion/)

*[Promotions withPromotion Workflows]({{site.baseurl}}/docs/gitops-quick-start/policy-multi-env-promotion/)

*[Environment dependencies]({{site.baseurl}}/docs/gitops-quick-start/dependency-multi-env-promotion/)

Watch this video to learn how to configure an automated Promotion Flow:

{::nomarkdown}<img src=../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/}[Promotion Flows](https://www.youtube.com/watch?v=M8G-AY7FIIg&t=76s){:target="\_blank"}

Learn how promotions work by exploring their core components. See[Promotion building blocks]({{site.baseurl}}/docs/promotions/promotion-components/).