> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/dashboards/policies.md).

# Policies

The policy dashboard provides an overview of the policies monitored by AppControl for your apps. Policies are monitored automatically by AppControl for each deployed revision by performing a set of checks against your app. These checks are based on policy rules for security, quality, maintainability, and development standards. By default AppControl checks your app against a library of community best practices maintained and developed by Blue Storm. This default configuration is the called the global policy.

It is possible to configure policies that are specific to your needs. The following policies can be configured:

* **Global Policy.** This policy applies to all apps managed by AppControl.
* **Group Policy.** This policy applies to all apps in a specific group.
* **App Policy.** This policy applies to a specific app.

Note: Only a single policy is used to check an app. Policy rules are inherited (Global -> Group -> App), and it is possible to make rules mandatory so that they cannot be overriden by a lower level policy.

For information on how to configure policies see the [policy administration](#policy-configuration) page in this documentation. The following information is available in the policy dashboard overview.

<details>

<summary>Environment Selector</summary>

Select the environment type that you wish to view the policy status for for. The default is 'Production'.

</details>

<details>

<summary>Policy Overview</summary>

For each deployed app with an environment that matches the environment type that you selected there is a single row in the overview. If an environment is not visible it means that the app does not have an environment of the type you have selected.

**Note:** If 'not yet processed' is displayed for an environment, it means that the policies for that enviornment have not yet been checked. This typically happens in the period after a new revision has been deployed to an environment. If this message remains for more than a few hours, check the Support tab to see if there are any processing errors for your environment.

For each app the following information is displayed:

* App. The name of the app.
* Revision. The branch and revision that was analyzed for the policy.
* Security / Maintainability / Quality / Standards. The total number of low, medium, and high risk policy checks that failed for the given check category.
* Policy Compliance. A summary of the total policy checks that failed for this app. The percentage shows the percentage of checks that were configured in the policy that passed. The star rating is a simple visualization of this percentage where 100% = 5 stars.

</details>

Click on an app to view the details of the policy results.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bluestorm.io/dashboards/policies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
