GitHub FAQs

Why are most of my GitHub users Unmatched?

Situation

All of the users coming back from your GitHub integration are labeled as "Unmatched" and don't have email addresses.

Solution

This happens because GitHub doesn't always return private user email addresses with GitHub handles.

Not all GitHub users have public emails on their profiles, so if GitHub doesn't return this information to us, we can't match it to an employee identity on our side and we call the account "Unmatched".

To manually match the accounts, follow the steps in this article:📄 How-To: Match Accounts

Why does my GitHub integration have 0 users?

Situation

After connecting the GitHub integration, Lumos is showing no users. See📄 Connecting GitHub

Solution

This is likely due to a permissions restriction on the GitHub side. To resolve this, check the following:

1. Check that the GitHub user you used to connect the integration is a GitHub Administrator with access to view all users and their org memberships.

If you're not sure, reconnect the integration. See📄 Connecting GitHub

2. Make sure that the Lumos app is approved in your GitHub tenant.

This article walks through the process of approving the Lumos app in your GitHub organization. If the Lumos app isn't approved, we can't pull back the list of users and their org memberships.

Why doesn't a user's GitHub email match their company email?

Situation

The email address of an account returned by the GitHub integration is the employee's personal email, instead of their company email.

Solution

Lumos uses the public email field on the user's GitHub profile (if it's made available by the user) that's returned by the GitHub API and prioritizes that email when showing the user account in the Accounts tab.

You can match the account to the correct Lumos User, if it's unmatched, by following these steps:📄 How-To: Match Accounts