> 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/implementation-guides/team-implementation-guide/phase-2-configure-your-organization.md).

# Phase 2: Configure your Organization

Phase 2 of the Snyk team implementation: name and configure your Organization and its integrations

### Name your Organization

This step is easiest performed prior to purchasing the license. If you did not, Snyk support can assist you.

#### Changing the name prior to purchase

Open the **Organization** dropdown in the scope selector and click **+ Create new Organization**. Then purchase a Team plan for the new Organization.

#### Changing the name after purchase

After you determine the name of your Organization in phase 1, navigate to **Settings** > **Organization settings** > **General**, update the **Organization name** box, and click **Update**.

{% hint style="info" %}
You must contact Snyk support and submit a ticket to update the url slug. This can impact any existing CI/CD scripts that your team has previously created, so this step should be performed as early as possible and be communicated to your team if CLI has been in use for a while.
{% endhint %}

### Additional settings to consider

* Enable Snyk Code, if purchased, in **Settings** > **Products and features** > **Snyk Code**.
* Require a reason to ignore issues in the **Ignores** section of **Settings** > **Organization settings** > **General**.
* Disable notifications at the Organization level in **Settings** > **Organization settings** > **Notifications**. You can re-enable notifications after importing in the later step. This reduces noise during early testing/importing and is more appropriate for a steady state of the implementation.

#### License policy (optional)

Snyk comes with a default policy. You can find this under **Group** > **Policies** > **License policies** > **Snyk Default License Policy**.

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

By default, Snyk determines the severity of licenses as follows:

* High severity - licenses that present issues for commercial software.
* Medium severity - licenses that have clauses that may be of concern and should be reviewed.

Configure policies to match your requirements.

For details, see [Getting Started with Snyk License Compliance Management](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-open-source/scan-open-source-libraries-and-licenses/snyk-license-compliance-management).


---

# 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/implementation-guides/team-implementation-guide/phase-2-configure-your-organization.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.