Skip to main content
We publish frequent updates to our documentation, and translation of this page may still be in progress. For the most current information, please visit the English documentation.

This version of GitHub Enterprise was discontinued on 2023-03-15. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Managing the forking policy for your organization

You can allow or prevent the forking of any private and internal repositories owned by your organization.

Who can use this feature

Organization owners can manage the forking policy for an organization.

By default, new organizations are configured to disallow the forking of private and internal repositories.

If you allow forking of private and internal repositories at the organization level, you can also configure the ability to fork a specific private or internal repository. For more information, see "Managing the forking policy for your repository."

  1. In the top right corner of GitHub Enterprise Server, click 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. Next to the organization, click Settings.

  3. In the "Access" section of the sidebar, click Member privileges.

  4. Under "Repository forking", select Allow forking of private and internal repositories.

  5. Click Save.

Further reading