> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cysmiq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure repository scanning

> Set repository ownership, default branch filters, and the analysis jobs Cysmiq runs.

Repository settings let you adapt scanning and triage defaults for one codebase. Repository-level values override inherited workspace or organization settings until you reset them.

## Prerequisites

* A connected repository in your workspace
* Permission to manage repository settings

<Info>Availability depends on your Cysmiq plan.</Info>

## Steps

<Steps>
  <Step title="Open repository settings">
    Open **Repositories** under **Assets**, select the repository, then select **Settings**.

    Keep **Enable** turned on for repositories that Cysmiq should scan. Turning it off stops Cysmiq from running analysis for that repository.
  </Step>

  <Step title="Set ownership and the default branch view">
    Select a **Default Assignee** when new findings should begin with a specific owner. This supports triage ownership and can be changed on individual findings later.

    Use **Default branch filter** to control which branches appear initially on vulnerability views for this repository:

    * Keep **Include default branch** enabled to include the repository's default branch.
    * Add exact branch names for other long-lived branches.
    * Add patterns such as `release/*` when several branches follow the same naming convention.

    <Frame caption="Repository ownership and default branch filtering for the storefront repository.">
      <img src="https://mintcdn.com/cysmiq/jILg5Q1KdyGSo81w/images/guides/configure-repository-scanning/configure-repository-scanning-01-scope.webp?fit=max&auto=format&n=jILg5Q1KdyGSo81w&q=85&s=8235f292144bfaa45da67e7b68f6a55e" alt="Repository settings showing Maya Chen as the default assignee and a default branch filter that includes main and release branches." width="1932" height="965" data-path="images/guides/configure-repository-scanning/configure-repository-scanning-01-scope.webp" />
    </Frame>

    These settings change the default view. You can still change filters when reviewing vulnerabilities.
  </Step>

  <Step title="Choose the analysis jobs">
    In **Scan jobs**, enable the analysis types that should run for this repository:

    * **SCA** discovers manifests, builds SBOM data, and checks package advisories.
    * **Provider checks** verify detected credentials with supported providers.
    * **Context assessments** assess source context when a provider check is unavailable.
    * **Secret History** searches Git history for exposed secrets.
    * **Code analysis** scans source code and runs post-processing.
    * **Call chains** analyze local functions and call paths after code analysis.

    <Frame caption="Repository scan jobs enabled with call chains limited to selected branch patterns.">
      <img src="https://mintcdn.com/cysmiq/jILg5Q1KdyGSo81w/images/guides/configure-repository-scanning/configure-repository-scanning-02-scan-jobs.webp?fit=max&auto=format&n=jILg5Q1KdyGSo81w&q=85&s=19feb136bb46fcb24c0387f02ee99d85" alt="Scan job settings showing SCA, secret checks, code analysis, and call chains enabled with main and release branches selected." width="1900" height="756" data-path="images/guides/configure-repository-scanning/configure-repository-scanning-02-scan-jobs.webp" />
    </Frame>
  </Step>

  <Step title="Scope call-chain analysis">
    Choose **All branches** when call-chain analysis should run everywhere. Choose **Specific branches** and enter comma-separated names or patterns when it should run only on selected branches.

    Call chains depend on **Code analysis**. Cysmiq disables both code analysis and Secret History for repositories marked as monorepos.
  </Step>

  <Step title="Manage inherited settings">
    Repository settings inherit workspace or organization values until you save an override. Select **Reset overrides** in a section to return that repository to inherited values.

    Configure provider check statuses and pull request decoration separately. See [VCS status updates and pull request decoration](/scanning/vcs-status-updates).
  </Step>
</Steps>

## Related documentation

* [Repositories](/assets/repositories)
* [Scan types](/concepts/scans)
* [Secret scanning](/scanning/secrets)
* [Code scanning](/scanning/code)
* [VCS status updates and pull request decoration](/scanning/vcs-status-updates)