# Snyk License Compliance Management
{% hint style="info" %}
**Feature availability**
Snyk License Compliance Management is available only with Enterprise plans. For more information, see [plans and pricing](https://snyk.io/plans/).
{% endhint %}
You can check compliance for open-source licenses in your code using Snyk License Compliance Management.
The Snyk Default License Policy defines how Snyk identifies potential license issues in the open-source packages your Projects are using. This policy applies to all Organizations created in your Group.
## **Prerequisites for using Snyk License Compliance Management**
Before checking license compliance with Snyk License Compliance Management, ensure you:
* Are part of a Snyk [paid plan](https://snyk.io/plans/).
* Have integrated and imported your Projects. See [Getting started](https://docs.snyk.io/discover-snyk/getting-started).
## **Define license policies**
To take effective action based on license issues, you need to define policies that specify these actions for each license type. Policies provide a way to capture different requirements within an Organization based on factors such as line of business. Work with your legal team to create policies tailored to your company.
To open your Snyk Group License policy, navigate to the **Policies** menu option in your Group.
### Create policy rules
Each policy contains rules detailing which licenses are acceptable and which are forbidden for use, together with a severity level that indicates how severe the license violation is.
You can create and edit multiple license policies for Organizations. For details, see [Create a license policy and rules](https://docs.snyk.io/manage-risk/policies/license-policies/create-a-license-policy-and-rules).
## View compliance issues
Snyk’s [Git-based integrations ](https://docs.snyk.io/developer-tools/scm-integrations/organization-level-integrations)support license scanning as part of the regular workflow. During scanning, license issues appear as a filterable list in the **Issues** tab.
Issues overview with the "License issues" filter applied
The example below shows a high-severity issue under the GPL-2.0 license, with accompanying instructions as defined in the license's policies.
You can also view license issues using the Snyk CLI tool after running `snyk test`:
License issue overview in Snyk CLI
### **View all license information**
You can view and share detailed lists of licenses being used by all Projects in your Organization and see a report that lists all the open-source components and licenses.
### **View license dependencies**
Snyk shows license issues in both your direct and transitive dependencies in the **Dependencies** tab:
Click the tree icon to view a full dependency tree. This shows the dependency that introduced the license issue:
Dependencies overview - tree view
## **Resolve license issues**
You can now take action to resolve the license issues identified during the scan, to help you build and deploy your application without outstanding licensing issues.
The actions you take depend on the license conditions and on your policies. For example, if a license violation has surfaced, this issue can be mitigated by either approaching your legal team or by replacing the dependency that added the violation.
Alternatively, you may want to ignore the issue. For details, see [ignore issues](https://docs.snyk.io/manage-risk/prioritize-issues-for-fixing/ignore-issues).
