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

# License policies

Group administrators can set license policies to define Snyk behavior for handling license issues. For example, you can allow or disallow packages with certain license types to avoid using packages containing incompatible licenses.

You can [create a license policy and rules](/scan-fix-and-prevent/prevent/policies/license-policies/create-a-license-policy-and-rules.md) for your Group.

An initial policy is created automatically and set as the default to help you get started quickly with license policy management.

This default policy is a baseline to meet the requirements of multiple types of applications, such as SaaS, distributed, and so on, and may be used as a starting point to calibrate additional license policies.

The default license policy contains the standard Snyk Default License Policy, but you can edit the rules to suit your preferences.

{% hint style="info" %}
The default policy does not endorse or criticize any license and should not be treated as legal guidance.
{% endhint %}

Any new Organization created in your Group is automatically added to the default policy. When an Organization is created, it can be moved to a different policy.

For more information, see [Open Source Licenses: Types and Comparison](https://snyk.io/learn/open-source-licenses/).


---

# 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/license-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.