> 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/scan-fix-and-prevent/fix/configure-repository-monitoring.md). # Configure repository monitoring How to configure repository monitoring in Snyk {% 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 %} ## Configure repository monitoring {% hint style="info" %} **Release status** Repository monitoring configuration is in Early Access and available only with Enterprise plans. To enable the feature, visit [Snyk Preview](https://docs.snyk.io/platform-administration/snyk-hierarchy/snyk-preview). {% endhint %} ### Overview {% hint style="info" %} To perform bulk monitoring configuration and maintain visibility into the security health of all repositories, you must be a Group Admin. {% endhint %} You can manage repository coverage and monitoring configurations centrally across your entire Snyk Group from the **Inventory** page, at Group level. This means you can monitor and manage repositories without navigating between individual Snyk Organizations. Repository monitoring configuration provides the following capabilities: * Centralized asset monitoring: view monitoring status for all products, identify health status, and see required actions (such as enabling Snyk Code or resolving SCM integration issues) in one view. * Bulk import: import repositories directly from the Group **Inventory** page into specific Snyk Organizations. * On-demand retesting: trigger a retest for specific repositories directly from **Inventory**. * Actionable error resolution: clear guidance is available when testing fails due to integration issues or entitlements. After the underlying issue is resolved, testing resumes automatically. ### Configure settings for repository monitoring You can configure repository monitoring settings for your Projects across multiple repositories simultaneously. These configurations are asset-based. To do this, navigate to **Inventory** > **All Assets**, at the Group level. {% stepper %} {% step %} **Select the repositories to update** Select the repositories you want to update, then click **Configure monitoring.** {% endstep %} {% step %} **Select the configuration type** Select one of the following: * **Create new configuration (override)**: create a new configuration for the repositories you selected and override previous configurations. * **Update specific settings (partial)**: update the settings for an existing configuration. Click **Continue**. {% endstep %} {% step %} **Configure settings** On the configuration page, the following configurations are available: * **Test frequency**: update the test frequency for Open Source, Code, and Secrets Projects to **Daily**, **Weekly**, or **Never**. For Secrets, the frequency applies to recurring tests only. Scans triggered by pushes and by Pull Request checks are not affected. {% hint style="info" %} It is not possible to manage these settings at Organization level for assets tracked on the **Inventory** page. {% endhint %} * **Report to Organization**: map repositories to Snyk Organizations. To avoid duplicate issues, Snyk recommends one Snyk Organization per repository. * **Testing exclusions (optional)**: manage file exclusions for Snyk Open Source and Snyk Container Projects. Exclusions apply at the asset level. You cannot exclude specific files for the same repository in different Snyk Organizations. {% hint style="info" %} For Snyk Code, you can manage exclusions using the `.snyk` files, in order to maintain developer-first workflows. {% endhint %} Click **Continue**. {% endstep %} {% step %} **Enable monitoring** Review your configuration settings and click **Enable monitoring**. {% endstep %} {% endstepper %} #### Configure the Secrets test frequency for a single repository To set the Secrets test frequency for one repository: 1. Navigate to **Inventory** > **All Assets**. 2. Click the repository asset. 3. Open the **Settings** tab. 4. In the **Test Frequency** section, select **Daily**, **Weekly**, or **Never** for **Secrets testing**. The default is **Weekly**. #### Disable recurring testing For on-demand testing or to disable recurring testing for specific repositories: 1. Click the asset you want to disable recurring testing for. 2. In the asset card's **Settings** tab, click **Disable recurrent tests** to disable recurrent testing. To trigger a retest, click **Retest.** --- # 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/scan-fix-and-prevent/fix/configure-repository-monitoring.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.