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

# Setup GitLab Discovery

> Enable GitLab Discovery in Portal for GitLab-backed repository workflows.

## Overview

This step will guide you through the process of setting up GitLab Discovery for the repositories Portal should be able to read from GitLab.

### Step Checklist

This is the second (2) step in this guide.

1. [Setup the GitLab integration in App Settings](./gitlab-app-settings-integrations)
2. ***Setup GitLab Discovery***

## Walkthrough

To enable GitLab Discovery, navigate to Catalog Settings > Providers, open the GitLab provider, and add a new provider configuration.

<Frame>
  <img
    src="https://mintcdn.com/spotify-89f50c35/vAIwtfnEDW2fYb5m/portal/assets/gitlab-catalog-provider.png?fit=max&auto=format&n=vAIwtfnEDW2fYb5m&q=85&s=b6ecc44b181ded06891c851518a36706"
    alt="GitLab catalog provider configuration in Catalog
Settings"
    width="1404"
    height="908"
    data-path="portal/assets/gitlab-catalog-provider.png"
  />
</Frame>

## Required Fields

Fill in the required fields before saving:

* `Provider ID` - A unique identifier for this provider configuration. Use `default` to get started.
* `Host` - The hostname of the GitLab instance Portal should read from. Use `gitlab.com` for GitLab SaaS, or your self-managed GitLab hostname.
* `Schedule` - Configure when and how often Portal refreshes this provider. Use the default schedule to get started, then adjust the refresh frequency and timeout later if needed.

The `Group` and `Branch` fields are optional. Leave them at their defaults to start unless you need to limit discovery to a specific GitLab group or branch.

After saving the configuration, wait for Portal to apply the new settings and reload when prompted.

From here Portal can use the GitLab provider configuration for supported GitLab-backed workflows.