> 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/developer-tools/integrations/scm-integrations/workspaces.md).

# Workspaces

How Snyk Workspaces improve the accuracy and reliability of SCM integration results in large enterprises

Workspaces represents a significant step forward in providing you with the most reliable and accurate vulnerability detection possible.

{% hint style="info" %}
Workspaces improve the accuracy and reliability of Snyk’s SCM integration results, especially for large-scale enterprise environments. This capability also supports additional functionality and improvements we have planned in the future. For these reasons, Snyk strongly recommends [enabling this option](#manage-workspaces) by default at your Group level.
{% endhint %}

Traditionally, Snyk has accessed repository contents using SCM APIs, which impose primary and secondary rate limits, and content limits. For example, the GitHub.com APIs are rate-limited to allow only a certain number of requests per hour, and there is a limit on the number of tree entries that can be retrieved from the Git database.

When repository contents are retrieved over these APIs, these limitations inhibit Snyk’s providing a complete analysis in a number of ways, especially across a very large number of repositories, or for repositories containing more than 100,000 files, sometimes referred to as monorepos.

Through Workspaces, these limitations are removed.

The accuracy of results is improved in a number of ways through cloning. Since Snyk can access a complete view of a source code repository at a specific commit SHA, including repositories containing more than 100,000 files, the analysis is also more complete through cloning.

## Snyk data ingestion

When Workspaces is enabled, Snyk will ingest, through configured SCM integrations, a temporary and shallow clone of repository contents at a given commit and all commit metadata (including the commit message, authors, and timestamp).

{% hint style="info" %}
For more information on Snyk data processing and safeguards concerning Git repo cloning, see [Cache retention period related to vulnerability source data](https://docs.snyk.io/snyk-data-and-governance/how-snyk-handles-your-data#cache-retention-period-related-to-vulnerability-source-data) and [Snyk integrations: workspaces](https://docs.snyk.io/snyk-data-and-governance/how-snyk-handles-your-data#snyk-integrations-workspaces).
{% endhint %}

## Git protocols used by Workspaces

Repositories are cloned using HTTPS. SSH-based clones are unavailable.

## Manage Workspaces

You manage Workspaces in the **Workspaces** section of the **Integration Settings** page, at the Group or Organization level. You must be a Snyk Group Admin or Snyk Organization Admin. To turn on Workspaces, click **Enable for group** or **Enable for organization**. After you turn on Workspaces, you cannot turn it off.

If your Group or Organization turned off Workspaces in the past, Workspaces stays off until you turn it on.

When you turn on Workspaces at the Group level, every Organization in the Group inherits the setting, unless the Organization has its own Workspaces setting.

{% hint style="warning" %}
An Organization-level setting always takes precedence over the Group-level setting. If an Organization turned off Workspaces in the past, Workspaces stays off for that Organization even after you turn it on for the Group. To turn on Workspaces for that Organization, turn it on at the Organization level.
{% endhint %}


---

# 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/developer-tools/integrations/scm-integrations/workspaces.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.