> ## Documentation Index
> Fetch the complete documentation index at: https://docs.semgrep.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# Create and manage unified policies
This document explains how to migrate existing policies to [unified policies](/semgrep-appsec-platform/unified-policies/overview), as well as how to create new unified policies.
## Migrate existing policies
Sign in to [ Semgrep AppSec Platform](https://semgrep.dev/login).
Go to **Rules & Policies > Policies**. You will see a banner that prompts you to begin the upgrade to unified policies. Click to launch the **Upgrade to Unified Policies** dialog, and follow the on-screen prompts to proceed.
Review the policies that Semgrep has migrated for you. For each product where you have existing policies, select the **I have reviewed these migration details** checkbox to proceed.
When you have completed the migration process, you are redirected to the new **Policies** page, where you can manage your detection and remediation policies.
Note: Email notifications are not supported by Unified Policies. If you currently have an email integration set up, no additional emails will be sent after you migrate to Unified Policies.
## Manage existing detection policies
Sign in to [ Semgrep AppSec Platform](https://semgrep.dev/login).
Go to **Rules & Policies > Detection**. You can manage your policies for:
* Code rules
* Secrets rules
* Supply Chain advisories
Select the product for which you’d like to manage your Detection policy, and click **Edit**.
Find the rules and rulesets you’d like to modify. Filters allow you to narrow the list of rules based on scanning behaviors, languages, rulesets, and more. You can also search for a rule using its name or label.
To change the behavior of your rules:
i. Select the rules by clicking the checkboxes next to their names, then click **Change scanning behavior (n)**. If you're modifying only one rule, you can click the rule’s link in the **Projects scanning** column.
ii. The **Projects scanning** dialog appears. You can choose to use the rules with **All projects**, **Selected projects** by **Project name**, **Selected projects** by **Tags**, **All with exceptions**, or **None (disable)**.
iii. To use the rules with all of your projects, click **All projects**, then click **Save**.
iv. To use the rules with some of your projects, click **Selected projects**, then click the checkboxes next to the projects to which the rule applies. Click **Save** to proceed.
v. To exclude specific projects, click **All with exceptions**, then select the projects to which the rule doesn’t apply. Click **Save** to proceed.
vi. To prevent the rules from being used at all, click **None (Disable)**, then **Save** to proceed.
## Create a remediation policy
Sign in to Semgrep AppSec Platform.
Go to **Rules & Policies > Remediation**.
To create a policy that defines the automated responses to security findings:
i. Click **+ Create automation**.
ii. Provide a **Policy name**.
iii. Set the **Scope** of the policy by selecting all of the projects to which this policy applies.
iv. Define the **Conditions** that trigger the policy by clicking **+ Add condition** to expand a drop-down list of attributes that you can use. Select the attribute, then set the specific conditions.
* For example, you can select **Severity**, then complete the conditional statement provided to read **When Severity is any of Critical, High**.
* You can define as many conditions as necessary, and Semgrep treats them additively.
v. Choose the **Actions** that occur if there are findings that trigger the policy by clicking **+ Add action**. You can choose multiple **Actions**, including:
vi. Click **Create & Enable** to save and proceed, so that Semgrep uses your new policy the next time you scan a project within its scope. Otherwise, click **Create** to save your changes without enabling the policy.