> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/manage-scanning.md).

# Manage Scanning

The **Manage Scanning** tab of Code Analysis is where you choose which repositories and projects are scanned, and where you reach their connection, discovery, schedule and pull-request settings. Review the resulting branches and findings in the other Code Analysis tabs.

Open it from **Workspaces** → **Code Analysis** → **Manage Scanning** in the sidebar.

{% hint style="info" %}
Requires the **Code Analysis** licence.
{% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FYGKKXbdexv0t2QzZQgS0%2Fv2-code-manage-scanning.png?alt=media&amp;token=edcaace3-6c14-436a-8e41-be1d47322ffc" alt="Manage Scanning on the GitHub tab with the setup status, Manage menu and repository tiles"><figcaption><p>Manage Scanning</p></figcaption></figure>

## Sources

Choose the source tab: **Bitbucket**, **GitHub** or **Design Center**. Each tab has the same layout.

## Setup status

The panel at the top shows the next setup step for the source, or that it is complete (for example **GitHub is connected and scans are scheduled**). Its button opens the step, for example:

| Step                                                     | Button                                                                                         |
| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| The source is not turned on                              | **Turn on Bitbucket** / **Turn on GitHub**                                                     |
| The OAuth app is not registered, or the last sync failed | **Configure Bitbucket access** / **Configure GitHub access**                                   |
| Access is not authorized, or was revoked                 | **Authorize Bitbucket access** / **Authorize GitHub access** (the provider opens in a new tab) |
| Repositories are in but no scan is scheduled             | **Configure scan schedules**                                                                   |
| Design Center needs its organizations or connection      | **Configure Anypoint connection** / **Configure Design Center connection**                     |

The **Manage** (or **More**) menu opens the other settings of the source:

* **Bitbucket connection & discovery** / **GitHub connection & discovery**, or **Design Center connection**.
* **Scan schedules**.
* **Pull-request scanning** (Bitbucket only).

These open the same drawers as [Setup](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/setup.md)

.

## Connect Design Center

Design Center projects are scanned with their own Anypoint connected app. Set it up from the **Design Center** tab.

1. Connect Anypoint Platform and run the **Anypoint Sync** first: projects are filed under the Anypoint business groups they belong to. Until the sync has brought them in, the setup status shows **Run the Anypoint Sync first** with **Configure Anypoint connection** (see [MuleSoft Anypoint Platform](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/supported-platforms/mulesoft-anypoint-platform.md)).
2. In Anypoint Platform, open **Access Management** and create a connected app of type **App acts on its own behalf (client credentials)** in the root organization. Give it Design Center access (**Design Center Developer**) for the organization whose projects you want scanned. You can reuse the Anypoint inventory sync's app if it already has that access.
3. On the **Design Center** tab, click **Configure Design Center connection**. Once connected, it is under **More** → **Design Center connection**. The **Connect Design Center** drawer opens.
4. Fill in the fields and click **Save**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FRxCMj6aidkjE16BZarOD%2Fv2-code-design-center.png?alt=media&amp;token=b5c37e45-0cd2-4701-ba86-3096b2739a32" alt="Connect Design Center drawer with the connected app steps, Client ID, Client secret and Owner ID"><figcaption></figcaption></figure>

| Field             | Description                                                                                         |
| ----------------- | --------------------------------------------------------------------------------------------------- |
| **Client ID**     | The connected app's client ID. Stored encrypted; once saved, leave it blank to keep it.             |
| **Client secret** | The connected app's secret. Stored encrypted; once saved, leave it blank to keep it.                |
| **Owner ID**      | Required. The Anypoint user ID that owns the Design Center projects. It is not the organization ID. |

There is no test button: your agent signs in to Design Center on the next project sync, and the projects appear when it succeeds. Next, click **Configure scan schedules** to schedule the Design Center project sync and scans; each business group gets its own.

{% hint style="warning" %}
You need a role that can create and edit global settings to save the connection, and the **Code Analysis** licence.
{% endhint %}

## Repository tiles

| Tile                       | Description                                                                                |
| -------------------------- | ------------------------------------------------------------------------------------------ |
| **Repositories**           | Repositories matching this source and the search.                                          |
| **Enabled for scanning**   | Repositories eligible for scanning. Eligibility does not mean an assessment has completed. |
| **Excluded from scanning** | Repositories explicitly excluded.                                                          |

Click a tile to filter the list.

## Automatic repository scanning

On the **Bitbucket** tab, **Automatic repository scanning** uses your existing Bitbucket connection. Turn on **Automatically scan all repositories** to scan all current and future repositories of the connection, or leave it off to keep a selected list. The panel shows the connection, the organization and whether **All-repository scanning is active** or **All-repository scanning is off**.

{% hint style="warning" %}
You need a role that can manage connections and configure jobs to change automatic scanning.
{% endhint %}

## Repository selection

| Item                                 | Description                                                                                                 |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------- |
| **All** / **Enabled** / **Excluded** | Filters the list by eligibility, with counts.                                                               |
| Search                               | **Search repositories** by name.                                                                            |
| **Export**                           | Downloads this page of repositories as CSV. Refresh reloads the list and Columns chooses the columns shown. |
| **Repository**                       | Name. **Open application dossier** opens the dossier of a scanned repository.                               |
| **Scan eligibility**                 | **Enabled** or **Excluded**.                                                                                |
| **Organization / environment**       | The organization the repository belongs to and its environment.                                             |
| **Updated**                          | When the record last changed.                                                                               |

### Enable or exclude repositories

1. Tick the repositories. Selections can span pages; changing the search or eligibility clears them.
2. Click **Enable selected** or **Exclude selected**.
3. To enable: choose the **Organization for selected applications**. Optionally turn on a one-time scan (with a connection) or a repository scan schedule.
4. Click **Confirm scan eligibility** (or **Confirm exclusion**).

Click **Clear selection** to untick everything. Excluding a repository stops future scans of it and its branches; its existing assessment evidence is kept.

{% hint style="warning" %}
You need a role that can configure jobs to select, enable or exclude repositories.
{% endhint %}

## Next Steps

* [Branches & Baselines](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/branches-and-baselines.md): review the branches of the scanned repositories.
* [Pull Requests](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/pull-requests.md): review scanned pull requests.
* [Schedules](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules.md): follow the scans that run.
* [Code Analysis](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis.md): back to the workspace.


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/manage-scanning.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.
