> 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/accept-risk.md).

# Accept Risk

The accept risk pop-up can be accessed from the check result pop-up. This dialog enables you to accept the risk that is reported by check result. Accepted risks are not used when calculating the compliance score for an app. After accepting a risk the score for the current app is re-calculated. The next time a new revision is checked the list of accepted risks will also not be used to calculate the score.

The following options are available:

* **What do you want to accept?**
  * **Ignore specific risk** : If you select this, the currently selected combination of check type, element type, and element name will be accepted.
  * **Ignore all risks of the same type** : If you select this, all check results of this type will be accepted.
* **Comment.** Enter a comment that explains why you are accepting this risk. If the policy administrator has made it mandatory, you must enter a comment in this field.
* **Check type.** The name of the check type to be accepted.
* **Element type.** The element type to be accepted.
* **Element name.** The element name to be accepted.


---

# 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/accept-risk.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.