# Private Code Repositories

## Configure access to private code

Private code configuration requires credentials to access the private code. This may include a combination of access token, username, certificates depending on the SCM platform. In general, the configuration has two steps

<figure><img src="/files/oTvR87VYBwbkMxQcjCNm" alt=""><figcaption></figcaption></figure>

### Step 1: Details

* Add credentials to access the private code. This may include a combination of access token, username, certificates depending on the SCM platform.
* By clicking Test Connection, the connection will be tested against the credentials.

### **Step 2: Review**

* All the repositories associated with credentials will be displayed
* Either a branch or tag can be selected for the each code repository
* Project name and version will be auto generated based on repo name and branch/tag. It can be edited.
* Click on Save Configuration to generate project.

![](/files/eAPBHovwi2futPQhJA2I)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.veedna.com/sbom360-osm/generate-an-sbom/source-code-management-scm-as-source/private-code-repositories.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.