# GitLab

> Connect GitLab to sanda: what to prepare, the fields the connection form asks for, and how its data lands in your warehouse.

## Connect GitLab

:::steps
1. **Open the catalogue.** In the console, go to **Data · Connections** and press **New connection**.
2. **Choose GitLab.** It is listed under product and operations; you can also search for it by name.
3. **Fill in the form.** Enter the fields below. Credentials go straight to sanda’s sync engine and are never stored in sanda’s database.
4. **Choose what to sync.** Pick the streams you want, and a sync mode for each. See [choose what to sync](https://docs.sanda-os.com.au/connections/choose-streams).
5. **Run the first sync.** sanda tests the connection, then lands each stream as a table in your warehouse.
:::

## Configuration fields

What the connection form asks for. Required fields are marked; the rest are optional.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| **Authorization Method** | one of 2 options | Yes |  |
| **Start Date** | string | No | The date from which you'd like to replicate data for GitLab API, in the format YYYY-MM-DDT00:00:00Z. Optional. If not set, all data will be replicated. All data generated after this date will be replicated. |
| **API URL** | string | No | Please enter your basic URL from GitLab instance. Default `gitlab.com`. |
| **Groups** | array | No | List of groups. e.g. your-group. |
| **Projects** | array | No | Space-delimited list of projects. e.g. your-group/your-project your-group/other-project. |
| **Number of Concurrent Threads** | integer | No | Number of concurrent threads for syncing. Higher values can speed up syncs but may hit rate limits. Adjust based on your GitLab instance rate limits. Default `4`. |

### Authorization Method


Choose one of the following. Each asks for its own fields.

**OAuth2.0**

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| **Access token** | string, secret | Yes | Access Token for making authenticated requests. |
| **Client id** | string, secret | Yes | The API ID of the Gitlab developer application. |
| **Client secret** | string, secret | Yes | The API Secret the Gitlab developer application. |
| **Refresh token** | string, secret | Yes | The key to refresh the expired access_token. |
| **Token expiry date** | string | Yes | The date-time when the access token should be refreshed. |

**Private Token**

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| **Private Token** | string, secret | Yes | Log into your Gitlab account and then generate a personal Access Token. |


## Related

:::links
- [Sync modes](https://docs.sanda-os.com.au/connections/sync-modes): How sanda reads each stream on every run.
- [Sync schedules](https://docs.sanda-os.com.au/connections/schedules): How often a connection runs.
- [Allowlist sanda’s address](https://docs.sanda-os.com.au/connections/allowlist): For a system behind a firewall.
- [Troubleshoot connections](https://docs.sanda-os.com.au/connections/troubleshooting): What an error means and how to fix it.
:::