> 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/platform-administration/snyk-broker/classic-broker/clone-an-integration-across-your-snyk-organizations.md).

# Clone an integration across your Snyk Organizations

How to reuse a brokered SCM integration across multiple Snyk Organizations by cloning it

{% hint style="info" %}
**Snyk is rolling out a new navigation.** The steps on this page describe the classic interface. If your view looks different, visit [Navigate the Snyk Web UI](https://docs.snyk.io/navigate-the-snyk-web-ui#where-things-moved) to map these options to the new interface.
{% endhint %}

## Clone an integration across your Snyk Organizations

You can choose to use the same brokered Git integration across multiple Organizations in Snyk by copying and duplicating the Organization you have already configured.

For example, you can integrate Snyk Organizations X, Y, and Z with your single Git repo X.

To clone Organization configurations, you must have teams and groups enabled.

1. From the **Organization** list, choose an Organization in the Group that you are working with.\ <img src="https://1005789498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgtgtomLQ2TUgSKOMSAm%2Fuploads%2Fgit-blob-c8f66d013a9e786c46bb9fab56d7ca38c7aca8eb%2Fswitch_org_02oct2022.png?alt=media" alt="Choose Organization" data-size="original">
2. From the same **Organization** dropdown, click **+Create new Organization.**

   <figure><img src="https://1005789498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgtgtomLQ2TUgSKOMSAm%2Fuploads%2Fgit-blob-d0dfc17caf5d7dbaa08bf31c8095db056addc7ef%2Fclone-organization1_02oct2022.png?alt=media" alt="Select +Create new Organization"><figcaption><p>Select +Create new Organization</p></figcaption></figure>
3. In the next window, enter a name for your new Organization.
4. In the **Copy settings from an existing org** section, choose an Organization that you have already configured for the Broker token.
5. Review the summary of what will be copied across to the new Organization and click **Create organization** to confirm.

   <figure><img src="https://1005789498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgtgtomLQ2TUgSKOMSAm%2Fuploads%2Fgit-blob-fdd1d6601fc6c91853308972c273c561fea7cd1a%2Fclone-org-3screens_02oct2022.png?alt=media" alt="Review summary of what will be copied to the new Organization and Create"><figcaption><p>Review summary of what will be copied to the new Organization and Create</p></figcaption></figure>

The **Dashboard** for the Organization that you just created opens. The Broker integration is duplicated and set up, and the Broker token is identical to the token for the original Organization.


---

# 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/platform-administration/snyk-broker/classic-broker/clone-an-integration-across-your-snyk-organizations.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.
