> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/prevent/policies/assets-policies/use-cases-for-policies.md).

# Use cases for policies

Use cases for Snyk Essentials asset policies

Gain a better understanding of the policies you can use by going through the following use cases. These are only examples of some situations where policies can be applied. You can customize your policies as needed. The **Send Email** and **Send Slack Message** actions are both notifications and are treated as a single use case.

* [Coverage control](/scan-fix-and-prevent/prevent/policies/assets-policies/use-cases-for-policies/coverage-control-policy.md)
* [Coverage and Coverage gap](/scan-fix-and-prevent/prevent/policies/assets-policies/use-cases-for-policies/coverage-and-coverage-gap-policies.md)
* [Pre-set coverage control policy](/scan-fix-and-prevent/prevent/policies/assets-policies/use-cases-for-policies/coverage-and-coverage-gap-policies.md#pre-set-coverage-control-policy)
* [Classification](/scan-fix-and-prevent/prevent/policies/assets-policies/use-cases-for-policies/classification-policy.md)
* [Labeling](/scan-fix-and-prevent/prevent/policies/assets-policies/use-cases-for-policies/tagging-policy.md)
* [Notifications](/scan-fix-and-prevent/prevent/policies/assets-policies/use-cases-for-policies/notification-policy.md)

Each type of policy is accompanied by a use case, explaining a practical way of using the policy. The use cases provide a clear example of one of the possible ways of using the policy and offer details about the conditions needed for the filters and actions when building your policy.


---

# 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.snyk.io/scan-fix-and-prevent/prevent/policies/assets-policies/use-cases-for-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.