Skip to main content
Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos.

Troubleshooting license usage for GitHub Enterprise

You can troubleshoot license usage for your enterprise by auditing license reports.

Enterprise owners can review license usage for GitHub Enterprise.

About unexpected license usage

If the number of consumed licenses for your enterprise is unexpected, you can review your consumed license report to audit your license usage across all your enterprise deployments and subscriptions. If you find errors, you can try troubleshooting steps. For more information about viewing your license usage, see "Viewing license usage for GitHub Enterprise" and "Viewing the subscription and usage for your enterprise account."

For privacy reasons, enterprise owners cannot directly access the details of user accounts.

About the calculation of consumed licenses

GitHub bills for each person who uses deployments of GitHub Enterprise Server, is a member of an organization on Nube de GitHub Enterprise, or is a Suscriptor de Visual Studio. For more information about the people in your enterprise who are counted as consuming a license, see "About per-user pricing."

Para que una persona que utiliza varios ambientes de GitHub Enterprise consuma una licencia única, debes sincronizar el uso de licencias entre ambientes. Entonces, GitHub dejará de duplicar a los usuarios con base en las direcciones de correo electrónico asociadas con sus cuentas de usuario. Las cuentas de usuario múltiples consumirán una sola licencia cuando haya una coincidencia entre la dirección de correo electrónico principal en GitHub Enterprise Server o con una dirección de correo electrónico verificad de una cuenta de GitHub.com. Para obtener más información sobre la verificación de las direcciones de correo electrónico de GitHub.com, consulta la sección "Verificar tu dirección de correo electrónico" en la documentación de Nube de GitHub Enterprise.

Cuando sincronizas el uso de licencia, solo la ID de usuario y las direcciones de correo electrónico de cada cuenta de usuario en GitHub Enterprise Server se transmiten a Nube de GitHub Enterprise.

Fields in the consumed license files

The GitHub.com license usage report and GitHub Enterprise Server exported license usage file include a variety of fields to help you troubleshoot license usage for your enterprise.

GitHub.com license usage report (CSV file)

The license usage report for your enterprise is a CSV file that contains the following information about members of your enterprise. Some fields are specific to your Nube de GitHub Enterprise (GHEC) deployment, GitHub Enterprise Server (GHES) connected environments, or your Visual Studio subscriptions (VSS) with GitHub Enterprise.

CampoDescripción
NombreFirst and last name for the user's account on GHEC.
Handle or emailGHEC username, or the email address associated with the user's account on GHES.
Profile linkLink to the GitHub.com profile page for the user's account on GHEC.
License typeCan be one of: Visual Studio subscription or Enterprise.
License statusIdentifies if a user account on GitHub.com successfully matched either a Suscriptor de Visual Studio or GHES user.

Can be one of: Matched, Pending Invitation, Server Only, blank.
Member rolesFor each of the organizations the user belongs to on GHEC, the organization name and the person's role in that organization (Owner or Member) separated by a colon

Each organization is delimited by a comma.
Roles en la empresaCan be one of: Owner or Member.

Suscriptor de Visual Studios who are not yet members of at least one organization in your enterprise will be included in the report with a pending invitation status, and will be missing values for the "Name" or "Profile link" field.

GitHub Enterprise Server exported license usage (JSON file)

Your GitHub Enterprise Server license usage is a JSON file that is typically used when performing a manual sync of user licenses between GitHub Enterprise Server and Nube de GitHub Enterprise deployments. The file contains the following information specific to your GitHub Enterprise Server environment.

CampoDescripción
CaracterísticasThe GitHub Connect features that are enabled on your GitHub Enterprise Server instance, and the date and time of enablement.
Host nameThe hostname of your GitHub Enterprise Server instance.
HTTP onlyWhether Transport Layer Security (TLS) is enabled and configured on your GitHub Enterprise Server instance. Can be one of: True or False.
LicenciaUn hash de tu licencia GitHub Enterprise Server.
Public keyLa parte pública de la clave de tu licencia GitHub Enterprise Server.
Server IDUUID generated for your GitHub Enterprise Server instance.
VersiónThe version of your GitHub Enterprise Server instance.

Troubleshooting consumed licenses

If the number of consumed seats is unexpected, or if you've recently removed members from your enterprise, we recommend that you audit your license usage.

To determine which users are currently consuming seat licenses, first try reviewing the consumed licenses report for your enterprise and/or an export of your GitHub Enterprise Server license usage for unexpected entries.

There are two especially common reasons for inaccurate or incorrect license seat counts.

  • The email addresses associated with a user do not match across your enterprise deployments and subscriptions.
  • An email address for a user was recently updated or verified to correct a mismatch, but a license sync job hasn't run since the update was made.

When attempting to match users across enterprises, GitHub identifies individuals by the verified email addresses associated with their GitHub.com account, and the primary email address associated with their GitHub Enterprise Server account and/or the email address assigned to the Suscriptor de Visual Studio.

Your license usage is recalculated shortly after each license sync is performed. You can view the timestamp of the last license sync job, and, if a job hasn't run since an email address was updated or verified, to resolve an issue with your consumed license report you can manually trigger one. For more information, see "Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud."

If your enterprise uses verified domains, review the list of enterprise members who do not have an email address from a verified domain associated with their GitHub.com account. Often, these are the users who erroneously consume more than one licensed seat. Para obtener más información, consulta la sección "Ver a los miembros sin un a dirección de correo electrónico desde un dominio verificado".

Note: For privacy reasons, your consumed license report only includes the email address associated with a user account on GitHub.com if the address is hosted by a verified domain. For this reason, we recommend using verified domains with your enterprise account on GitHub.com. Then, if one person is erroneously consuming multiple licenses, you can more easily troubleshoot, as you will have access to the email address that is being used for license deduplication.

If you still have questions about your consumed licenses after reviewing the troubleshooting information above, you can contact Soporte de GitHub through the GitHub Support portal.