Экспорт сведений об участниках организации

В этой статье

You can export information about all of your organization's members from GitHub's web UI.

Кто может использовать эту функцию.

Organization owners can export member information for an organization.

About export of membership information

You can export aggregated information about your organization's members as a report. For example, you may want to perform an audit of your organization's current members. You can generate a file containing the report from GitHub's web UI.

The membership information report includes the following information.

  • Username and display name details
  • Whether the user has two-factor authentication enabled
  • Whether the membership is public or private
  • Whether the user is an organization owner or member
  • Datetime of the user's last activity (for a full list of relevant activity, see "Managing dormant users")
  • Optionally, additional information that depends on the organization's configuration:
    • The user's SAML NameID
    • Username and primary email addresses on any GitHub Enterprise Server instances where GitHub Connect is configured
    • User, subscription email address, and license status for Visual Studio subscriptions with GitHub Enterprise

You can also use GitHub's APIs to retrieve information about your organization's members. For more information, see the GraphQL API and REST API documentation.

Enterprise owners can also export membership information for an enterprise. For more information, see "Exporting membership information for your enterprise."

Exporting a membership information report

You can download a CSV or JSON file containing the membership information report for your organization.

  1. In the upper-right corner of GitHub.com, select your profile photo, then click Your organizations.

    Screenshot of the dropdown menu under @octocat's profile picture. "Your organizations" is outlined in dark orange.

  2. Click the name of your organization.

  3. Under your organization name, click People.

    Screenshot of the horizontal navigation bar for an organization. A tab, labeled with a person icon and "People," is outlined in dark orange.

  4. To the right of the search bar, select the Export dropdown menu and click the desired export format.

Viewing members' email addresses

You may be able to view the email addresses for members of your organization on either GitHub.com or an external identity system. The visibility of the email addresses depends on the organization's authentication configuration, domains, and potentially the member's user profile configuration.

  • If SAML single sign-on (SSO) is configured for your organization and the NameID for your SAML configuration is an email address, you can view the NameID for each of your organization members.

  • If you verify a domain for your organization, you can view members' email addresses for the verified domain.

  • If you don't configure SAML SSO, members access your organization's resources on GitHub.com solely using a personal account. The owner of a personal account can choose whether or not to publicly display an email address. If a user chooses not to display the email address, you cannot view the email address. Without SAML, GitHub cannot display external identity information, like the NameID, which is typically an email address.

If SAML SSO is configured for your organization, or if you have verified a domain, you may be able to view the email addresses in one or more of the following ways.

  1. On your SAML Identity Provider (IdP), review the email addresses of users with access to GitHub Enterprise Cloud. For more information, see "About SAML for enterprise IAM."

  2. Export the membership report for your organization. The report may contain the user's email address, stored as the following values.

    For more information, see "Exporting membership information."

  3. Use the GraphQL API to retrieve the ExternalIdentity for each member. For more information, see "About the GraphQL API" and "Objects" in the GraphQL API documentation.