---
title: "Approve once or reject a blocked deployment from Slack | Proofline Help"
description: "Use the approval request in the delivery channel to decide a GitHub Actions deployment that is waiting on Proofline’s protection rule. Confirm the repository and commit before deciding."
url: https://proofline.sh/help/deployment-block-decision-slack/
---

[Help center](/help/)

# Approve once or reject a blocked deployment from Slack

Use the approval request in the delivery channel to decide a GitHub Actions deployment that is waiting on Proofline’s protection rule. Confirm the repository and commit before deciding.

## Record a decision for this deployment attempt

When a deployment review blocks a GitHub Actions deploy that waits on Proofline's protection rule, Proofline posts a **Deployment blocked** card to the [Slack delivery channel](/help/connect-slack/#choose-the-channel). Cloud Build gates and deploys that the review allows post no card.

The card names the repository, environment and commit, lists up to eight supported findings, and states the decision basis. Depending on the review policy, it also shows the decision's coverage or what Kian counted. When a monthly [spend limit](/help/billing/#set-spend-limits) stopped the deployment review, the decision basis says so and links Billing through **Raise the limit in Billing**. Protected environment values are withheld from the card. **Review risks on GitHub** opens the review's GitHub check, which holds every finding.

To decide from the card:

1.  Select **Approve once** or **Reject deployment**, then select **Continue**.
2.  In **Deployment decision**, enter a **Reason** of 3 to 2,000 characters.
3.  Select **Record decision**.

**Approve once** lets this workflow run's deployment proceed; the next deploy is reviewed again, and the automated block remains in the audit record. **Reject deployment** tells GitHub to stop the waiting deployment.

Anyone in the delivery channel can decide. Proofline does not require a linked Slack account or check a Proofline role. It accepts a decision only while the deployment is still blocked, from the connected workspace's current delivery channel, and from the person who opened the dialog. The first recorded decision stands; a later one shows **This deployment already has a recorded action or is no longer actionable.** After you choose another channel or disconnect Slack, the buttons on earlier cards stop working.

The card then replaces its buttons with the decision, the person who made it, when, and their reason. It says **Waiting for GitHub to accept it** until GitHub does, then its heading changes to **Deployment approved once** or **Deployment rejected**. If GitHub refuses the decision, for example because the workflow run was cancelled or timed out, the card says that GitHub did not accept it and why, and the deployment stays blocked; rerun the deployment to decide again. On GitHub, Proofline approves or rejects its protection rule for that environment on the workflow run, with the comment `Proofline Slack decision by <Slack username>: <reason>`. When the review has a GitHub check, the comment ends with a **View findings** link to it.

Someone can also override the block on GitHub, for example with **Start all waiting jobs**. Proofline records the override once the workflow run completes. The card then drops its buttons and its heading changes to **Deployment block overridden**. It names the GitHub user, when Proofline recorded the override, and their comment.

## Related guides

-   [Configure deployment protection](/help/deployment-protection/)
-   [Create an environment](/help/create-environment/)
