# Name your Organization

Organizations contain your scan, setup integrations, and view results.

The first step is to set the name of your Organization to be used by Snyk and others when referring to Snyk.

## Introduction to structure

<div align="left"><figure><img src="/files/7j3M4NDbZE1ny7zNzp4Q" alt="Determine your account structure"><figcaption><p>Determine your Snyk account structure</p></figcaption></figure></div>

Snyk uses a hierarchical approach to managing assets, access, and rollup reporting.

* **Snyk Tenant:** A Tenant encompasses the entire Snyk workspace of your company, team and individual users. It is typically named after your company.
* **Snyk Group:** This is the top entity used to group Organizations. Groups are typically named after your company or line of business.
* **Snyk Organizations**: below the Group level, typically representing:
  * Line of business
  * Git organization or team structure
  * Types of application
  * Development teams
* **Snyk Projects:** The targets you have tested/monitored with Snyk, such as a CLI scan, a container being monitored in registry, or open source files identified.

All customers have a Group and at least one Organization. On the Free and Team plans, you can create up to five Organizations in your Tenant. On the Enterprise plan, you can create an unlimited number of Organizations.

For more details, visit [Manage Groups and Organizations](/snyk-platform-administration/groups-and-organizations.md).

{% hint style="info" %}
If you have hundreds or thousands of repositories, consider the Snyk Enterprise plan for access to additional organizations to restrict access, separate reporting, and manageable lists to interact with.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.snyk.io/implementation-and-setup/team-implementation-guide/phase-1-discovery-and-planning/name-your-organization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.