> 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/enterprise-implementation-guide/phase-3-gain-visibility.md). # Gain visibility by importing repositories How to gain visibility by importing Projects so Snyk monitors your code, dependencies, containers, and infrastructure {% 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 %} ## Gain visibility by importing repositories Gaining visibility over your Organization security begins with importing Projects. This process allows Snyk to monitor your code, dependencies, containers, and infrastructure. Complete [Create your Snyk structure](/implementation-guides/enterprise-implementation-guide/create-your-snyk-structure.md) before you start this phase. You also need an Organization to import into and an account with the **Add Project** permission for that Organization, such as Org Admin or Org Collaborator. There are several ways you can import Projects, depending on your tech stack and package managers: * **SCM integration:** Recommended for automatic scanning and developer workflows. * **Snyk CLI:** Recommended for granular control in CI/CD pipelines. * **Snyk API:** Recommended for large-scale, programmatic automation. {% embed url="" %} Import your first Projects video guide {% endembed %} ### Import Projects using an SCM integration Use this method to connect repositories for automatic scanning. This is the preferred way for teams who prioritize ease of use. {% hint style="success" %} **Key decision**: Determine the scale of your import. Use the web UI for under 100 repositories; use the `snyk-api-import` tool for hundreds or thousands of repositories to mirror your source control structure. {% endhint %} To do this: 1. In the Snyk web UI, select your Organization in the scope selector, then navigate to **Settings** > **Integrations** > **All integrations**. 2. Connect to your SCM code repositories using the specific tile. 3. Configure the integration settings: * Disable automatic fixes and PR/Merge checks during initial onboarding. * Enable these features after reaching a steady state. 4. Select **Projects** in the side menu and click **Add projects**. 5. Monitor results directly in your SCM repositories. The import succeeds when each repository you selected appears as a Project in the **Projects** listing and Snyk reports its issues. {% hint style="info" %} Snyk recommends that any monorepos are imported into separate individual Organizations, rather than being split or imported between multiple Orgs. {% endhint %} ### Import Projects using Snyk CLI The Snyk CLI provides granular scanning and is typically implemented in build scripts before deployment. {% hint style="success" %} **Key decision**: Decide whether to use `test` to break builds based on severity thresholds or `monitor` to report vulnerabilities passively. {% endhint %} 1. Install the CLI as part of your build script. 2. Navigate to the Project directory. 3. Run the scan command for your Project type: * Code: `snyk code test --org=org-id` * Open Source: `snyk test --all-projects --org=org-id` 4. Review results locally or in the Snyk web UI. The scan succeeds when the command returns its results in the terminal. If you also run `snyk monitor`, the Project appears in the **Projects** listing. ### Import Projects using Snyk API Use the API to trigger scans and handle results programmatically across a large portfolio. {% hint style="success" %} **Key decision**: Identify which pipelines require real-time issue identification at scale. {% endhint %} 1. In the Snyk web UI, navigate to **Settings** > **Organization settings** > **Service accounts** and generate an API token. 2. Call the Snyk API in your pipelines. 3. Handle the results programmatically to trigger downstream actions. The import succeeds when the [Import targets](https://docs.snyk.io/developer-tools/snyk-api/reference/import-projects-v1) call returns `201` with a URL to poll, and polling **Get import job details** returns `success: true` for each manifest processed. ### Add Projects tags and attributes After importing Projects, use Project attributes and tags to categorize your data. This metadata allows you to filter and report on specific subsets of your Organization. For example, apply the `frontend` attribute and a `Team:Unicorn` tag to your Projects. You can then generate a report specifically for critical frontend vulnerabilities in production owned by Team Unicorn. Attributes and tags also allow you to: * Group related Projects for easier management. * Customize how you view and access Project data. --- # 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/enterprise-implementation-guide/phase-3-gain-visibility.md?ask=&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.