Aktivieren von GitHub Copilot Enterprise-Features

Erfahren Sie, wie Sie die für GitHub Copilot Enterprise verfügbaren Features aktivieren oder deaktivieren.

In diesem Artikel

Introduction

To enable users to use Copilot Enterprise features, your GitHub Enterprise Cloud enterprise must have a subscription to Copilot Enterprise. For more information, see "About GitHub Copilot."

Access to Copilot is determined at the enterprise and organization levels:

When access to Copilot has been enabled, features such as the ability to use Copilot on GitHub.com, can be configured. Features are enabled or disabled at the enterprise or organization level:

  • Enterprise owners can set Copilot features to be enabled or disabled for all organizations in the enterprise that have access to Copilot. Alternatively, they can allow each organization to set its own policy for each feature.
  • If the enterprise owner has permitted it, organization owners can enable or disable Copilot features for their organization.

This article explains how to enable or disable the features of GitHub Copilot Enterprise at the enterprise level, and for an individual organization.

About Copilot Enterprise features

GitHub Copilot Enterprise provides AI features to enhance your experience on GitHub.com, such as the ability to chat with Copilot in the browser and reference context for Copilot from across your project repositories. For more information, see "GitHub Copilot Enterprise feature set."

When members are granted access to the features, they'll be notified by email that they have access. The message includes instructions on how to start using the features.

Enabling or disabling GitHub Copilot Enterprise features for an enterprise

An enterprise owner can choose whether to enable GitHub Copilot Enterprise features for all organizations, disable for all organizations, or allow each organization to choose its own policy for the features. By default, each organization can choose its own policy.

  1. On the left side of the page, in the enterprise account sidebar, click Policies.

  2. In the " Policies" section, click Copilot.

  3. On the "GitHub Copilot" page, click the Policies tab.

  4. Next to "Copilot in GitHub.com," click the dropdown menu and select the policy you want to enforce.

    • No policy - Allow each of your organizations to set their own policy. "Copilot in GitHub.com" will initially be disabled for all organizations, but can be enabled by organization owners in their organization settings.
    • Enabled - Allow use of "Copilot in GitHub.com" by all members of organizations in your enterprise who have been granted access to Copilot.
    • Disabled - Prevent organizations from assigning Copilot Enterprise seats to members under the enterprise's Copilot Enterprise subscription.

  5. If you select Enabled for the "Copilot in GitHub.com" policy, the Opt in to user feedback collection check box is displayed.

    Clear the Opt in to user feedback collection check box to prevent the display of the thumbs up and thumbs down feedback icons after Copilot generates a pull request summary. The thumbs up and thumbs down feedback icons will still be displayed below each response in the Copilot Chat panel, and users will still be able to submit written feedback to GitHub about Copilot generally via the "Give feedback" link in the chat panel.

    If you select the Opt in to user feedback collection check box, then when a user clicks the thumbs up or thumbs down icon, after a pull request summary is generated, the summary will be returned to GitHub to provide context for the user's feedback.

    For more information about user feedback collection for Copilot, see "Asking GitHub Copilot questions in GitHub.com."

    Note

    If you choose No policy for the "Copilot in GitHub.com" option, user feedback collection will initially be enabled at the organization level, but organization owners can choose to opt out for their organization.

  6. Next to "Give Copilot access to Bing," click the dropdown menu and select the policy you want to enforce.

    • No policy - Allow each of your organizations to set their own policy. Access to Bing will initially be disabled for all organizations, but can be enabled by organization owners in their organization settings.

    • Enabled - Allow Copilot Chat to use results from a Bing web search to provide information for its responses. See "Asking GitHub Copilot questions in GitHub.com" and "Asking GitHub Copilot questions in your IDE."

    • Disabled - Prevent Copilot Chat from accessing Bing.

    Note

    Bing search integration into Copilot Chat in GitHub.com, VS Code, and Visual Studio is currently in beta and is subject to change.

Enabling or disabling Copilot Enterprise features for an organization

Organization owners can enable or disable Copilot Enterprise for all members of their organization that have access to Copilot Enterprise, provided no specific policy has been set to enable or disable Copilot Enterprise at the enterprise level.

Granting access to Copilot

To give members of your organization access to the features of Copilot Enterprise those members must have access to Copilot. This is achieved by assigning seats for Copilot. Once a GitHub Enterprise Cloud admin enables a Copilot Enterprise subscription in your organization, you can assign GitHub Copilot seats to individuals and teams in the organization. See "Granting access to Copilot for members of your organization."

Enabling or disabling Copilot Enterprise

Copilot Enterprise can be enabled or disabled at either the enterprise or organization level.

If your organization's parent enterprise has selected No policy for "Copilot in GitHub.com" in the enterprise settings, GitHub Copilot Enterprise will initially be disabled for your organization. If you are an owner of the organization, you can choose to enable the additional features provided by GitHub Copilot Enterprise for all of the organization's members who have access to Copilot.

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

  2. Next to the organization, click Settings.

  3. In the sidebar, under "Code, planning, and automation", click Copilot, and then click Policies.

    Note

    If the side panel only contains the Access option under Copilot, it indicates that Copilot is not currently available in the organization. An enterprise admin must enable Copilot for your organization. See "Enabling Copilot for organizations in your enterprise."

  4. Next to "Copilot in GitHub.com", select the dropdown menu (labeled Disabled by default), then choose from the following options.

    • Enabled: The feature is enabled for all members of the organization.
    • Disabled: The feature is disabled for all members of the organization.

  5. If you select Enabled, two check boxes are displayed.

Configuring Copilot Enterprise features for an organization

After Copilot Enterprise has been enabled for an organization, an administrator should spend a few minutes setting up their organization to ensure users have a great onboarding experience.

  1. Index your organization's most popular repositories.

    Copilot Enterprise works best when repositories have semantic code indexing enabled. For more information, see Asking GitHub Copilot questions in GitHub.com.

    Note

    Initial indexing can take up to 30 minutes for large repositories. Once a repository has been indexed for the first time, updates will typically be indexed within 5 minutes.

  2. Create at least one knowledge base.

    Knowledge bases bring together Markdown documentation across one or more repositories and make them available through Copilot Enterprise. Once created, organization members can specify a knowledge base as the context for Copilot Chat in GitHub.com and Copilot Chat in Visual Studio Code. For more information, see "Managing Copilot knowledge bases."

Further reading