# Structure your account

## Plan your Organization structure

{% hint style="success" %}
**Key decision:** Select the structure (team, product, or SCM-based) that best supports how you want to manage policies, report vulnerabilities, and define user access.
{% endhint %}

Snyk Organizations (Orgs) are the primary level for managing Projects and user access. Align your Org structure with your business, development, or security reporting needs.

| Structure                  | Description                                                                                               | Recommended for                                                                               | Avoid if                                                                            |
| -------------------------- | --------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| **Team-based**             | Linked to a specific developer or security team.                                                          | Strict security ownership and reporting by team.                                              | Multiple teams need access to the exact same set of projects (leads to complexity). |
| **Product-based**          | Set up for distinct applications or product lines (for example, product a front-end, product a back-end). | Product-centric reporting and access control.                                                 | You have hundreds of small, unrelated products.                                     |
| **SCM Organization-based** | Mimics your SCM hosting platform structure (for example Github orgs, Gitlab groups).                      | Automated onboarding using the Snyk API, when you have more than 10 SCM-related integrations. | Your SCM organization names are not intuitive or don't align with business units.   |


---

# 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/enterprise-implementation-guide/create-a-template-organization/structure-your-account.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.