# Policy Evaluations

When a configured policy is not followed, the associated GitHub Actions workflow run will be blocked automatically. This helps enforce organization-wide security and compliance standards.

In such a case, you will see the following message within the workflow run:

```
The run was canceled by @stepsecurity-app[bot].
```

### Viewing Blocked Runs in the Dashboard

To investigate blocked runs, go to the “Policy Evaluations” dashboard under Run Policies in the StepSecurity platform.

This dashboard provides:

* A list of recent policy evaluation events across your organization.
* Information about the repository, workflow file, and timestamp of each event.
* The status of the run (e.g., Blocked).
* A direct link to the workflow run for deeper inspection.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2F7M0Fduzlv8glC6zlba9S%2FCreate%20GitHub%20Action%20Security%20Policies%20with%20Step%20Security%20-%20Step%2046.jpeg?alt=media&#x26;token=81aa0f14-b131-4e06-9c6e-c9044de88caa" alt=""><figcaption><p>Policies Evaluations dashboard</p></figcaption></figure>

### Understanding Why a Run Was Blocked

Click the arrow next to any listed evaluation to expand detailed information about:

* The specific policy or policies that were violated (e.g., *Do not allow GitHub-Hosted Runners*).
* The reason the run was blocked, based on the conditions defined in the policy (e.g., the job was configured to run on ubuntu-latest, which violates the organization’s policy against using GitHub-hosted runners)

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FQ5p1bTAHmXH1klincw93%2FCreate%20GitHub%20Action%20Security%20Policies%20with%20Step%20Security%20-%20Step%2048.jpeg?alt=media&#x26;token=69625798-ea61-4b4d-8a54-8bfd9c2bb435" alt=""><figcaption><p>Policies Evaluations dashboard showing more details of a failed run</p></figcaption></figure>