By default, DX links user identities in third-party tools based on email addresses. For example, a user in PagerDuty with the email [email protected] would be matched to the corresponding DX user with the same email.
However, some third-party tools—either consistently or in specific scenarios—do not store or expose work email addresses through their APIs. In these cases, alternative user linking methods are required, as detailed in the table below:
Tool | User linking method |
GitHub | For organizations using GitHub Enterprise Cloud with a verified domain, the GitHub API provides users’ verified work email addresses through the
In all other scenarios, the GitHub API does not expose users' work emails. To link identities in these cases, customers should associate GitHub usernames with DX users—either via CSV upload, API, SCIM integration, or manually through the DX UI.
|
GitLab | The GitLab API does not provide users’ work email addresses. To link user identities, customers should associate GitLab usernames with DX users—either through CSV upload, API requests, SCIM, or manually via the DX UI.
|
Jira Cloud | Jira’s API only returns user email addresses for Managed accounts. As a result, a Managed account is required to integrate Jira with DX. In some cases, certain email addresses may still be unavailable via the API, requiring manual user linking within the DX UI.
|
Bitbucket Cloud | The Bitbucket API does not provide user email addresses. To enable user identification, a Jira Cloud connection is required so that DX can link Bitbucket users based on their associated Jira IDs.
|