---
title: Configure DevOps Intelligence
for GitHub, legacy users
slug: configure-devops-intelligence-for-github-legacy-users
docTags: 
createdAt: 2026-07-09T18:48:43.545Z
---

This procedure is valid only for customers onboarded before 6 June 2024. Procedures for recent customers are provided in the subsequent section Configure  DevOps Intelligence for Git and legacy customers.

# Organization level tracking

1. Navigate to DevOps Intelligence → **Settings & Utilities** → **Tools Configuration** → **Add Configuration**.
2. For **Tool engine**, select **GitHub.**
3. For**Connection**select the appropriate connection name.
   For **Tracking Type**, select **Organization**.
4. For Organization, select any organization to be tracked.
5. Click configure.

Additional configurations are supported:

- Configure release format: Release can be identified by the pattern generated from two fields, **prefix** and **variable**.
- Severity of defects: Sev 1, Sev 2, Sev 3 and Sev 4 are terminologies used in  DevOps Intelligence dashboards. Using these severity levels, the user is allowed to provide mapping for endpoint Severity Values. For example, any value provided under the "Severity: Sev 1" category, will be considered as "Sev 1" while displaying the values on the dashboard.

# Tracking Non-Organization(Independent) Repositories

Use the following procedure to configure GitHub for repositories:

1. Navigate to DevOps Intelligence → **Settings & Utilities** → **Tools Configuration** → **Add Configuration**.
2. For **Tool engine**, select GitHub.
3. For **Connection**, select the appropriate connection name.
4. For **Type**, select Repository and Organisation. This selection is **not** required.
5. For Repository select any repo you want to track.
6. Click configure.

Additional configurations are supported:

- Configure release format - Release is being identified by the pattern generated from two fields, **prefix** and **variable**.
- Severity of defects: Sev 1, Sev 2, Sev 3 and Sev 4 are terminologies used in  DevOps Intelligence  dashboards. Using these severity levels, the user is allowed to provide mapping for endpoint Severity Values. For example, any value provided under the "Severity: Sev 1" category, will be considered as "Sev 1" while displaying the values on the dashboard.
- [GitHub Webhook configuration](docId\:Zq0J-dl3DYuBbeSzVhD_t) Understand how to configure a Webhook for GitHub to ensure proper data synchronization.