Overview

Link your GitHub teams to Datadog Teams to automatically provision Datadog Teams. The following features are supported:

• Create Datadog Teams based on your GitHub teams configuration.
• Sync team membership between Datadog and GitHub. Requires individual users to connect their Datadog accounts to GitHub.

Datadog links existing teams by performing an exact name match between GitHub team slugs and Datadog Team handles. The match is case-insensitive and ignores whitespace differences.

If your GitHub teams have a hierarchical team structure, Datadog replicates that same structure during provisioning.

Note: In Datadog, a sub-team must be as restrictive as or more restrictive than its parent team. For example, a sub-team cannot be open if the parent team is invite-only.

Datadog only reads GitHub teams. Datadog never modifies, creates, or deletes GitHub teams.

Prerequisites

GitHub integration

Ensure your Datadog organization is connected to a GitHub organization. Your GitHub integration must have the members_read permission to read team data.

Permissions

• To link and create teams, your Datadog user must have the teams_manage permission.
• To manage team membership, your Datadog user must have the user_access_manage permission.

Setup

Connect GitHub teams to Datadog Teams

1. Navigate to Teams.
2. In the upper right, click GitHub Connections.
3. Configure your connection by selecting options for import type, sync members, and cadence.
4. Click Save.

View Datadog Teams

1. Navigate to GitHub Connections.
2. If the list of created and linked teams is empty, click Refresh.
3. Optionally, manually update Datadog Teams to reach your desired state.

User configuration

After an admin enables team provisioning from GitHub, a notification appears on the Team detail page. The notification asks users Log in to GitHub to connect their accounts from Datadog to GitHub through OAuth.

Each user must manually link their GitHub account to Datadog to establish the connection between Datadog and GitHub. This behavior is required by GitHub’s OAuth and user privacy policies.

After a user links their accounts, Datadog adds the user to any Datadog Teams that correspond to GitHub teams where the user is a member.

For example, assume that user B is a member of team A in GitHub. The following sequence occurs in Datadog:

1. An admin enables Datadog Teams provisioning and user syncing from GitHub.
2. Team A is created in Datadog, empty.
3. User B sees a notification to Log in to GitHub and follows through.
4. User B is provisioned into Team A in Datadog.

Deleting teams

The GitHub automatic connection only manages resources that it created.

If a team was created manually in Datadog and later linked to a GitHub team, deleting that GitHub team does not delete the Datadog Team.

However, if a team was originally created by the automatic GitHub sync, and that GitHub team is deleted, Datadog also deletes the corresponding team to maintain consistency.

Examples

The following examples show the different results when deleting teams that were created in Datadog versus GitHub.

Team created in Datadog:

1. An admin creates Team A in Datadog.
2. Team A is linked to a GitHub team.
3. Team A is deleted in GitHub.
4. Team A remains in Datadog, but is not linked to any GitHub team.

Team created automatically from GitHub:

1. In Datadog, Team B is created automatically from GitHub.
2. Team B is deleted in GitHub.
3. Team B is automatically deleted in Datadog.

Further reading

Documentation, liens et articles supplémentaires utiles:

GitHub integrationDOCUMENTATION