> 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/create-policies.md).

# Create policies

Snyk Essentials includes a powerful policy editor for creating and modifying policies.

There are two steps to building policies:

1. [Define filters](#define-filters) - Set filter conditions on asset properties.
2. [Set actions](#set-actions) - Define actions to be taken on filtered assets.

## New policy

You can create a new policy using the **Start from scratch** option or choose one of the available policy templates using the **Use a template** option.

### Start from scratch - policy creation

To create a new policy, you have to click the **New Policy** option from the Policies/Assets view and select the **Start from scratch** option.

You must name your policy and, optionally, provide a description of the policy. After you complete these steps you have to [define the filters ](#define-filters)and [set the actions](#set-actions) of your policy.

### Use a template - policy creation

You can create a new policy by using one of the available templates. To select one of the policy templates, you have to click the **New Policy** option from the Policies/Assets view and select the **Use a template** option. You can select one of the templates from the templates library by clicking the **Use template** button from the policy template card.

Each policy template has a name, a description, and displays the graphic connections between filters and actions.

You can customize the filters and actions or use the template as is. After finishing all the template changes, click the **Save** button to create the new policy.

## Define Filters

{% hint style="info" %}
**Release status**

The risk factors on assets are taking the release status of the applied [risk factor](/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/assets-and-risk-factors.md#risk-factors).

The Runtime discovered and Runtime last seen filters are taking the release status of the used runtime integration.
{% endhint %}

You must specify an asset property for each filter component. For all available properties for asset policies, see [Asset inventory filters](/scan-fix-and-prevent/fix/assets-inventory-filters.md).

You can specify more than one filter component with an **And** or **Or** operator.

## Set actions

After defining filter components, you need to define the actions that the policy has to perform on the filtered assets. Asset policies support the following actions:

* **Send Email** - Receive an email every time there are asset updates. You can choose between daily emails or scheduling the checks. You can include a link to the relevant assets. Each notification lists all impacted assets. You can view them individually or see the aggregated view by clicking **Click Here**. The list of assets displayed in the email notification is automatically generated.
* **Send Slack Message** - Receive a Slack notification every time there are asset updates. You need to add your [Slack webhook URL](/developer-tools/integrations/jira-and-slack-integrations/slack-integration.md), then you can choose between daily emails or scheduling the checks. You can include a link to the relevant assets. Each notification lists all impacted assets. You can view them individually or see the aggregated view by clicking **Click Here**. The list of assets displayed in the email notification is automatically generated.
* **Set Asset Class** - Sets the class on the matched assets. Removing the policy or turning in off does not retroactively change the asset class back to default.
* **Set Asset Tag** - Sets a tag on the matched assets. Removing the policy or turning in off will remove the tags of this policy from the relevant assets.
* **Set Coverage Control Policy** - Sets a control on filtered assets that checks whether selected security products are scanning assets, optionally within a given timeframe. Assets that fail this control will be marked accordingly on inventory pages. This control applies the OR logic across products.

The editor supports multiple flows for the same policy. The flows can be independent or intersect.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snyk.io/scan-fix-and-prevent/prevent/policies/assets-policies/create-policies.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.