Configuring identity mappings

The identity mappings feature allows you to map accounts from different integrations to Cortex accounts, based on name or email address. With identity mapping, you can not only make sure that integrations are working properly for your team members, but you can also ensure that the Developer Homepage and Eng Intelligence features are working as intended with their mappings.

Identity mapping is available for:

• Azure DevOps

• Bitbucket

• ClickUp

• GitHub

• GitLab

• Jira

• Microsoft Teams

• Opsgenie

• PagerDuty

• Slack

Git providers and Jira support multiple mappings per user.

View your personal identity mappings

All of your personal mappings for your established integrations are listed in Cortex under Settings > My identity mapping.

From this page, you can directly add your OAuth user for GitHub cloud if there’s no mapping. For other integrations, a user with the Configure identity mappings permission must configure the identity mappings.

OAuth mapping is only valid for GitHub cloud and not for GitHub Enterprise server.

View and manage all identity mappings

Users with the Configure identity mappings permission can review all user mappings specific to each configured integration in your Cortex Settings under the "Identity mappings" section. Any integrations configured will appear there, whether you have already mapped users or not.

See specific identity mapping pages in the Cortex Settings

Review mapped and ummapped users

Click on one of your configured integrations under Settings > Identity mappings to view the user mappings for that integration. You'll see the option to select a mapping next to users who have not yet been mapped for the integration you're viewing.

In the upper right corner of each integration's user mapping page, click Display then toggle on Hide mapped users to view only a list of unmapped users.

Map unmapped users

While viewing the user mappings for an integration, you can view Cortex's suggestions for user accounts. You can accept suggestions individually by clicking the checkmark next to a suggestion in a user’s row.

You can also bulk accept suggestions selecting Accept all suggestions in the upper right corner of the list. This will open a modal where you can review all the accounts with available suggested mappings, and quickly confirm mappings for dozens of users at once.

If Cortex does not have a suggestion, you will see a dropdown menu labeled Select mapping for that user.

Map multiple identities to users

You may have multiple instances within your git providers or Jira. It is possible to have multiple identities mapped in Cortex for a single user corresponding with each instance alias.

The following providers are supported:

• Azure DevOps

• Bitbucket

• GitHub

• GitLab

• Jira

To configure multiple mappings for a user:

1. In Cortex, click your avatar in the lower left corner then click Settings.

2. In Settings, under "Identity mappings," click into the integration you want to configure mappings for.

3. Locate the user you need to map. Next to their name, click the arrow to expand their mappings.

4. In the dropdown menus next to each instance alias name, if an identity has not been mapped, Cortex will recommend a possible user to map. In the dropdown, select the user, then click Save.

   • If multiple aliases are configured for an integration, you may see a dropdown in the identity mappings settings titled Unknown. This happens if no alias is associated with the identity mapping. When Cortex syncs user identity information, it will attempt to match the identity mapping with an alias. This will not impact any functionality within Cortex.