> For the complete documentation index, see [llms.txt](https://docs.pullrequest.com/on-premise-server/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pullrequest.com/on-premise-server/configure-webhooks/configure-gitlab-webhooks.md).

# Configure GitLab Webhooks

After the GitLab posting user has been created and the repositories are populating in the HackerOne Code dashboard successfully, the GitLab webhooks can be configured.

## Configure Webhooks

GitLab allows webhooks to be configured on a GitLab Group level or per Project within a Group.

{% hint style="warning" %}
**HackerOne strongly recommends configuring webhooks on the Group level** so that new Projects your team creates will be immediately provisioned without service interruption.
{% endhint %}

* [**Apply on the Group level**](https://docs.pullrequest.com/gitlab-self-managed/configure-gitlab-webhooks#applying-on-the-group-level) (recommended)
* [**Apply to each Project individually**](https://docs.pullrequest.com/gitlab-self-managed/configure-gitlab-webhooks#applying-on-the-project-level)

## Applying on the Group level

From your GitLab dashboard, select the desired GitLab **Group** -> **Settings** -> **Webhooks**:

![NOTE: GitLab's interface may change without notice](https://624363444-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LNMKNsDv2KL9GI5L5YY%2F-Lhf6qZunJ_9gib6ID44%2F-LhfDNZZXcAPRj_b6P3E%2Fimage.png?alt=media\&token=54fe6ae8-bf27-4c5d-a7bc-3f6de1e88580)

![](https://624363444-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LNMKNsDv2KL9GI5L5YY%2F-Lhf6qZunJ_9gib6ID44%2F-LhfDTZfZ0vajLPFJgLS%2Fimage.png?alt=media\&token=b83f1a9b-c035-4c50-83ec-5ba930548990)

### Webhook Settings

#### **URL** 

The base URL of your Proxy with the following:

```
/webhooks/gitlab
```

#### Triggers

* [x] **Comments**
* [x] **Merge request events**

#### SSL verification

* [x] **Enable SSL Verification**

***OPTIONAL** -* Add a webhook secret. The secret will be used to sign your webhook requests as they are posted to the proxy:

* You will need the same webhook secret for all of your repositories if you add one.
* This secret must match the `WEBHOOK_SECRET` field when you configured the proxy.

### Test Connection

Click the **Add Webhook** button; the webhook should appear in the **Webhooks** section at the bottom of the page.

Click the **Test** button to test the connection. You should receive a "Hook executed successfully:" message at the top of the screen.

{% hint style="warning" %}
If you received an error message, double-check the proxy base is valid and `/webhooks/gitlab` is added as a path.
{% endhint %}

## Applying on the Project level

Webhooks can also be applied at the project level. The configuration is the same:

![](https://624363444-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LNMKNsDv2KL9GI5L5YY%2F-Lhf6qZunJ_9gib6ID44%2F-LhfDl5F9YXF02tsCE6F%2Fimage.png?alt=media\&token=dd98ac30-91cf-48e3-8714-8f70a6d58b28)

### Webhook Settings

#### **URL** 

The base URL of your Proxy with the following:

```
/webhooks/gitlab
```

#### Triggers

* [x] **Comments**
* [x] **Merge request events**

#### SSL verification

* [x] **Enable SSL Verification**

***OPTIONAL** -* Add a webhook secret. The secret will be used to sign your webhook requests as they are posted to the proxy:

* You will need the same webhook secret for all of your repositories if you add one.
* Update your webhook secret in the PullRequest Proxy UI if you are adding one, otherwise the proxy will not be able to verify/process the webhooks.

### Test Connection

Click the **Add Webhook** button; the webhook should appear in the **Webhooks** section at the bottom of the page.

Click the **Test** button to test the connection. This will expand a list of trigger types.

Select **Merge request events** from the list.

![](https://624363444-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LNMKNsDv2KL9GI5L5YY%2F-Lhf6qZunJ_9gib6ID44%2F-LhfDuJlq2sXZeVGP1gV%2Fimage.png?alt=media\&token=12f27a68-2508-46e0-92db-077e40d61fe7)

 You should receive a "Hook executed successfully:" message at the top of the screen.

{% hint style="warning" %}
If you received an error message, double-check the proxy base is valid and `/webhooks/gitlab` is added as a path.
{% endhint %}

Repeat these steps for any other GitLab Projects listed in PullRequest that have not been configured.