Recommended for testing purposes and not as the preferred method.

For how-to instructions, see[Manually assign unassigned applications]({{site.baseurl}}/docs/products/configure-product-settings/#manually-assign-unassigned-applications).

You can always unassign an application from a product, for declaratively assigned applications by removing the annotation, and for manually assigned applications, by removing them through[Product Settings](products/configure-product-settings/#unassign-manually-assigned-applications).

You can always unassign an application from a product, for declaratively assigned applications by removing the annotation, and for manually assigned applications, by removing them through[Product Settings]({{site.baseurl}}/docs/products/configure-product-settings/#unassign-manually-assigned-applications).

In Product > Settings > Promotion Flows, you can select one or more Promotion Flows for theprodcut, and then configure custom conditions to trigger the flows.

See also[Promotion Flow CRD](#promotion-flow-crd).

In Product > Settings > Promotion Flows, you can select one or more Promotion Flows for theproduct, and then configure custom conditions to trigger the flows.

See also[Promotion Flow CRD]({{site.basurl}}/docs/promotions/configuration/yaml/promotion-flow-crd/).

{% include

image.html

%}

For how to instructions on configuring Promotion Flows, see[Configure Promotion Flows]({{site.baseurl}}docs/products/manage-products/configure-product-settings/#configure-promotion-flows).

For how to instructions on configuring Promotion Flows, see[Configure Promotion Flows]({{site.baseurl}}/docs/products/configure-product-settings.md/#configure-promotion-flows).

[Assigning applications to products]({{site.baseurl}}/docs/products/assign-applications/)

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

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

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

[Creating products]({{site.baseurl}}/docs/products/create-product/)

%}

For how-to instructions, see[Configure Promotion Settings]({{site.baseurl}}/docs/products/manage-products/configure-product-settings/#configure-promotion-settings).

For how-to instructions, see[Configure Promotion Settings]({{site.baseurl}}/docs/products/configure-product-settings/#configure-promotion-settings).

Visually design and create the flow by selecting environments, Promotion Actions, and Workflows, and defining dependencies through the Flow Builder. If needed, create new environments and promotion workflows on-the-fly when doing so.

* Review[Create a promotion sequence]({{site.baseurl}}/docs/promotions/create-promotion-sequence/)

* Review[Promotion: End-to-end guide]({{site.baseurl}}/docs/promotions/create-promotion-sequence/)

The path in the Shared Configuration Repo is`<gitops-runtime>/<shared-configuration-repo>/resources/configurations/promotion-policies/`.

See[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/) and[Designating Configuration Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#designating-configuration-runtimes).

For the YAML specifications, see[Promotion Policy YAML]({{site.baseurl}}/_docs/promotions/configuration/yaml/promotion-policy-crd/).

For the YAML specifications, see[Promotion Policy YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/promotion-policy-crd/).

| `spec.steps.policy.action` | The action that should trigger the promotion in the target environment for this Promotion Policy.<br>Can be one of the following:{::nomarkdown}<ul><li><code class="highlighter-rouge">commit</code>:Executes a commit operation on the target application.</li><li><code class="highlighter-rouge">pr</code>: Executes a commit and opens a pull request for the target application.<br>Useful when you need manual approval before commit.</li><li><code class="highlighter-rouge">none</code>: Does not execute any action on the target application.<br>In this case, the Post-Action workflow must include a step that is equivalent </li></ul>{:/}| string | Required |

|**Release ID**| The Codefresh-assigned identifier uniquely identifying the release. Clicking the Release ID displays the ongoing or completed Promotion Flow for the release.|

|**Initiator**| The user who created the release. The initiator is displayed only for releases created through automated promotions.|

|**Promotion Flow**| The name of the flow orchestrating the promotion for the specific release. Clicking the link takes you to the Promotion Flow page with a graphical representation of the flow. For details, see[Promotion Flows]({{site.baseurl}}/docs/promotions/configuration/promotion-flow/).<br>**Manual** indicates that the release was created for manually triggered single-environment promotions, from the trigger to a single target environment. See[Manual promotion triggers]({{site.baseurl}}/docs/promotions/trigger-promotions/#manual-promotion-triggers-quick-reference).|

| **Environments** | The environments promoted for the release and their deployment statuses, which can be one of the following:{::nomarkdown}<ul><li><img src="../../../images/icons/promotion-success.png?display=inline-block">: Successful</li><li><img src="../../../images/icons/promotion-running.png?display=inline-block">: Running</li><li><img src="../../../images/icons/promotion-suspended.png?display=inline-block"> or <img src="../../../images/icons/promotion-suspending-pending-pr?display=inline-block">: Suspended or suspended pending PR approval/merge.</li><li><img src="../../../images/icons/promotion-pending.png?display=inline-block">: Pending</li><li><img src="../../../images/icons/promotion-terminated.png?display=inline-block">: Terminated.</li><li><img src="../../../images/icons/promotion-failed.png?display=inline-block">: Failed</li><li><img src="../../../images/icons/promotion-failed.png?display=inline-block">: Failed</li></ul>{:/} See [Environment (deployment) status](#environment-deployment-status).|

|**Environments**| The environments promoted for the release and their deployment statuses, which can be one of the following:{::nomarkdown}<ul><li><imgsrc="../../../images/icons/promotion-success.png?display=inline-block">: Successful</li><li><imgsrc="../../../images/icons/promotion-running.png?display=inline-block">: Running</li><li><imgsrc="../../../images/icons/promotion-suspended.png?display=inline-block"> or <imgsrc="../../../images/icons/promotion-suspending-pending-pr.png?display=inline-block">: Suspended or suspended pending PR approval/merge.</li><li><imgsrc="../../../images/icons/promotion-pending.png?display=inline-block">: Pending</li><li><imgsrc="../../../images/icons/promotion-terminated.png?display=inline-block">: Terminated.</li><li><imgsrc="../../../images/icons/promotion-failed.png?display=inline-block">: Failed</li></ul>{:/} See[Environment (deployment) status](#environment-deployment-status).|

{: .table .table-bordered .table-hover}

| Environment Status| Description|

|------------|---------------------------------------|

|**Successful**| Promotion to an environment is considered successful when the following conditions are met, in the order listed. {::nomarkdown}<ol><li>Pre-Action Workflow completed successfully.</li><li>Promotion Action submitted successfully. For PRs, the PR was successfully merged.</li><li>Application synced to the cluster.</li><li><li>Application is healthy.</li><li>Post-Action Workflow completed successfully.</li></ol>{:/}.|

|**Successful**| Promotion to an environment is considered successful when the following conditions are met, in the order listed. {::nomarkdown}<ol><li>Pre-Action Workflow completed successfully.</li><li>Promotion Action submitted successfully. For PRs, the PR was successfully merged.</li><li>Application synced to the cluster.</li><li>Application is healthy.</li><li>Post-Action Workflow completed successfully.</li></ol>{:/}|

|**Running**| At least one step in a Pre- or Post-Action Workflow in the environment is currently in progress.|

|**Suspended**| One or both the Pre- and Post-Action Workflows or the Promotion Action is pending execution. This could be because of a condition in the Workflow or because a pull request is pending manual approval.|

|**Failed**| At least one step in a Workflow failed to execute, has a syntax error, was manually terminated, or the application is out of sync or degraded.|

[Promotion Flows]({{site.baseurl}}/docs/promotions/configuration/promotion-flow/)

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